Slight reformatting of instructions for submitting a merge so I can find it in the document more easily!

CONTRIBUTING.md

@@ -42,10 +42,17 @@ Setting aside the religious wars that can arise over any development methodology
         git pull
         git checkout my-branch
         git merge master
+    Use `git stash` and `git stash pop` later if needed to hide some changes.
 
 5. If there are any merge conflicts, resolve them and then build and test again. See below for details on resolving conflicts.
 
-6. Push your branch up to gitlab: `git push -u origin my-branch`. Note that `git push` by itself won't push a branch that doesn't exist upstream, so you need to do this the first time you push your branch. After that (if you need to push additional changes later), you can just use `git push`.
+6. Push your branch up to gitlab: 
+
+    ```
+    git push -u origin my-branch
+    ```
+
+    Note that `git push` by itself won't push a branch that doesn't exist upstream, so you need to do this the first time you push your branch. After that (if you need to push additional changes later), you can just use `git push`.
 
 7. Create a merge request describing your proposed change, linking to any issues that it might address, and attaching your branch.
   * On gitlab, create a new merge request from your branch into the upstream's master branch. The "git push" above will helpfully provide you with a direct URL to start this process. (Make sure you're logged into gitlab or you'll get a 404 error.) Otherwise you can do it manually by going to **Merge Requests > New Merge Request** and selecting your branch; upstream master is the default target.