linked to cheatsheet EVERYWHERE

README.md

@@ -14,6 +14,8 @@ Features include:
 
 _New_ If using jest, try the new [fetch-mock-jest](https://www.npmjs.com/package/fetch-mock-jest) wrapper.
 
+_New_ [Cheatsheet](https://github.com/wheresrhys/fetch-mock/blob/master/docs/cheatsheet.md)
+
 ![node version](https://img.shields.io/node/v/fetch-mock.svg?style=flat-square)
 [![licence](https://img.shields.io/npm/l/fetch-mock.svg?style=flat-square)](https://github.com/wheresrhys/fetch-mock/blob/master/LICENSE)
 ![npm downloads](https://img.shields.io/npm/dm/fetch-mock.svg?style=flat-square)
@@ -52,7 +54,7 @@ fetch-mock requires the following to run:
 
 ## Documentation and Usage
 
-See the [project website](http://www.wheresrhys.co.uk/fetch-mock/)
+See the [project website](http://www.wheresrhys.co.uk/fetch-mock/) or [cheatsheet](https://github.com/wheresrhys/fetch-mock/blob/master/docs/cheatsheet.md)
 
 If you're using jest as your test runner, consider using [fetch-mock-jest](https://www.npmjs.com/package/fetch-mock-jest), a lightweight, jest-friendly wrapper around fetch-mock.
 

docs/_api-inspection/fundamentals.md

@@ -2,6 +2,9 @@
 title: "Inspection fundamentals"
 position: 0
 description: |-
+  Check out the new [cheatsheet](https://github.com/wheresrhys/fetch-mock/blob/master/docs/cheatsheet.md)
+  {: .info}
+  
   `fetch-mock`'s inspection methods allow information about how `fetch` was called to be retrieved after your application code has run. Most inspection methods take two arguments — `filter` and `options` — which allow individual, or groups of, `fetch` calls to be extracted and examined.
 parameters:
   - name: filter

docs/_api-mocking/mock.md

@@ -3,6 +3,9 @@ title: ".mock(matcher, response, options)"
 navTitle: .mock()
 position: 1
 description: |
+  Check out the new [cheatsheet](https://github.com/wheresrhys/fetch-mock/blob/master/docs/cheatsheet.md)
+  {: .info}
+
   Initialises or extends a stub implementation of fetch, applying a `route` that matches `matcher`, delivers a `Response` configured using `response`, and that respects the additional `options`. The stub will record its calls so they can be inspected later. If `.mock` is called on the top level `fetch-mock` instance, this stub function will also replace `fetch` globally. Calling `.mock()` with no arguments will carry out this stubbing without defining any mock responses.
 
   In the documentation, **route** is often used to refer to the combination of matching and responding behaviour set up using a single call to `mock()`

docs/_includes/sidebar.html

@@ -16,7 +16,12 @@ <h1>{{ collection.title }}</h1>
 					{% endfor %}
 					{%if collection.title == "About" %}
 						<li>
-							<a class="github-link" href="https://github.com/wheresrhys/fetch-mock"">
+							<a href="https://github.com/wheresrhys/fetch-mock/blob/master/docs/cheatsheet.md">
+								Cheatsheet
+							</a>
+						</li>
+						<li>
+							<a class="github-link" href="https://github.com/wheresrhys/fetch-mock">
 								Github project
 							</a>
 						</li>

docs/_usage/requirements.md

@@ -10,4 +10,7 @@ content_markdown: |-
   - Either
     - [node-fetch](https://www.npmjs.com/package/node-fetch) when testing in Node.js. To allow users a choice over which version to use, `node-fetch` is not included as a dependency of `fetch-mock`.
     - A browser that supports the `fetch` API either natively or via a [polyfill/ponyfill](https://ponyfoo.com/articles/polyfills-or-ponyfills)
+
+  Check out the new [cheatsheet](https://github.com/wheresrhys/fetch-mock/blob/master/docs/cheatsheet.md)
+  {: .info}
 ---