Documentation-update-process.md

@@ -34,7 +34,7 @@ When you save your changes version, GitHub automatically creates a fork (if it d
 1. Merge `vN.m-latest` back into `master`.
 1. Push `vN.m-latest` and `master` back to github.  `git push origin master vN.m-latest`
 1. After(!) the release, modify the `vN.m-latest` branch (Note: this branch will have to be updated updated manually but will allow people to have a stable link for documentation of that version)
-    * the edit-on-github link `_templates/sourcelink.html` to point to the `current` branch.
+    * the edit-on-github link `_templates/sourcelink.html` to point to the `current` branch. ((**pkra:** this may be unnecessary, I think rtfd now adds it to the sidebar and this might not have any effect anymore))
     * 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>` (this may seem counter-intuitive, but `latest` is designed to be more up-to-date.
 1. Commit & push pack to github: `git commit -a -m "(log message about the new release branch)" &&