diff --git a/filecoin-virtual-machine/section-a.md b/filecoin-virtual-machine/section-a.md
index 6f58b5c..b4bfb96 100644
--- a/filecoin-virtual-machine/section-a.md
+++ b/filecoin-virtual-machine/section-a.md
@@ -1,4 +1,4 @@
-# 🅰 Upload, PoDSI, and Deal-Making
+# 🅰 Upload Your Data to Filecoin
 
 In this **Section A**, we will discuss the following
 
@@ -52,7 +52,7 @@ const dealParams = {
   num_copies: 2,
 };
 // The `false` indicates that we're uploading a single file.
-// Returns a CID (Content ID) for your file that you can use for PoDSI verification.
+// Returns a CID (Content ID) for your file that you can use for provable storage verification.
 const uploadResponse = await lighthouse.upload('/path/to/adorable/dog.jpg', 'YOUR_API_KEY', false, dealParams);
 ```
 {% endcode %}
@@ -127,7 +127,7 @@ const response = await lighthouse.upload(path, apiKey, false, dealParam_mock);
 const response = await lighthouse.upload(path, apiKey, false, dealParam_ignore);
 </code></pre>
 
-### Step 3: Understanding PoDSI: Getting the PoDSI for your file
+### Step 3: Understanding PoDSI: Getting Storage Proofs for your file
 
 Now that you've registered the picture of your puppy, how would you know that it's actually being maintained on the Filecoin network? This is where the PoDSI comes in. The PoDSI is a proof that your file is being maintained on the Filecoin network.
 
diff --git a/filecoin-virtual-machine/section-b.md b/filecoin-virtual-machine/section-b.md
index b6ce6f6..55fe71c 100644
--- a/filecoin-virtual-machine/section-b.md
+++ b/filecoin-virtual-machine/section-b.md
@@ -4,7 +4,7 @@ description: >-
   through the Lighthouse Smart Contract
 ---
 
-# 🅱 Attaching RaaS (renew, repair, replication) Worker
+# 🅱 Renew, Repair, and Replicate Storage on Filecoin
 
 ## <mark style="color:blue;">1) Attaching Lighthouse RaaS Worker</mark>