add jump to sections

release_process.md

@@ -51,14 +51,13 @@ Since this is the first time that the factory and the DAO are being upgraded and
 
 ## v3 Release Plan
 
-#### 1. Upgrade the factory from v2 to v3 and then set up the default code for the DAO to be v2.
-#### 2. After we get enough confidence using factory v3 and DAO v2, change the default code for the DAO from v2 to v3.
-#### 3. New DAOs will get created using the v3 code that should include all the fixes and the new features.
-#### 4. Existing DAOs will need to migrate from v2 to v3.
+1. [Upgrade the factory from v2 to v3 and then set up the default code for the DAO to be v2.](#upgrade-the-factory-from-v2-to-v3)
+2. [After we get enough confidence using factory v3 and DAO v2, change the default code for the DAO from v2 to v3.](#change-dao-default-code-from-v2-to-v3)
+3. [Existing DAOs will need to migrate from v2 to v3.](#migrate-dao-from-v2-to-v3)
 
-Now, let's dive deeper into how to achieve each step from the list above.
+---
 
-### 1. Upgrade the factory from v2 to v3.
+### Upgrade the factory from v2 to v3
 
 This should be done in the following order:
 - 1. testnet, using a personal account 
@@ -192,8 +191,9 @@ Please note that the DAO itself is still v2. The only difference is that the DAO
 
 The process is very similar with 1.2.
 
+---
 
-### 2. After we get enough confidence using factory v3 and DAO v2, change the default code for the DAO from v2 to v3.
+### Change DAO default code from v2 to v3
 
 After a few weeks of running factory v3 + DAO v2, it's time to step up the game and upgrade the default DAO version to v3.
 
@@ -246,7 +246,9 @@ The DAO that gets created should be a brand new v3 DAO.
 
 The process is very similar with 2.1.
 
-### 4. Existing DAOs will need to migrate from v2 to v3.
+---
+
+### Migrate DAO from v2 to v3
 
 Assumptions:
 - we are the trying to upgrade `amber.sputnik-dao.near` from v2 to v3