Try to fix problems with MkDocs rendering

Author: mpilgrem

doc/maintainers/releases.md

@@ -45,25 +45,13 @@ Examples:
 * `1.7.0.2`: continuing development on pre-release branch
 * `1.7.0.3`: second release candidate for first release of v1.7.x series (`v1.7`
   branch)
-
-
-
 * `1.7.1`: first release of the 1.7.x series (`release` branch)
-
-
-
 * `1.7.2.0`: development for second release of 1.7.x series (`stable` branch)
 * `1.7.2.1`: release candidate for second release of 1.7.x series (`stable`
   branch)
-
-
-
 * `1.7.3`: second release of 1.7.x series (`release` branch)
 * `1.7.3.1`: first hackage-only patch of 1.7.3 (`release` branch)
 * `1.7.3.2`: second hackage-only patch of 1.7.3 (`release` branch)
-
-
-
 * `1.8.0`: unstable development code (`master` branch)
 * `1.8.0.20181004`: pre-release snapshot of unstable version (`master` branch)
 
@@ -80,10 +68,7 @@ Examples:
    nightly (go over the extra-deps too) and ensure the project builds and tests
    pass. For example:
 
-
-       ~~~
-       $ stack build --stack-yaml=… --haddock --test --bench --no-run-benchmarks
-       ~~~
+        $ stack build --stack-yaml=… --haddock --test --bench --no-run-benchmarks
 
 7. Ensure integration tests pass on a Windows, macOS, and Linux. Do so by
    checking that the latest nightly build for the `master` branch succeeded in
@@ -117,8 +102,6 @@ branch.
       will be the next final (non-RC) release (e.g. `v2.1.1`).
     * add new "Unreleased changes" section:
 
-
-            ~~~
             ## Unreleased changes
 
             Release notes:
@@ -132,7 +115,6 @@ branch.
             Other enhancements:
 
             Bug fixes:
-            ~~~
 
 ### D: In the release candidate branch
 
@@ -241,9 +223,7 @@ Edit the draft
   to the release and add it to the description. For example, use:
 
 
-        ~~~
         $ git shortlog -s origin/release..HEAD|sed $'s/^[0-9 \t]*/* /'|grep -v azure-pipelines|LC_ALL=C sort -f
-        ~~~
 
 Publish the GitHub release.
 
@@ -316,8 +296,6 @@ In either the `stable` branch or, in the case of a release candidate, the
 * `ChangeLog.md`: Add an “Unreleased changes” section (update the “changes
   since” version):
 
-
-        ~~~
         ## Unreleased changes
 
         Release notes:
@@ -331,7 +309,6 @@ In either the `stable` branch or, in the case of a release candidate, the
         Other enhancements:
 
         Bug fixes:
-        ~~~
 
 ### G: Update the repository's issue and pull request templates
 
@@ -367,24 +344,16 @@ Update the fpco/stack-build Docker images with new version:
   released Stack version):
 
 
-        ~~~
         FROM $DOCKER_REPO:lts-X.Z
         ARG STACK_VERSION=X.Y.Z
         RUN wget -qO- https://github.com/commercialhaskell/stack/releases/download/v$STACK_VERSION/stack-$STACK_VERSION-linux-x86_64.tar.gz | tar xz --wildcards --strip-components=1 -C /usr/local/bin '*/stack'
-        ~~~
 
 * Run `./build.sh lts-X.Y` and then test that the new image has the new version
   of Stack. For example:
 
-
-        ~~~
         $ docker run --rm fpco/stack-build:lts stack --version
-        ~~~
 
 * Run the following command to push the new image to the registry:
 
-
-        ~~~
         $ ./build.sh --push lts-X.Y
         $ ./build.sh --push --small lts-X.Y
-        ~~~