Documentation-update-process.md

@@ -20,17 +20,18 @@ When you save your changes version, GitHub automatically creates a fork (if it d
 
 0. This is part of the [[Release process checklist]].
 1. Clone the repository `git clone https://github.com/mathjax/mathjax-docs.git`
-1. Create a branch corresponding to the **current** version, i.e., the version that will be replaced by the new release.
-1. In that "current" branch, modify
-    * the edit-on-github link `_templates/sourcelink.html` to point to the "current" branch.
+1. Create a branch `current` corresponding to the **current** version, i.e., the version that will be replaced by the new release.
+1. In the `current` branch, modify
+    * the edit-on-github link `_templates/sourcelink.html` to point to the `current` branch.
     * the theme layout `_themes/sphinx-bootstrap/layout.html`: add the version-warning to the quick-links:
         * After `<li><strong>Quick links</strong></li>` insert `<li> <a class="btn btn-mini btn-success" href="http://docs.mathjax.org/">Newer version available!</a> </li>`
 1. Commit & push pack to github: `git commit -a -m "(log message about the 'current' branch)" && 
- git push origin (current branch)`
-1. Checkout the `master` branch,
+ git push origin "current"`
+1. Then checkout the `master` branch,
      * update the version number in the Sphinx configuration file `config.py`.
 1. Commit & push pack to github: `git commit -a -m "(log message about version change)" && 
  git push origin master`
+1. Visit the user page on ReadTheDocs and check that `current` branch is included in the build list.
 
 ### Appendix: Understanding the process