GITBOOK-189: Update activation sequence graphic

nakamoto-upgrade/nakamoto-rollout-plan/README.md

@@ -30,20 +30,14 @@ Nakamoto rules are the logic that makes Nakamoto different than the version befo
 
 ### Nakamoto Activation Sequence
 
-**On August 28th, the final code for Nakamoto will be shipped to network operators and the activation window will open**. Network operators will have one Stacking Cycle (Cycle 92) to upgrade. After the network has successfully handed off from Cycle 92 to Cycle 93, a final hard fork block will be chosen by core developers.\
-
-
-<table><thead><tr><th width="68"></th><th width="175">Step	</th><th width="316">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>August 28th</td></tr><tr><td>C</td><td><strong>C</strong>ycle Handoff - Signers</td><td>With final code loaded on mainnet, Signers have one full Stacking cycle to make any necessary final adjustments to their setup. 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><strong>D</strong>etermine Hard Fork Block</td><td>Once the handoff from Cycle 92 to Cycle 93 has been confirmed as successful at Block 861,500, Core Developers will pick the final hard fork block for all Nakamoto rules to go live.</td><td>During reward phase of Cycle 93</td></tr><tr><td>E</td><td><strong>E</strong>poch 3.0 - Nakamoto Rules Start</td><td>Fast blocks, full Bitcoin finality! Nakamoto rules go live at the hard fork block.</td><td>At 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><strong>D</strong>etermine Hard Fork Block</td><td>Core Developers <a href="https://stacks.org/nakamoto-hard-fork-block">have selected Bitcoin block #864864</a></td><td>Sept 20</td></tr><tr><td>E</td><td><strong>E</strong>poch 3.0 - Nakamoto Rules Start</td><td>Fast blocks, full Bitcoin finality! Nakamoto rules go live at Bitcoin block #864864.</td><td><a href="https://stacks.org/nakamoto-hard-fork-block#countdown">Current projection: ~October 9</a></td></tr></tbody></table>
 
 ### Factors that could affect timelines:
 
 * **Testing & Audit Results:** A top-notch group of researchers, contractors, and testers, along with security auditors from Clarity Alliance and Quantstamp, continue to hammer away at Nakamoto as they have for the past several months. This testing is ongoing, so there is always the possibility they surface an issue that needs to be addressed before the final hard fork.
 * **Signer Needs:** The ecosystem is proud to have industry leaders comprising its leading Signer network. Signers are a critical new network player so if a clear issue or unexpected need arises during activation, additional time would be taken to address it.
 * **Miner adoption:** As always, miners must choose to adopt the new code. Should they be delayed or experience issues with their setups, it could cause a delay in Activation.
-* **SIP-025 Voting:** While there is every indication Signers will approve the ongoing SIP-025 vote, we should not entirely eliminate the possibility feedback is raised which requires addressing before both Signers and core developers are comfortable with the signature scheme.
-
-Factors that could affect timelines:As always, core developers are committed to a safe, secure launch. As such, several factors _could_ warrant additional time added to the Nakamoto activation sequence outlined above and result in a new hard fork block being selected:\
-\
 
+Factors that could affect timelines: As always, core developers are committed to a safe, secure launch. As such, several factors _could_ warrant additional time added to the Nakamoto activation sequence outlined above and result in a new hard fork block being selected:
 
 \