A batch of docs style fixes.

docs/cygwin_dll_remapping_failure.md

Index: docs/cygwin_dll_remapping_failure.md
diff --git a/docs/cygwin_dll_remapping_failure.md b/docs/cygwin_dll_remapping_failure.md
index 3b56273dd8405d3ba442be07e627009ca1b684f6..468d133ed8ac0fdfaf66b90190f891a81ec72910 100644
--- a/docs/cygwin_dll_remapping_failure.md
+++ b/docs/cygwin_dll_remapping_failure.md
@@ -1,16 +1,15 @@
-Handling repeated failures of rebaseall to allow cygwin remaps
-
-# Introduction
+# Handling repeated failures of rebaseall to allow cygwin remaps
 
 Sometimes DLLs over which cygwin has no control get mapped into cygwin
 processes at locations that cygwin has chosen for its libraries.
-This has been seen primarily with anti-virus DLLs.  When this occurs,
+This has been seen primarily with anti-virus DLLs. When this occurs,
 cygwin must be instructed during the rebase to avoid the area of
 memory where that DLL is mapped.
 
-# Background
+## Background
 
-Some background for this is available on http://www.dont-panic.cc/capi/2007/10/29/git-svn-fails-with-fatal-error-unable-to-remap/
+Some background for this is available on
+http://www.dont-panic.cc/capi/2007/10/29/git-svn-fails-with-fatal-error-unable-to-remap/
 
 Because of unix fork semantics (presumably), cygwin libraries must be
 mapped in the same location in both parent and child of a fork.  All
@@ -34,22 +33,26 @@ To handle this case, you need to figure out what the problematic
 non-cygwin library is, where it is in the address space, and do the
 rebase all so that no cygwin hints map libraries to that location.
 
-# Details
-
-<ul>
-<li>Download the ListDLLs executable from sysinternals<br>
-(<a href='http://technet.microsoft.com/en-us/sysinternals/bb896656.aspx'>http://technet.microsoft.com/en-us/sysinternals/bb896656.aspx</a>)</li>
-<li>Run it as administrator while some cygwin commands are running.</li>
-<li>Scan the output for the cygwin process (identifiable by the command) and for DLLs in that process that do not look like cygwin DLLs (like an AV).  Note the location of those libraries (there will usually only be the one).  Pick an address space location lower than its starting address.</li>
-<li>Quit all cygwin processes.</li>
-<li>Run a windows command shell as administrator</li>
-<li>cd in \cygwin\bin</li>
-<li>Run "ash /usr/bin/rebaseall -b <base address>" (This command can also take a "-v" flag if you want to see the DLL layout.)</li>
-</ul>
-
+## Details
+
+*   Download the ListDLLs executable from
+    [sysinternals](http://technet.microsoft.com/en-us/sysinternals/bb896656.aspx)
+*   Run it as administrator while some cygwin commands are running.
+*   Scan the output for the cygwin process (identifiable by the command) and for
+    DLLs in that process that do not look like cygwin DLLs (like an AV). Note
+    the location of those libraries (there will usually only be the one).
+*   Pick an address space location lower than its starting address.
+*   Quit all cygwin processes.
+*   Run a windows command shell as administrator
+*   cd in \cygwin\bin
+*   Run `ash /usr/bin/rebaseall -b <base address>` (This command can also take a
+    `-v` flag if you want to see the DLL layout.)
 
 That should fix the problem.
 
-# Failed rebaseall
+## Failed rebaseall
 
-If you pick a base address that is too low, you may end up with a broken cygwin install. You can reinstall it by running cygwin's setup.exe again, and on the package selection page, clicking the "All" entry to Reinstall. You may have to do this twice, as you may get errors on the first reinstall pass.
+If you pick a base address that is too low, you may end up with a broken cygwin
+install. You can reinstall it by running cygwin's setup.exe again, and on the
+package selection page, clicking the "All" entry to Reinstall. You may have to
+do this twice, as you may get errors on the first reinstall pass.