Link directly to each section header

This gets more of the document on the page immediately, rather than
requiring scrolling past the top part of GitHub's UI.

Author: randycoulman

docs/1-installation.md

@@ -102,4 +102,4 @@ QUnit.testDone(function() {
 ```
 
 ***
-Next:  [Purpose](2-howto-purpose.md)
+Next:  [Purpose](2-howto-purpose.md#purpose)

docs/2-howto-purpose.md

@@ -111,5 +111,5 @@ integrated test suite and afford some opportunity for responding to hard-to-test
 situations by improving the API design of your adapters.
 
 ***
-Previous: [Installing testdouble.js](1-installation.md)
-Next:  [Getting Started](3-getting-started.md)
+Previous: [Installing testdouble.js](1-installation.md#installing-testdoublejs)
+Next:  [Getting Started](3-getting-started.md#getting-started)

docs/3-getting-started.md

@@ -356,5 +356,5 @@ Further reading that documents the features shown off in this tutorial include:
 * [Verifying invocations with `verify()`](6-verifying-invocations.md)
 
 ***
-Previous: [Purpose](2-howto-purpose.md)
-Next: [Creating Test Doubles](4-creating-test-doubles.md)
+Previous: [Purpose](2-howto-purpose.md#purpose)
+Next: [Creating Test Doubles](4-creating-test-doubles.md#creating-test-doubles)

docs/4-creating-test-doubles.md

@@ -225,5 +225,5 @@ FakeCat.prototype.scratch // a test double function named '#scratch'
 As you can see, there are a plethora of ways to create test doubles with testdouble.js, each designed to handle a different style of organizing JavaScript code. We recommend on landing on one consistent style (e.g. each module as one function) for each project, which in turn would encourage one consistent style of creating test doubles. This API is written to be flexible for a number of potential contexts across objects, but it has come at the cost of a large enough surface area that if any project were to make ample use of all or most of the above invocation styles, it would confuse readers.
 
 ***
-Previous: [Getting Started](3-getting-started.md)
-Next: [Stubbing behavior](5-stubbing-results.md)
+Previous: [Getting Started](3-getting-started.md#getting-started)
+Next: [Stubbing behavior](5-stubbing-results.md#stubbing-behavior)

docs/5-stubbing-results.md

@@ -624,5 +624,5 @@ on about [verifying interactions with `verify()`](6-verifying-invocations.md),
 and rest easy knowing that you already know exactly how to do it.
 
 ***
-Previous: [Creating Test Doubles](4-creating-test-doubles.md)
-Next: [Verifying interactions](6-verifying-invocations.md)
+Previous: [Creating Test Doubles](4-creating-test-doubles.md#creating-test-doubles#creating-test-doubles)
+Next: [Verifying interactions](6-verifying-invocations.md#verifying-interactions)

docs/6-verifying-invocations.md

@@ -375,5 +375,5 @@ testdouble.js! At this point, you know everything you need to know to be pretty
 dangerous writing isolated tests.
 
 ***
-Previous: [Stubbing behavior](5-stubbing-results.md)
-Next: [Replacing Real Dependencies with Test Doubles](7-replacing-dependencies.md)
+Previous: [Stubbing behavior](5-stubbing-results.md#stubbing-behavior)
+Next: [Replacing Real Dependencies with Test Doubles](7-replacing-dependencies.md#replacing-real-dependencies-with-test-doubles)

docs/7-replacing-dependencies.md

@@ -229,5 +229,5 @@ to short-circuit any attempts to load and imitate a module at
 `relativePathToModule`.
 
 ***
-Previous: [Verifying interactions](6-verifying-invocations.md)
-Next: [Custom argument matchers](8-custom-matchers.md)
+Previous: [Verifying interactions](6-verifying-invocations.md#verifying-interactions)
+Next: [Custom argument matchers](8-custom-matchers.md#custom-argument-matchers)

docs/8-custom-matchers.md

@@ -66,5 +66,5 @@ For some examples of `td.matchers.create()` in action, check out the
 [built-in matchers](src/matchers/index.coffee) provided by testdouble.js.
 
 ***
-Previous: [Replacing Real Dependencies with Test Doubles](7-replacing-dependencies.md)
-Next: [Debugging with testdouble.js](9-debugging.md)
+Previous: [Replacing Real Dependencies with Test Doubles](7-replacing-dependencies.md#replacing-real-dependencies-with-test-doubles)
+Next: [Debugging with testdouble.js](9-debugging.md#debugging-with-testdoublejs)

docs/9-debugging.md

@@ -80,5 +80,5 @@ to make [`explain` describe test double objects](https://github.com/testdouble/t
 in addition to functions.
 
 ***
-Previous: [Custom argument matchers](8-custom-matchers.md)
-Next: [Plugins](A-plugins.md)
+Previous: [Custom argument matchers](8-custom-matchers.md#custom-argument-matchers)
+Next: [Plugins](A-plugins.md#plugins)

docs/A-plugins.md

@@ -25,14 +25,14 @@ Jasmine `expect` matchers (WIP by @BrianGenisio)
 
 ## Build Plugins
 
-Sometimes, it can be handy to have a ready-made shim to pull in and configure the 
+Sometimes, it can be handy to have a ready-made shim to pull in and configure the
 library for various build tools. Here's what testdouble.js has so far:
 
-* [ember-cli-testdouble](https://github.com/isleofcode/ember-cli-testdouble) by 
-[@AlexBlom](https://github.com/AlexBlom) provides a shim for easy importing of 
+* [ember-cli-testdouble](https://github.com/isleofcode/ember-cli-testdouble) by
+[@AlexBlom](https://github.com/AlexBlom) provides a shim for easy importing of
 testdouble.js by Ember projects that using Ember CLI
-* [karma-testdouble](https://github.com/kahwee/karma-testdouble) by 
-[@kahwee](https://github.com/kahwee) will configure 
+* [karma-testdouble](https://github.com/kahwee/karma-testdouble) by
+[@kahwee](https://github.com/kahwee) will configure
 [Karma](https://karma-runner.github.io) to load test double's browser
 distribution
 
@@ -48,5 +48,5 @@ This API has been ported for use with testdouble.js by
 [testdouble-timers](https://github.com/kuy/testdouble-timers).
 
 ***
-Previous: [Debugging with testdouble.js](9-debugging.md)
-Next: [Frequently Asked Questions](B-frequently-asked-questions.md)
+Previous: [Debugging with testdouble.js](9-debugging.md#debugging-with-testdoublejs)
+Next: [Frequently Asked Questions](B-frequently-asked-questions.md#frequently-asked-questions)