release-process: fixes

Signed-off-by: Maël Valais <[email protected]>

content/docs/contributing/release-process.md

@@ -475,10 +475,10 @@ page if a step is missing or if it is outdated.
    EOF
    ```
 
-   Finally, get back to the main tag:
+   Finally, get back to the branch you were on initially:
 
    ```bash
-   git checkout $RELEASE_VERSION
+   git checkout $BRANCH
    ```
 
 10. In this section, we will be creating the description for the GitHub Release.
@@ -575,9 +575,9 @@ page if a step is missing or if it is outdated.
     2. While the build is running, send a third Slack message in reply to the
        first message:
 
-    <div className="pageinfo pageinfo-primary"><p>
-    Follow the `cmrel publish` dry-run build: https://console.cloud.google.com/cloud-build/builds16f6f875-0a23-4fff-b24d-3de0af207463?project=1021342095237
-    </p></div>
+        <div className="pageinfo pageinfo-primary"><p>
+        Follow the `cmrel publish` dry-run build: https://console.cloud.google.com/cloud-build/builds16f6f875-0a23-4fff-b24d-3de0af207463?project=1021342095237
+        </p></div>
 
     3. Now publish the release artifacts for real. The following command will
        publish the artifacts to GitHub, `Quay.io` and to our
@@ -603,9 +603,9 @@ page if a step is missing or if it is outdated.
     4. While the build is running, send a fourth Slack message in reply to the
        first message:
 
-    <div className="pageinfo pageinfo-primary"><p>
-    Follow the <code>cmrel publish</code> build: https://console.cloud.google.com/cloud-build/builds/b6fef12b-2e81-4486-9f1f-d00592351789?project=1021342095237
-    </p></div>
+        <div className="pageinfo pageinfo-primary"><p>
+        Follow the <code>cmrel publish</code> build: https://console.cloud.google.com/cloud-build/builds/b6fef12b-2e81-4486-9f1f-d00592351789?project=1021342095237
+        </p></div>
 
 13. Publish the GitHub release: