Update docs/cdk/how-to/migrate/7-8.md

Author: kmurphypolygon

docs/cdk/how-to/migrate/7-8.md

@@ -5,24 +5,6 @@ This document shows Polygon partners how to migrate a CDK stack from fork 7 to f
 
 ## Process to upgrade from fork 7 to 8 for isolated CDK chains
 
-1. CDK owners make an upgrade request to Polygon.
-
-2. Polygon schedules the update transaction, and informs the owners of the date and time that the timelock delay expires, after which point the upgrade can go ahead.
-
-3. Polygon and CDK owners agree upon a time window for the upgrade.
-
-4. During the agreed time window, CDK operators ensure that all the batches of the system are verified. Follow the [verify all batches](#verify-all-batches) instructions below to do that. 
-
-    !!! warning
-        The current batch verification procedure relies on stopping the sequencer.
-
-5. After successful batch verification, CDK operators inform Polygon that their CDK is ready for the upgrade.
-
-6. Polygon executes the scheduled transaction on the timelock, making the upgrade effective.
-
-7. Polygon informs the CDK operators of the transaction confirmation. (It is also possible to check Etherscan for confirmation of the same.)
-
-8. CDK operators update the software and restart all components. Follow the [update software](#update-software) instructions below.
 In order to avoid reorgs and other undesirable scenarios, all L2 transactions must be verified before upgrading a fork. Verification means that all batches are closed, sequenced, and verified on L1.
 
 Follow the steps to verify all batches for upgrading from fork 7 to 8.