Yet another ``` user

ReleaseChecklist.md

@@ -27,8 +27,7 @@ I wrote up this document as a checklist of stuff to do before putting out a Libe
  * Set some variables. In the instructions below, I'll assume that you have set:
    * `LAST_TAG=release-2.0.17-stable`
    * `NEW_TAG=release-2.0.18-stable`
- * Generate the changelog.  For generating the contents of the changelog, you can get something pretty close to what we've done in the past by saying:
-	 git log --no-merges --reverse --pretty='format: o %s (%h %an)' ${LAST_TAG}..HEAD | perl -pe 's/ \(Nick Mathewson)\)$/\)/'
+ * Generate the changelog.  For generating the contents of the changelog, you can get something pretty close to what we've done in the past by saying: `git log --no-merges --reverse --pretty='format: o %s (%h %an)' ${LAST_TAG}..HEAD | perl -pe 's/ \(Nick Mathewson)\)$/\)/'`
  * Generate the credits.   I like to use `git log ${LAST_TAG}..HEAD --pretty='format:%an' > names` for everybody whose name is on a commit, then `git log ${LAST_TAG}..HEAD | perl -ne 'if (/([A-Z]\w* [A-Z]\w*)/) { print "$1\n"; }' >> names` to get all the namelike sequences in the log.  Then I use a `sort -k2 | uniq` pipeline to sort and uniqueify them. These names get stuck in the list in the `README`, and in the announcement. {NOTE: The `perl` snippet above is }
  * Increment the version number and version string in configure.in. The next version should be 2.0.18-stable; the numeric version should be `0x02001200` (That is, 02 00 12 00 : the first three bytes are the version number, and the final 00 byte means that this is the actual release of 2.0.18, not some development version between 2.0.18 and 2.0.19.)
  * Increment the version number and string in `WIN32-Code/nmake/event2/event-config.h`.  (These are not automatically changed by configure.in, since we don't use `autoconf` with `nmake`.)