diff --git a/nakamoto-upgrade/nakamoto-activation-guide-for-signers/README.md b/nakamoto-upgrade/nakamoto-activation-guide-for-signers/README.md
index 34cdde81c3..555f92e0e2 100644
--- a/nakamoto-upgrade/nakamoto-activation-guide-for-signers/README.md
+++ b/nakamoto-upgrade/nakamoto-activation-guide-for-signers/README.md
@@ -1,9 +1,9 @@
 # Nakamoto Activation Guide for Signers
 
 {% hint style="info" %}
-The block for Nakamoto activation has been chosen as Bitcoin block 864,864, which is currently expected on October 9th. This block is subject to change should core developers need additional time for testing or unexpected issues.
+The block for Nakamoto activation has been chosen as Bitcoin block 867,867, which is currently expected on October 29th. This block is subject to change should core developers need additional time for testing or unexpected issues.
 
-Binaries will be provided roughly a week in advance and your normal upgrade procedure should apply here, you’ll want to be running the latest node and Signer software. Note that if you do not upgrade ahead of the hard fork, your nodes will be dropped from the network. Ideally, you will have Stacked for Cycle #94 ahead of time, any time now is good.
+Binaries will be provided roughly a week in advance and your normal upgrade procedure should apply here, you’ll want to be running the latest node and Signer software. Note that if you do not upgrade ahead of the hard fork, your nodes will be dropped from the network.
 {% endhint %}
 
 #### Testnet Activation Window (August 19)
diff --git a/nakamoto-upgrade/nakamoto-rollout-plan/README.md b/nakamoto-upgrade/nakamoto-rollout-plan/README.md
index c47378fa1b..101eb1a47a 100644
--- a/nakamoto-upgrade/nakamoto-rollout-plan/README.md
+++ b/nakamoto-upgrade/nakamoto-rollout-plan/README.md
@@ -16,7 +16,7 @@ Nakamoto has completed step 1 of the rollout (Instantiation). Next, a hard fork
 The rollout will follow this two-step process, each of which is implemented via hard fork.  
 
 1. **Step 1 - Instantiation:** The pox-4 contract and the majority of the Nakamoto code are shipped, but Nakamoto rules are inactive. This is so other aspects of the contract can be tested before layering on the complexity that comes with the testnet (and later mainnet) being dependent on it. Importantly, this phase also allows time for Signers to register without the network being dependent on them to sign blocks.
-2. **Step 2 - Activation:** A process to make Nakamoto rules live begins on August 28. Once completely rolled out, the full set of Nakamoto features including Signer-based functions, fast blocks, and Bitcoin finality. In other words, ‘the switch is flipped’!
+2. **Step 2 - Activation:** Once completely rolled out, the full set of Nakamoto features including Signer-based functions, fast blocks, and Bitcoin finality. In other words, ‘the switch is flipped’! This switch is scheduled to occur at Bitcoin Block #867867 (\~October 29th).
 
 It’s important to note the heaviest lift of any hard fork is historically the sync from genesis. With the two Nakamoto forks, one goal is not to require this, making the upgrade more akin to a push-button software update and much simpler for all node operators.
 
@@ -30,7 +30,7 @@ Nakamoto rules are the logic that makes Nakamoto different than the version befo
 
 ### Nakamoto Activation Sequence
 
