diff --git a/cspell.json b/cspell.json
index 02ea8cc..e32c4d8 100644
--- a/cspell.json
+++ b/cspell.json
@@ -188,7 +188,12 @@
     "jito",
     "Jito",
     "Offramp",
-    "offramp"
+    "offramp",
+    "offramps",
+    "zkcompression",
+    "ZKCompression",
+    "Tasktool",
+    "clippy"
   ],
   "ignorePaths": [
     "node_modules",
diff --git a/light-token/defi/programs.mdx b/light-token/defi/programs.mdx
index 3da147e..ab035e7 100644
--- a/light-token/defi/programs.mdx
+++ b/light-token/defi/programs.mdx
@@ -512,10 +512,12 @@ space. Both address spaces are checked before creation, preventing re-init
 attacks, even if the account is currently cold. </Accordion>
 
 <Accordion title="Who triggers compression?"> Miners automatically compress when
-virtual rent is below threshold (eg 24h without write bump). </Accordion>
+virtual rent is below threshold (e.g., multiple epochs without any writes). In
+practice, cold markets should be rare. The common path (hot) has no extra
+overhead and does not increase CU or txn size. </Accordion>
 
 <Accordion title="Can active pools get compressed?">
-No. Any write bumps the virtual rent balance. Active accounts never compress.
+No. Any write bumps the virtual rent balance. Active accounts do not get compressed.
 </Accordion>
 
 <Accordion title="Do I need to run infrastructure?"> No. Helius and Triton run
diff --git a/light-token/defi/routers.mdx b/light-token/defi/routers.mdx
index 601989b..a710333 100644
--- a/light-token/defi/routers.mdx
+++ b/light-token/defi/routers.mdx
@@ -171,12 +171,15 @@ Latency, tx size, and CU depend on the number and type of cold accounts.
 
 ### When does a market go cold?
 A market is "cold" after it has been compressed by a miner. Accounts become
-eligible for compression when inactive (e.g., after 24h without lamport bumps
-from fee payers), causing the virtual rent balance to fall below threshold.
+eligible for compression only after extended inactivity (e.g., multiple epochs
+without any writes), causing the virtual rent balance to fall below threshold.
+
+**In practice, cold markets should be rare.** The common path (hot) has no extra
+overhead and does not increase CU or txn size.
 
 **To ensure swaps execute regardless of whether the market is hot or cold,
-always prepend `create_load_instructions` to the swap transaction. This no-ops
-if the market is hot.**
+always call `create_load_instructions` when building the swap instructions. It
+simply no-ops if the market is hot.**
 
 ---
 ## Error Handling