Fetcher docs, except hydrate still needs work

Author: letitia

_fetcher/fetch.md

@@ -3,7 +3,7 @@ header: fetch
 example: Fetcher.fetch(fetchSpec, [options], callback)
 ---
 
-`fetchSpec` is an object with the information to fetcher [Models](/model) or [Collections](/collection).
+Fetches [Models](/model) or [Collections](/collection) according to the parameters defined in the `fetchSpec` and populates the corresponding ModelStore and/or CollectionStore.
 
 Example `fetchSpec`:
 
@@ -28,16 +28,16 @@ Example `fetchSpec`:
 }
 ```
 
-This `fetchSpec` will get two models, the User and Character models, and one collection, the StarWarsCharacters collection.
+This `fetchSpec` will get two models (the User and Character models) and one collection (the StarWarsCharacters collection).
 
-Extra options to pass a `fetchSpec`:
+Extra options to pass to a `fetchSpec`:
 
 - *needsFetch* - Allows you to force a fetch request
 - *ensureKeys* - Ensures any stored data has all the required data, if not an API request will be made
 
-The `callback` function will be called with an `error` and `results` from the fetch.  The `error` argument will contain any errors when fetching data.  The `results` argument is an object of results from the API requests.  Each key is defined in the `fetchSpec` where the value is the response from the API.  For an example of what a callback function might look like, check out the [Contoller](/controller) documentation.
+The `callback` function will be called with an `error` and `results` from the fetch.  For an example callback function, check out the [Controller](/controller) documentation.
 
-`options` *optional* Allows you to set caching information.  The defaults for the options differ from client and server.  By default API responses are not written or read from the cache on the server, but both are true on the client.
+`options` *optional* Allows you to set caching information.  The defaults differ between client and server:  by default API responses are not written or read from the cache on the server, but both are true on the client.
 
 Example `options`:
 
@@ -50,4 +50,4 @@ var opts = {
 Fetcher.fetch(fetchSpec, opts, callback);
 ```
 
-The `fetch` function will make an AJAX request if `readFromCache` is false **or** if the data does not exist in the store.  By default on the client, the fetch request will check the corresponding store to see if the data exists, if it does no request is made and it simply returns the value in the store.  If the data isn't found it generates AJAX requests for each item defined in the `fetchSpec`.  **Note**: These AJAX requests are run in parallel.
+The `fetch` function will make an AJAX request if `readFromCache` is false **or** if the data does not exist in the ModelStore or CollectionStore.  If the data isn't found in the relevant store, it makes AJAX requests for each item defined in the `fetchSpec`.  **Note**:  These AJAX requests are run in parallel.

_fetcher/fetchFromApi.md

@@ -3,5 +3,5 @@ header: fetchFromApi
 example: Fetcher.fetchFromApi(spec, options, callback)
 ---
 
-Calls fetch for the [model](http://backbonejs.org#Model-fetch) or [collection](http://backbonejs.org#Collection-fetch) with the given options and invokes the callback when the fetch is completed.
+Calls `fetch` for the [model](http://backbonejs.org#Model-fetch) or [collection](http://backbonejs.org#Collection-fetch) with the given options and invokes the callback after the fetch is completed.
 

_fetcher/hydrate.md

@@ -9,6 +9,6 @@ Arguments:
 
 - `summaries` can be generated by the [Fetcher.summarize](#summarize) function.
 - `options` *optional* can be used to pass an instance of the [app](/app).
-- `callback` callback function, what you want to invoke after the data is retrieved from the store.
+- `callback` this function is invoked after the data is retrieved from the store.
 
 This function is used when [attaching the child views](/view#attachChildViews).

_fetcher/pendingFetches.md

@@ -3,4 +3,4 @@ header: pendingFetches
 example: Fetcher.pendingFetches
 ---
 
-Is a counter to the number of items currently being fetched.  The [fetch](#fetch) function keeps track of the number of pending fetches.
+A counter for the number of items currently being fetched.  The [fetch](#fetch) function keeps track of the number of pending fetches.

_fetcher/storeResults.md

@@ -3,4 +3,4 @@ header: storeResults
 example: Fetcher.storeResults(results)
 ---
 
-Stores each of the items in the `results` object to the corresponding store.
+Saves each item from the `results` object into the corresponding store.

fetcher/index.md

@@ -5,7 +5,7 @@ title: "Fetcher - RendrJS"
 
 # Fetcher
 
-The Fetcher is initialized during the [app](/app) initialization.  The class is designed to fetch data from an API on the client or server.  It is attached to the app object and initializes the [Model Store](/model-store) and the [Collection Store](/collection-store).  It also mixes in the [Backbone.Events](http://backbonejs.org#Events) to allow you to trigger the events on client or server the same way you would in Backbone.
+The Fetcher is initialized during the [app](/app) initialization and is attached to the app object.  This class is designed to fetch data from an API on the client or server.  It initializes the [Model Store](/model-store) and [Collection Store](/collection-store), and mixes in the [Backbone.Events](http://backbonejs.org#Events) to allow you to trigger events on client or server the way you would in Backbone.
 
 {% include pageDoc.html name="fetcher" %}
 

model/index.md

@@ -7,6 +7,6 @@ title: "Model - RendrJS"
 
 Rendr models extend [Backbone Models](http://backbonejs.org#Model).  They are configured to run on the client and server, though some of the functionality works a little different between the two.  You won't normally need to worry about these differences in your project.
 
-The model also mixes-in the **[syncer](/syncer)** functionality for fetching data from an API on the client or the server.
+The model also mixes in the **[syncer](/syncer)** functionality for fetching data from an API on the client or the server.
 
 {% include pageDoc.html name="model" %}