Fix apostrophe typos (#1454)

Changelog.txt

@@ -939,7 +939,7 @@ v2.0.0-pre.5 / 2016-12-31
 * Switched indentation from 2 to 4 spaces :)
 * Node.js compatibility improvements
 * Remove magic booleans from sinon.assert.expose, replace with option object
-* Put QUnit adapter in it's own repository
+* Put QUnit adapter in its own repository
 * Update build script to build standalone timers and server files
 * Breaking change: thisObj -> thisValue
   Change brings consistency to the code-base, always use thisValue

docs/README.md

@@ -10,7 +10,7 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for details on contributing documentation
 
 ## Documentation release process
 
-Whenever a new release is created using `npm version`, the tree from `release-source/release/` is copied into it's own folder under `releases/` with an appropriate name.
+Whenever a new release is created using `npm version`, the tree from `release-source/release/` is copied into its own folder under `releases/` with an appropriate name.
 
 Likewise, the `_releases/release.md` file is copied into a file matching the release name.
 

docs/_releases/v1.17.6/spies.md

@@ -134,7 +134,7 @@ first call. There are two ways of achieving this:
 ```
 
 The first example uses the two-dimensional `args` array directly on the spy,
-while the second example fetches the first call object and then accesses it's
+while the second example fetches the first call object and then accesses its
 `args` array. Which one to use is a matter of preference, but the recommended
 approach is going with `spy.calledWith(arg1, arg2, ...)` unless there's a need
 to make the tests highly specific.

docs/_releases/v1.17.7/spies.md

@@ -134,7 +134,7 @@ first call. There are two ways of achieving this:
 ```
 
 The first example uses the two-dimensional `args` array directly on the spy,
-while the second example fetches the first call object and then accesses it's
+while the second example fetches the first call object and then accesses its
 `args` array. Which one to use is a matter of preference, but the recommended
 approach is going with `spy.calledWith(arg1, arg2, ...)` unless there's a need
 to make the tests highly specific.

docs/_releases/v2.0.0/fake-timers.md

@@ -54,7 +54,7 @@ As above, but rather than starting the clock with a timestamp of 0, start at the
 
 *Since `sinon@2.0.0`*
 
-You can also pass in a Date object, and it's `getTime()` will be used for the starting timestamp.
+You can also pass in a Date object, and its `getTime()` will be used for the starting timestamp.
 
 #### `var clock = sinon.useFakeTimers([now, ]prop1, prop2, ...);`
 

docs/_releases/v2.0.0/migrating-to-2.0.md

@@ -64,7 +64,7 @@ The following utility functions are being marked as deprecated and are planned f
 
 ## `sandbox.useFakeXMLHttpRequest` no longer returns a "server"
 
-In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as it's `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
+In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as its `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
 
 ## `sinon.behavior` is gone
 

docs/_releases/v2.0.0/spies.md

@@ -134,7 +134,7 @@ first call. There are two ways of achieving this:
 ```
 
 The first example uses the two-dimensional `args` array directly on the spy,
-while the second example fetches the first call object and then accesses it's
+while the second example fetches the first call object and then accesses its
 `args` array. Which one to use is a matter of preference, but the recommended
 approach is going with `spy.calledWith(arg1, arg2, ...)` unless there's a need
 to make the tests highly specific.

docs/_releases/v2.0.0/stubs.md

@@ -453,7 +453,7 @@ Same as their corresponding non-Async counterparts, but with callback being defe
 
 #### `sinon.addBehavior(name, fn);`
 
-Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, it's return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
+Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, its return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
 
 ```javascript
 const sinon = require('sinon');

docs/_releases/v2.1.0/fake-timers.md

@@ -54,7 +54,7 @@ As above, but rather than starting the clock with a timestamp of 0, start at the
 
 *Since `sinon@2.0.0`*
 
-You can also pass in a Date object, and it's `getTime()` will be used for the starting timestamp.
+You can also pass in a Date object, and its `getTime()` will be used for the starting timestamp.
 
 #### `var clock = sinon.useFakeTimers([now, ]prop1, prop2, ...);`
 

docs/_releases/v2.1.0/migrating-to-2.0.md

@@ -64,7 +64,7 @@ The following utility functions are being marked as deprecated and are planned f
 
 ## `sandbox.useFakeXMLHttpRequest` no longer returns a "server"
 
-In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as it's `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
+In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as its `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
 
 ## `sinon.behavior` is gone
 

docs/_releases/v2.1.0/spies.md

@@ -134,7 +134,7 @@ first call. There are two ways of achieving this:
 ```
 
 The first example uses the two-dimensional `args` array directly on the spy,
-while the second example fetches the first call object and then accesses it's
+while the second example fetches the first call object and then accesses its
 `args` array. Which one to use is a matter of preference, but the recommended
 approach is going with `spy.calledWith(arg1, arg2, ...)` unless there's a need
 to make the tests highly specific.

