A batch of docs style fixes.

docs/windows_incremental_linking.md

Index: docs/windows_incremental_linking.md
diff --git a/docs/windows_incremental_linking.md b/docs/windows_incremental_linking.md
index 8d0149a3ff97ca700aa4827686266168bc4b76ec..0cf1a395c79da6c12d0d0b10f064d545e228249c 100644
--- a/docs/windows_incremental_linking.md
+++ b/docs/windows_incremental_linking.md
@@ -1,5 +1,15 @@
-Include in your `GYP_DEFINES`: `incremental_chrome_dll=1`. This turns on the equivalent of Use Library Dependency Inputs for the large components in the build.
+# Windows incremental linking
 
-And if you want faster builds, it would be best to include to `component=shared_library` too unless you need a fully static link for some reason.
+Include in your `GYP_DEFINES`: `incremental_chrome_dll=1`. This turns on the
+equivalent of Use Library Dependency Inputs for the large components in the
+build.
 
-Note that `incremental_chrome_dll=1` will probably not work on Visual Studio 2008 builds.  It may not work on Visual Studio 2010 builds either (pamg couldn't get it to work as of Nov 2012, encountering numerous link errors).  You may have to use [ninja](http://code.google.com/p/chromium/wiki/NinjaBuild), which has incremental linking on by default.
+And if you want faster builds, it would be best to include to
+`component=shared_library` too unless you need a fully static link for some
+reason.
+
+Note that `incremental_chrome_dll=1` will probably not work on Visual Studio
+2008 builds. It may not work on Visual Studio 2010 builds either (pamg couldn't
+get it to work as of Nov 2012, encountering numerous link errors). You may have
+to use [ninja](http://code.google.com/p/chromium/wiki/NinjaBuild), which has
+incremental linking on by default.