Replace broken internal links with page links.

sinonjs · Feb 26, 2017 · c9367aa · c9367aa
1 parent 592dffc
commit c9367aa
Show file tree

Hide file tree

Showing 16 changed files with 16 additions and 16 deletions.
diff --git a/docs/_releases/v1.17.6/mocks.md b/docs/_releases/v1.17.6/mocks.md
@@ -28,7 +28,7 @@ Thus, they enforce implementation details. The rule of thumb is: if you wouldn't
 
 In general you should have **no more than one** mock (possibly with several expectations) in a single test.
 
-[Expectations](#expectations) implement both the [spies](#spies) and [stubs](#stubs) APIs.
+[Expectations](#expectations) implement both the [spies](../spies) and [stubs](../stubs) APIs.
 
 To see what mocks look like in Sinon.JS, here is one of the [PubSubJS][pubsubjs] tests again, this time using a method as callback and using mocks to verify its behavior
 

diff --git a/docs/_releases/v1.17.6/stubs.md b/docs/_releases/v1.17.6/stubs.md
@@ -8,7 +8,7 @@ breadcrumb: stubs
 
 Test stubs are functions (spies) with pre-programmed behavior.
 
-They support the full <a href="#spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
+They support the full <a href="../spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
 
 As spies, stubs can be either anonymous, or wrap existing functions. When
 wrapping an existing function with a stub, the original function is not called.

diff --git a/docs/_releases/v1.17.6/utils.md b/docs/_releases/v1.17.6/utils.md
@@ -32,7 +32,7 @@ Restores supplied method
 
 Creates a new object with the given function as the protoype and stubs all implemented functions.
 
-The given constructor function is not invoked. See also the [stub API](#stubs).
+The given constructor function is not invoked. See also the [stub API](../stubs).
 
 #### `sinon.format(object);`
 

diff --git a/docs/_releases/v1.17.7/mocks.md b/docs/_releases/v1.17.7/mocks.md
@@ -28,7 +28,7 @@ Thus, they enforce implementation details. The rule of thumb is: if you wouldn't
 
 In general you should have **no more than one** mock (possibly with several expectations) in a single test.
 
-[Expectations](#expectations) implement both the [spies](#spies) and [stubs](#stubs) APIs.
+[Expectations](#expectations) implement both the [spies](../spies) and [stubs](../stubs) APIs.
 
 To see what mocks look like in Sinon.JS, here is one of the [PubSubJS][pubsubjs] tests again, this time using a method as callback and using mocks to verify its behavior
 

diff --git a/docs/_releases/v1.17.7/stubs.md b/docs/_releases/v1.17.7/stubs.md
@@ -8,7 +8,7 @@ breadcrumb: stubs
 
 Test stubs are functions (spies) with pre-programmed behavior.
 
-They support the full <a href="#spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
+They support the full <a href="../spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
 
 As spies, stubs can be either anonymous, or wrap existing functions. When
 wrapping an existing function with a stub, the original function is not called.

diff --git a/docs/_releases/v1.17.7/utils.md b/docs/_releases/v1.17.7/utils.md
@@ -32,7 +32,7 @@ Restores supplied method
 
 Creates a new object with the given function as the protoype and stubs all implemented functions.
 
-The given constructor function is not invoked. See also the [stub API](#stubs).
+The given constructor function is not invoked. See also the [stub API](../stubs).
 
 #### `sinon.format(object);`
 

diff --git a/docs/_releases/v2.0.0-pre.4/mocks.md b/docs/_releases/v2.0.0-pre.4/mocks.md
@@ -28,7 +28,7 @@ Thus, they enforce implementation details. The rule of thumb is: if you wouldn't
 
 In general you should have **no more than one** mock (possibly with several expectations) in a single test.
 
-[Expectations](#expectations) implement both the [spies](#spies) and [stubs](#stubs) APIs.
+[Expectations](#expectations) implement both the [spies](../spies) and [stubs](../stubs) APIs.
 
 To see what mocks look like in Sinon.JS, here is one of the [PubSubJS][pubsubjs] tests again, this time using a method as callback and using mocks to verify its behavior
 

diff --git a/docs/_releases/v2.0.0-pre.4/stubs.md b/docs/_releases/v2.0.0-pre.4/stubs.md
@@ -8,7 +8,7 @@ breadcrumb: stubs
 
 Test stubs are functions (spies) with pre-programmed behavior.
 
-They support the full <a href="#spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
+They support the full <a href="../spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
 
 As spies, stubs can be either anonymous, or wrap existing functions. When
 wrapping an existing function with a stub, the original function is not called.

diff --git a/docs/_releases/v2.0.0-pre.4/utils.md b/docs/_releases/v2.0.0-pre.4/utils.md
@@ -32,7 +32,7 @@ Restores supplied method
 
 Creates a new object with the given function as the protoype and stubs all implemented functions.
 
-The given constructor function is not invoked. See also the [stub API](#stubs).
+The given constructor function is not invoked. See also the [stub API](../stubs).
 
 #### `sinon.format(object);`
 

diff --git a/docs/_releases/v2.0.0-pre.5/mocks.md b/docs/_releases/v2.0.0-pre.5/mocks.md
@@ -28,7 +28,7 @@ Thus, they enforce implementation details. The rule of thumb is: if you wouldn't
 
 In general you should have **no more than one** mock (possibly with several expectations) in a single test.
 
-[Expectations](#expectations) implement both the [spies](#spies) and [stubs](#stubs) APIs.
+[Expectations](#expectations) implement both the [spies](../spies) and [stubs](../stubs) APIs.
 
 To see what mocks look like in Sinon.JS, here is one of the [PubSubJS][pubsubjs] tests again, this time using a method as callback and using mocks to verify its behavior
 

diff --git a/docs/_releases/v2.0.0-pre.5/stubs.md b/docs/_releases/v2.0.0-pre.5/stubs.md
@@ -8,7 +8,7 @@ breadcrumb: stubs
 
 Test stubs are functions (spies) with pre-programmed behavior.
 
-They support the full <a href="#spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
+They support the full <a href="../spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
 
 As spies, stubs can be either anonymous, or wrap existing functions. When
 wrapping an existing function with a stub, the original function is not called.

diff --git a/docs/_releases/v2.0.0-pre.5/utils.md b/docs/_releases/v2.0.0-pre.5/utils.md
@@ -32,7 +32,7 @@ Restores supplied method
 
 Creates a new object with the given function as the protoype and stubs all implemented functions.
 
-The given constructor function is not invoked. See also the [stub API](#stubs).
+The given constructor function is not invoked. See also the [stub API](../stubs).
 
 #### `sinon.format(object);`
 

diff --git a/docs/api/v2.0.0/stubs/index.md b/docs/api/v2.0.0/stubs/index.md
@@ -7,7 +7,7 @@ title: Stubs
 
 Test stubs are functions (spies) with pre-programmed behavior.
 
-They support the full <a href="#spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
+They support the full <a href="../spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
 
 As spies, stubs can be either anonymous, or wrap existing functions. When
 wrapping an existing function with a stub, the original function is not called.

diff --git a/docs/release-source/release/mocks.md b/docs/release-source/release/mocks.md
@@ -28,7 +28,7 @@ Thus, they enforce implementation details. The rule of thumb is: if you wouldn't
 
 In general you should have **no more than one** mock (possibly with several expectations) in a single test.
 
-[Expectations](#expectations) implement both the [spies](#spies) and [stubs](#stubs) APIs.
+[Expectations](#expectations) implement both the [spies](../spies) and [stubs](../stubs) APIs.
 
 To see what mocks look like in Sinon.JS, here is one of the [PubSubJS][pubsubjs] tests again, this time using a method as callback and using mocks to verify its behavior
 

diff --git a/docs/release-source/release/stubs.md b/docs/release-source/release/stubs.md
@@ -8,7 +8,7 @@ breadcrumb: stubs
 
 Test stubs are functions (spies) with pre-programmed behavior.
 
-They support the full <a href="#spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
+They support the full <a href="../spies">test spy API</a> in addition to methods which can be used to alter the stub's behavior.
 
 As spies, stubs can be either anonymous, or wrap existing functions. When
 wrapping an existing function with a stub, the original function is not called.

diff --git a/docs/release-source/release/utils.md b/docs/release-source/release/utils.md
@@ -32,7 +32,7 @@ Restores supplied method
 
 Creates a new object with the given function as the protoype and stubs all implemented functions.
 
-The given constructor function is not invoked. See also the [stub API](#stubs).
+The given constructor function is not invoked. See also the [stub API](../stubs).
 
 #### `sinon.format(object);`