docs/_releases/v2.1.0/stubs.md

@@ -436,7 +436,7 @@ Same as their corresponding non-Async counterparts, but with callback being defe
 
 #### `sinon.addBehavior(name, fn);`
 
-Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, it's return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
+Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, its return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
 
 ```javascript
 const sinon = require('sinon');

docs/_releases/v2.2.0/fake-timers.md

@@ -54,7 +54,7 @@ As above, but rather than starting the clock with a timestamp of 0, start at the
 
 *Since `sinon@2.0.0`*
 
-You can also pass in a Date object, and it's `getTime()` will be used for the starting timestamp.
+You can also pass in a Date object, and its `getTime()` will be used for the starting timestamp.
 
 #### `var clock = sinon.useFakeTimers([now, ]prop1, prop2, ...);`
 

docs/_releases/v2.2.0/migrating-to-2.0.md

@@ -64,7 +64,7 @@ The following utility functions are being marked as deprecated and are planned f
 
 ## `sandbox.useFakeXMLHttpRequest` no longer returns a "server"
 
-In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as it's `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
+In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as its `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
 
 ## `sinon.behavior` is gone
 

docs/_releases/v2.2.0/spies.md

@@ -134,7 +134,7 @@ first call. There are two ways of achieving this:
 ```
 
 The first example uses the two-dimensional `args` array directly on the spy,
-while the second example fetches the first call object and then accesses it's
+while the second example fetches the first call object and then accesses its
 `args` array. Which one to use is a matter of preference, but the recommended
 approach is going with `spy.calledWith(arg1, arg2, ...)` unless there's a need
 to make the tests highly specific.

docs/_releases/v2.2.0/stubs.md

@@ -474,7 +474,7 @@ Same as their corresponding non-Async counterparts, but with callback being defe
 
 #### `sinon.addBehavior(name, fn);`
 
-Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, it's return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
+Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, its return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
 
 ```javascript
 const sinon = require('sinon');

docs/_releases/v2.3.0/fake-timers.md

@@ -54,7 +54,7 @@ As above, but rather than starting the clock with a timestamp of 0, start at the
 
 *Since `sinon@2.0.0`*
 
-You can also pass in a Date object, and it's `getTime()` will be used for the starting timestamp.
+You can also pass in a Date object, and its `getTime()` will be used for the starting timestamp.
 
 #### `var clock = sinon.useFakeTimers([now, ]prop1, prop2, ...);`
 

docs/_releases/v2.3.0/migrating-to-2.0.md

@@ -65,7 +65,7 @@ The following utility functions are being marked as deprecated and are planned f
 
 ## `sandbox.useFakeXMLHttpRequest` no longer returns a "server"
 
-In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as it's `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
+In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as its `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
 
 ## `sinon.behavior` is gone
 

docs/_releases/v2.3.0/spies.md

@@ -134,7 +134,7 @@ first call. There are two ways of achieving this:
 ```
 
 The first example uses the two-dimensional `args` array directly on the spy,
-while the second example fetches the first call object and then accesses it's
+while the second example fetches the first call object and then accesses its
 `args` array. Which one to use is a matter of preference, but the recommended
 approach is going with `spy.calledWith(arg1, arg2, ...)` unless there's a need
 to make the tests highly specific.

docs/_releases/v2.3.0/stubs.md

@@ -474,7 +474,7 @@ Same as their corresponding non-Async counterparts, but with callback being defe
 
 #### `sinon.addBehavior(name, fn);`
 
-Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, it's return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
+Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, its return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
 
 ```javascript
 const sinon = require('sinon');

docs/_releases/v2.3.1/fake-timers.md

@@ -54,7 +54,7 @@ As above, but rather than starting the clock with a timestamp of 0, start at the
 
 *Since `sinon@2.0.0`*
 
-You can also pass in a Date object, and it's `getTime()` will be used for the starting timestamp.
+You can also pass in a Date object, and its `getTime()` will be used for the starting timestamp.
 
 #### `var clock = sinon.useFakeTimers([now, ]prop1, prop2, ...);`
 

docs/_releases/v2.3.1/migrating-to-2.0.md

@@ -65,7 +65,7 @@ The following utility functions are being marked as deprecated and are planned f
 
 ## `sandbox.useFakeXMLHttpRequest` no longer returns a "server"
 
-In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as it's `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
+In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as its `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
 
 ## `sinon.behavior` is gone
 

docs/_releases/v2.3.1/spies.md

@@ -134,7 +134,7 @@ first call. There are two ways of achieving this:
 ```
 
 The first example uses the two-dimensional `args` array directly on the spy,
