Fixed ref and switched to code-black::bash for rpyc-release-process.rst

docs/docs/rpyc-release-process.rst

@@ -3,7 +3,7 @@ RPyC Release Process
 
 A walkthrough of doing a RPyC Release.
 
-1. Describe commit history within `CHANGELOG.rst` (i.e. :ref:`Generate Entry<Generate CHANGELOG.rst Entry>`)
+1. Describe commit history within `CHANGELOG.rst` (see `Generate Entry`_)
 2. Update `version` and `release_date` values for `rpyc/version.py` (`Semantic Versioning`_)
 3. Review `git status`, commit changes, and `git push`.
 4. Create an Annotated tag: `git tag -a 5.X.Y -m "Updated CHANGELOG.rst and version for release 5.X.Y"`
@@ -15,10 +15,14 @@ A walkthrough of doing a RPyC Release.
 
 .. _Semantic Versioning: https://semver.org/
 
+.. _Generate Entry:
+
 Generate CHANGELOG.rst Entry
 ---------------------------------
 To create an initial entry draft, run some shell commands.
 
+.. code-block:: bash
+
     last_release="1/12/2021"
     log_since="$(git log --since="${last_release}" --merges --oneline)"
     pulls=( $(echo "${log_since}" | sed -n 's/^.*request #\([0-9]*\) from .*$/\1/p') )
@@ -35,6 +39,8 @@ To create an initial entry draft, run some shell commands.
 
 Once insert this entry at the top of `CHANGELOG.rst`, review what it looks like with `instant-rst`.
 
+.. code-block:: bash
+
     instantRst -b chromium -p 8612 -f "CHANGELOG.rst"