diff --git a/release_process.md b/release_process.md
index 017b7a491..a4e304b5b 100644
--- a/release_process.md
+++ b/release_process.md
@@ -51,14 +51,12 @@ 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.
+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.
 
-Now, let's dive deeper into how to achieve each step from the list above.
-
-### 1. Upgrade the factory from v2 to v3.
+### 1. Upgrade the factory from v2 to v3
 
 This should be done in the following order:
 - 1. testnet, using a personal account