-while the second example fetches the first call object and then accesses it's
+while the second example fetches the first call object and then accesses its
 `args` array. Which one to use is a matter of preference, but the recommended
 approach is going with `spy.calledWith(arg1, arg2, ...)` unless there's a need
 to make the tests highly specific.

docs/_releases/v2.3.1/stubs.md

@@ -474,7 +474,7 @@ Same as their corresponding non-Async counterparts, but with callback being defe
 
 #### `sinon.addBehavior(name, fn);`
 
-Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, it's return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
+Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, its return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
 
 ```javascript
 const sinon = require('sinon');

docs/_releases/v2.3.2/fake-timers.md

@@ -54,7 +54,7 @@ As above, but rather than starting the clock with a timestamp of 0, start at the
 
 *Since `sinon@2.0.0`*
 
-You can also pass in a Date object, and it's `getTime()` will be used for the starting timestamp.
+You can also pass in a Date object, and its `getTime()` will be used for the starting timestamp.
 
 #### `var clock = sinon.useFakeTimers([now, ]prop1, prop2, ...);`
 

docs/_releases/v2.3.2/migrating-to-2.0.md

@@ -65,7 +65,7 @@ The following utility functions are being marked as deprecated and are planned f
 
 ## `sandbox.useFakeXMLHttpRequest` no longer returns a "server"
 
-In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as it's `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
+In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as its `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
 
 ## `sinon.behavior` is gone
 

docs/_releases/v2.3.2/spies.md

@@ -134,7 +134,7 @@ first call. There are two ways of achieving this:
 ```
 
 The first example uses the two-dimensional `args` array directly on the spy,
-while the second example fetches the first call object and then accesses it's
+while the second example fetches the first call object and then accesses its
 `args` array. Which one to use is a matter of preference, but the recommended
 approach is going with `spy.calledWith(arg1, arg2, ...)` unless there's a need
 to make the tests highly specific.

docs/_releases/v2.3.2/stubs.md

@@ -474,7 +474,7 @@ Same as their corresponding non-Async counterparts, but with callback being defe
 
 #### `sinon.addBehavior(name, fn);`
 
-Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, it's return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
+Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, its return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
 
 ```javascript
 const sinon = require('sinon');

docs/_releases/v2.3.3/fake-timers.md

@@ -54,7 +54,7 @@ As above, but rather than starting the clock with a timestamp of 0, start at the
 
 *Since `sinon@2.0.0`*
 
-You can also pass in a Date object, and it's `getTime()` will be used for the starting timestamp.
+You can also pass in a Date object, and its `getTime()` will be used for the starting timestamp.
 
 #### `var clock = sinon.useFakeTimers([now, ]prop1, prop2, ...);`
 

docs/_releases/v2.3.3/migrating-to-2.0.md

@@ -65,7 +65,7 @@ The following utility functions are being marked as deprecated and are planned f
 
 ## `sandbox.useFakeXMLHttpRequest` no longer returns a "server"
 
-In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as it's `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
+In Sinon 1.x, the sandbox' `useFakeXMLHttpRequest` was the same as its `useFakeServer`. In 2.x, it maps directly to `sinon.useFakeXMLHttpRequest` (but with sandboxing). If you use `sandbox.useFakeXMLHttpRequest`, just replace it with `sandbox.useFakeServer`, and your tests should behave as they always did.
 
 ## `sinon.behavior` is gone
 

docs/_releases/v2.3.3/spies.md

@@ -134,7 +134,7 @@ first call. There are two ways of achieving this:
 ```
 
 The first example uses the two-dimensional `args` array directly on the spy,
-while the second example fetches the first call object and then accesses it's
+while the second example fetches the first call object and then accesses its
 `args` array. Which one to use is a matter of preference, but the recommended
 approach is going with `spy.calledWith(arg1, arg2, ...)` unless there's a need
 to make the tests highly specific.

docs/_releases/v2.3.3/stubs.md

@@ -474,7 +474,7 @@ Same as their corresponding non-Async counterparts, but with callback being defe
 
 #### `sinon.addBehavior(name, fn);`
 
-Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, it's return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
+Add a custom behavior. The name will be available as a function on stubs, and the chaining mechanism will be set up for you (e.g. no need to return anything from your function, its return value will be ignored). The `fn` will be passed the fake instance as its first argument, and then the user's arguments.
 
 ```javascript
 const sinon = require('sinon');

docs/_releases/v2.3.4/fake-timers.md

@@ -54,7 +54,7 @@ As above, but rather than starting the clock with a timestamp of 0, start at the
 
 *Since `sinon@2.0.0`*
 
-You can also pass in a Date object, and it's `getTime()` will be used for the starting timestamp.
+You can also pass in a Date object, and its `getTime()` will be used for the starting timestamp.
 
 #### `var clock = sinon.useFakeTimers([now, ]prop1, prop2, ...);`