Editing docs for View functions from index.md to getInnerHtml.md

Author: letitia

_fetcher/hydrate.md

@@ -5,6 +5,8 @@ example: Fetcher.hydrate(summaries, [options], callback)
 
 This method is called when attaching views to the DOM, specifically when [attaching the child views](/view#attachChildViews).  `hydrate` loops through each summary to retrieve the data from the corresponding [Model Store](/model-store) or [Collection Store](/collection-store) for each child view, then it invokes the specified callback.
 
+Hydration occurs either when the HTML has been loaded by the server, or when a view is creating an instance of a child view using a template adapter.
+
 Arguments:
 
 - `summaries` can be generated by the [Fetcher.summarize](#summarize) function.

_view/attachChildViews.md

@@ -3,4 +3,4 @@ header: attachChildViews
 example: View.attachChildViews()
 ---
 
-Removes all child views, then looks at all of the child views that are expected and attaches each view.
+Removes all child views, then looks at all of the expected child views and attaches each view.

_view/attachOrRender.md

@@ -3,6 +3,4 @@ header: attachOrRender
 example: View.attachOrRender(element, parentView)
 ---
 
-This is invoked when View is hydrating the [childViews](/#childViews).  This will inspect the element and check to see if the view is lazy loaded or already attached.  Hydration is the step where the HTML has been loaded by the server, or a view is creating an instance of a child view using a [template adapter](/template-adapters).
-
-If neither of those are true, then it will see if the `data-render` attribute is set on the element. If it is, it will invoke the [render](#render) function.  If not, it will call the [attach](#attach) function on the element.
+This is invoked when View is [hydrating](/fetcher/#hydrate) the [childViews](#childViews).  This inspects the element to see if the view is lazy loaded or already attached.  If neither of those are true, then it will check if the `data-render` attribute is set on the element.  If it is, it will invoke the [render](#render) function.  Otherwise it will call the [attach](#attach) function on the element.

_view/childViews.md

@@ -3,4 +3,4 @@ header: childViews
 example: View.childViews
 ---
 
-An array of the views that are children of the view.
+An array of subviews of the view.

_view/constructor.md

@@ -3,10 +3,10 @@ header: constructor
 example: new View([options])
 ---
 
-Creates a new instance of the View object.  A required option is [app](/app) which is used in many of the helper functions throughout the view, and entire application.
+Creates a new instance of the View object.  A required option is [app](/app) which is used in many helper functions throughout the view.
 
-The constructor will also intelligently retrieve [model](/model) and [collection](/collection) information.  If you pass a JSON object with an ID and give it the `collection_name` or `model_name` options, it will retrieve that data from the corresponding store and set the inflated model / collection as the view attribute.  For more information on parsing the model and collection attributes see [parseOptions](#parseOptions).
+The constructor will also intelligently retrieve [model](/model) and [collection](/collection) information.  If you pass a JSON object with an id and give it the `collection_name` or `model_name` options, it will retrieve that data from the corresponding store and set the populated model / collection as an attribute on the view.  For more information on parsing the model and collection attributes see [parseOptions](#parseOptions).
 
-The view constructor can have additional initialization information set by adding an `initialize` function.  This is the same pattern developed in [Backbone's initialization](http://backbonejs.org/#View-constructor).
+You can set additional initialization information in the view constructor by adding an `initialize` function, just as in [Backbone's initialization](http://backbonejs.org/#View-constructor).
 
-Another special option is `template_name`.  This allows a point to hook in at to give a view a different template, by default this is `undefined`.
+Another special option is `template_name`, where you can set a different template for the view.  By default this is `undefined`.

_view/decorateTemplateData.md

@@ -3,6 +3,6 @@ header: decorateTemplateData
 example: View.decorateTemplateData(data)
 ---
 
-This function takes the result from [getTemplateData](#getTemplateData) and applies special properties to the data for the view.  The special properties are `_app`, `_view`, `_model`, and/or `_collection`.  These special properties are the instance variables for each of the options set on the view.
+This function takes the result from [getTemplateData](#getTemplateData) and applies special properties to the data for the view.  The special properties are `\_app`, `\_view`, `\_model`, and/or `\_collection`:  the instance variables for each of the options set on the view.
 
 These are generally used in view helper functions, and for passing the instances to sub-views.

_view/fetchLazy.md

@@ -3,7 +3,7 @@ header: fetchLazy
 example: View.fetchLazy()
 ---
 
-*Client-side only* To lazy load a view set the `lazy` option to true.
+*Client-side only* Set the `lazy` option to true to lazy-load a view.
 
 <pre><code>var view = new View({
   'lazy': true,
@@ -13,9 +13,9 @@ example: View.fetchLazy()
 
 View options for enabling lazy loading:
 
-- `lazy` - Set this to true to stop the server from trying to render the HTML server-side.
-- `fetch_params` - an object of parameters to send to the API for the model or collection
+- `lazy` - Set this to true to stop the server from trying to render the HTML server-side
+- `fetch_params` - An object of parameters to send to the API for the model or collection
 - `model_name` - This is used to make the fetch request for a model with the given parameters
-- `collection_name` - If you're requesting a collection, this is the name of the collection for the view.
+- `collection_name` - If you're requesting a collection, this is the name of the collection for the view
 
-When the request begins, the `loading` class is added to the view, and triggers the `loading` event.  [preRender](#preRender) is also invoked before the fetch request to the server.  Once the data is retrieved from the server, if the view is still attached to the DOM, it will parse the results and [render](#render) the view.
+When the request begins, the `loading` class is added to the view, the `loading` event is triggered, and [preRender](#preRender) is invoked before the fetch request to the server.  Once the data is retrieved from the server, if the view is still attached to the DOM, it will parse the results and [render](#render) the view.

_view/getChildViewsByName.md

@@ -3,7 +3,7 @@ header: getChildViewsByName
 example: View.getChildViewsByName(name)
 ---
 
-This searches the [childViews](#childViews) attribute to return any children views that have a matching name. The function takes a string for the `name`, and returns an array of matches.
+This searches the [childViews](#childViews) attribute to return any children views that have a matching name.  The function takes a string for the `name`, and returns an array of matches.
 
-Note: these must be the *exact* name of the view, if the view name includes a path or namespace, that must be included.
+Note:  The argument must be the *exact* name of the view, including a path or namespace if those are present.
 

_view/getHtml.md

@@ -20,4 +20,4 @@ view.getHtml();
 
 The Result: `'<a class="text-primary" data-additional-option="test">/* template */</a>'`
 
-This function is expected to only be used on the server.
+This function should only be used on the server.

_view/getInnerHtml.md

@@ -5,4 +5,4 @@ example: View.getInnerHtml()
 
 Turns the view's template into a string of HTML, without the wrapper element defined in the view itself.
 
-This will invoke the [preRender](#preRender) hook. Having the preRender invoked in `getInnerHtml` will ensure that it is invoked on client and server.
+This function invokes the [preRender](#preRender) hook, which ensures that `preRender` is invoked on client and server.

_view/nonAttributeOptions.md

@@ -3,4 +3,4 @@ header: nonAttributeOptions
 example: View.nonAttributeOptions
 ---
 
-These are options for the view that we don't want to create data-attributes for in the HTML.  By default it's set to `['id', 'className', 'tagName']`, which are all attributes of the element itself.  For more information about those specific elements checkout Backbone's [documentation](http://backbonejs.org/#View).
+These are options for the view that we don't want to create data-attributes for on the HTML element.  By default it's set to `['id', 'className', 'tagName']`, which are all attributes of the element itself.  For more information about those specific elements check out [Backbone's documentation](http://backbonejs.org/#View).

view/index.md

@@ -5,11 +5,11 @@ title: "View - RendrJS"
 
 # View
 
-Views are the most powerful addition with Rendr.  They have the ability to render HTML on the client or the server.  This has a huge impact on performance, and with SEO.  We can now render the same HTML on the client or the server, allowing web crawlers to work the same way a client-side Backbone application would.
+Views are the most powerful addition in Rendr.  They are capable of rendering HTML on both the client and the server.  This boosts the performance of your initial content load, and improves SEO by enabling web crawlers to easily crawl the contents of the rendered HTML, which has traditionally been a challenge with AJAX-loaded content in client-side Backbone applications.
 
-`Rendr.View` also hides a lot of the inner workings.  Simply invoke the [render](#render) method of a view and it will re-render the template with the current state of the data and replace the HTML for you.  There are also pre and post render hooks; [preRender](#preRender) and [postRender](#postRender).
+`Rendr.View` also hides a lot of the inner workings.  Simply invoke the [render](#render) method of a view and it will re-render the template with the current state of the data.  You can also write code in the [preRender](#preRender) and [postRender](#postRender) hooks provided.
 
-Another performance boost comes with 'lazy-loading' views (see [fetchLazy](#fetchLazy)).  The views that don't affect SEO or are secondary to data are prime views to lazy-load.  When you lazy-load a view, it will wait to fetch data from the API until the page is loaded client-side.  After fetching the data, it will automatically render the component it was defined.
+Another performance boost comes with 'lazy-loading' views (see [fetchLazy](#fetchLazy)).  When you lazy-load a view, it will wait to fetch its data from the API until the page has finished loading on the client.  After fetching the data, it will automatically render that component.  The views that don't affect SEO or are secondary to data are prime views to lazy-load.
 
 {% include pageDoc.html name="view" %}