-<table><thead><tr><th width="106"></th><th width="169">Step	</th><th width="319">Overview	</th><th>Date/Period</th></tr></thead><tbody><tr><td>✅ A, B</td><td><strong>A</strong>ctivation Window Opens &#x26; <strong>B</strong>inaries Delivered</td><td>Pending no new bugs, final binaries are delivered - this is all the code Signers, Miners, and Node Operators need to run the network.</td><td>Aug 28th</td></tr><tr><td>✅ C</td><td><strong>C</strong>ycle Handoff - Signers</td><td>At the end of Cycle 92, core developers will watch for a successful ‘handoff’, meaning a successful change of the Signer sets between Stacking cycles.</td><td>Cycle 92 to Cycle 93</td></tr><tr><td>✅ D</td><td>First Testnet Hard Fork</td><td>Core developers performed a successful testnet hardfork (on Nakamoto testnet).</td><td>Sept 27</td></tr><tr><td>E</td><td>Determine Hard Fork Block</td><td>Core developers will select a mainnet hard fork block after performing a final testnet hardfork.</td><td>~October 10</td></tr><tr><td>F</td><td>Epoch 3.0 - Nakamoto Rules Start</td><td>Fast blocks, full Bitcoin finality! Nakamoto rules go live on mainnet at hard fork block.</td><td>Hard Fork Block</td></tr></tbody></table>
+<table><thead><tr><th width="106"></th><th width="169">Step	</th><th width="319">Overview	</th><th>Date/Period</th></tr></thead><tbody><tr><td>✅ A, B</td><td><strong>A</strong>ctivation Window Opens &#x26; <strong>B</strong>inaries Delivered</td><td>Pending no new bugs, final binaries are delivered - this is all the code Signers, Miners, and Node Operators need to run the network.</td><td>Aug 28th</td></tr><tr><td>✅ C</td><td><strong>C</strong>ycle Handoff - Signers</td><td>At the end of Cycle 92, core developers will watch for a successful ‘handoff’, meaning a successful change of the Signer sets between Stacking cycles.</td><td>Cycle 92 to Cycle 93</td></tr><tr><td>✅ D</td><td>First Testnet Hard Fork</td><td>Core developers performed a successful testnet hardfork (on Nakamoto testnet).</td><td>Sept 27</td></tr><tr><td>✅ E</td><td>Determine Hard Fork Block</td><td>Core developers have selected Bitcoin block #867867.</td><td>October 17</td></tr><tr><td>F</td><td>Epoch 3.0 - Nakamoto Rules Start</td><td>Fast blocks, full Bitcoin finality! Nakamoto rules go live on mainnet at hard fork block.</td><td>~October 29</td></tr></tbody></table>
 
 ### Factors that could affect timelines:
 
diff --git a/nakamoto-upgrade/nakamoto-rollout-plan/nakamoto-for-exchanges.md b/nakamoto-upgrade/nakamoto-rollout-plan/nakamoto-for-exchanges.md
index aa38981c71..d28e7b1cf0 100644
--- a/nakamoto-upgrade/nakamoto-rollout-plan/nakamoto-for-exchanges.md
+++ b/nakamoto-upgrade/nakamoto-rollout-plan/nakamoto-for-exchanges.md
@@ -44,7 +44,7 @@ Exchanges that support native Bitcoin yield via Stacking may have extra upgrade
 Core developers expect to release binaries on or around August 28th. Exchanges can expect their usual ecosystem point of contact to provide them with detailed information and updates during the process.&#x20;
 
 1. **Instantiation block:** The first hard fork occurred <mark style="color:orange;">at Bitcoin block 840,360.</mark> If you haven't already, you will need to upgrade to the latest node software or they will not process valid blocks and users will not be able to move funds on the network.
-2. **Activation block:** The second hard fork occurs around August 28. At this time, the Nakamoto consensus rules will activate, meaning the new Nakamoto features will be made live. Exchanges will need to repeat the upgrade process at this time. Again, no genesis sync, just a download and restart.
+2. **Activation block:** The second hard fork will occur at Bitcoin Block #867867 (\~October 29th). At this time, the Nakamoto consensus rules will activate, meaning the new Nakamoto features will be made live. Exchanges will need to repeat the upgrade process at this time. Again, no genesis sync, just a download and restart.
 
 The hard fork will occur **after** a series of activation steps. You can learn more about this upcoming Nakamoto Activation sequence here: [#nakamoto-activation-sequence](./#nakamoto-activation-sequence "mention").&#x20;