diff --git a/docs/src/running-validator/restart-cluster.md b/docs/src/running-validator/restart-cluster.md
index a85d9524c3..8f52f38b69 100644
--- a/docs/src/running-validator/restart-cluster.md
+++ b/docs/src/running-validator/restart-cluster.md
@@ -2,11 +2,17 @@
 
 ### Step 1. Identify the slot that the cluster will be restarted at
 
-This will probably be the last root that was made. Call this slot `SLOT_X`
+
+The highest optimistically confirmed slot is the best slot to start from, which
+can be found by looking for
+[this](https://github.com/solana-labs/solana/blob/0264147d42d506fb888f5c4c021a998e231a3e74/core/src/optimistic_confirmation_verifier.rs#L71)
+metrics datapoint.  Otherwise use the last root.
+
+Call this slot `SLOT_X`
 
 ### Step 2. Stop the validator(s)
 
-### Step 3. Install the new solana version
+### Step 3. Optionally install the new solana version
 
 ### Step 4. Create a new snapshot for slot `SLOT_X` with a hard fork at slot `SLOT_X`
 
@@ -18,7 +24,7 @@ The ledger directory should now contain the new snapshot.
 `solana-ledger-tool create-snapshot` will also output the new shred version, and bank hash value,
 call this NEW\_SHRED\_VERSION and NEW\_BANK\_HASH respectively.
 
-Adjust your validator's arugments:
+Adjust your validator's arguments:
 
 ```bash
  --wait-for-supermajority SLOT_X
@@ -29,18 +35,13 @@ Then restart the validator.
 
 Confirm with the log that the validator booted and is now in a holding pattern at `SLOT_X`, waiting for a super majority.
 
-### Step 5. Update shred documentation
-
-Edit `https://github.com/solana-labs/solana/blob/master/docs/src/clusters.md`,
-replacing the old shred version with NEW\_SHRED\_VERSION. Ensure the edits make it into the release channel
-
-### Step 6. Announce the restart on Discord:
+### Step 5. Announce the restart on Discord:
 
 Post something like the following to #announcements (adjusting the text as appropriate):
 
 > Hi @Validators,
 >
-> We've released v1.1.12 and are ready to get TdS back up again.
+> We've released v1.1.12 and are ready to get testnet back up again.
 >
 > Steps:
 > 1. Install the v1.1.12 release: https://github.com/solana-labs/solana/releases/tag/v1.1.12
@@ -49,27 +50,37 @@ Post something like the following to #announcements (adjusting the text as appro
 >
 > ```bash
 > solana-validator
->   --wait-for-supermajority 12961040  # <-- NEW! IMPORTANT!
->   --expected-bank-hash 6q2oTgs8FiJxra2Zo1N8tzWqo5b6uGbjmFgoWDsXxchY    # <-- NEW! IMPORTANT!
->   --hard-fork 56096                  # <-- NEW! IMPORTANT!
->   --entrypoint 35.203.170.30:8001    # <-- Same as before
+>   --wait-for-supermajority SLOT_X     # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
+>   --expected-bank-hash NEW_BANK_HASH  # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
+>   --hard-fork SLOT_X                  # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
+>   --no-snapshot-fetch                 # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
+>   --entrypoint entrypoint.testnet.solana.com:8001
 >   --trusted-validator 5D1fNXzvv5NjV1ysLjirC4WY92RNsVH18vjmcszZd8on
 >   --expected-genesis-hash 4uhcVJyU9pJkvQyS88uRDiswHXSCkY3zQawwpjk2NsNY
 >   --no-untrusted-rpc
 >   --limit-ledger-size
->   --no-snapshot-fetch
->   --no-genesis-fetch
 >   ...                                # <-- your other --identity/--vote-account/etc arguments
 > ```
->   b. If your validator doesn't have ledger up to slot 21042873, have it download a snapshot by removing
->      `--no-snapshot-fetch --no-genesis-fetch --hard-fork 21042873` arguments.
+>   b. If your validator doesn't have ledger up to slot SLOT_X or if you have deleted your ledger, have it instead download a snapshot with:
+> ```bash
+> solana-validator
+>   --wait-for-supermajority SLOT_X     # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
+>   --expected-bank-hash NEW_BANK_HASH  # <-- NEW! IMPORTANT! REMOVE AFTER THIS RESTART
+>   --entrypoint entrypoint.testnet.solana.com:8001
+>   --trusted-validator 5D1fNXzvv5NjV1ysLjirC4WY92RNsVH18vjmcszZd8on
+>   --expected-genesis-hash 4uhcVJyU9pJkvQyS88uRDiswHXSCkY3zQawwpjk2NsNY
+>   --no-untrusted-rpc
+>   --limit-ledger-size
+>   ...                                # <-- your other --identity/--vote-account/etc arguments
+> ```
+>
 >      You can check for which slots your ledger has with: `solana-ledger-tool -l path/to/ledger bounds`
 >
 > 3. Wait until 80% of the stake comes online
 >
 > To confirm your restarted validator is correctly waiting for the 80%:
 > a. Look for `N% of active stake visible in gossip` log messages
-> b. Ask it over RPC what slot it's on: `solana --url http://127.0.0.1:8899 slot`.  It should return `12961040` until we get to 80% stake
+> b. Ask it over RPC what slot it's on: `solana --url http://127.0.0.1:8899 slot`.  It should return `SLOT_X` until we get to 80% stake
 >
 > Thanks!