minor edits to Controller docs

Author: letitia

_controller/action.md

@@ -15,4 +15,4 @@ module.exports = {
 };
 ```
 
-The example above will have add the `index` action to the `users_controller`.  To hookup the controller's action to a route simply add `addRoute('/users', 'users#index')` to the [app/routes.js](/router#routes.js) file.
+The example above will add the `index` action to the `users_controller`.  To connect the controller's action to a route, simply add `addRoute('/users', 'users#index')` to the [app/routes.js](/router#routes.js) file.

_controller/name.md

@@ -2,8 +2,8 @@
 header: name
 ---
 
-All controllers are required to have the `_controller.js` post-fix.  The name of the controller is the filename before the post-fix.
+All controllers are required to have the `_controller.js` postfix.  The name of the controller is the filename before the postfix.
 
-For example: `users_controller.js` has the name `users`.
+For example:  `users_controller.js` has the name `users`.
 
-This is a convention, and doesn't actually have an attribute stored, the [router](/router) uses it to generate the handler in [addRouteDefinition](/router#addRouteDefinition).
+The [router](/router) uses this naming convention to generate the handler in [addRouteDefinition](/router#addRouteDefinition), but a `name` attribute isn't actually stored.

controller/index.md

@@ -5,14 +5,14 @@ title: Controller - RendrJS
 
 # Controller
 
-Controllers are an addition to Rendr that doesn't exist in Backbone. Controllers allow us to have a cleaner [router](/router).  Controllers define functions that the router will invoke when a URL is visited.  The functions that are invoked are called [actions](#action).
+Controllers are an addition to Rendr that do not exist in Backbone.  Controllers define functions (known as [actions](#action)) that the [router](/router) will invoke when a URL is visited.  This allows us to have a cleaner router.
 
-Controllers have no base class, as they are simply objects where the values are functions.  Simply create files in the `controllers/` directory of your application and follow the naming convention: `<name>_controller.js`.  The [name](#name) is how the router will know which file to open.  The keys of the object being exported are the [actions](#action) for a controller.
+Controllers have no base class, as they are simply objects containing functions.  Simply create files in the `controllers/` directory of your application and follow the naming convention: `<name>_controller.js`.  The [name](#name) is how the router will know which file to open.  The keys of the object being exported are the [actions](#action) for a controller.
 
 Example Controller:
 
 ```js
-// contollers/users_controller.js
+// controllers/users_controller.js
 module.exports = {
   index: function(params, callback) {
     var spec = {
@@ -44,9 +44,9 @@ module.exports = {
 };
 ```
 
-The above example creates a controller with two actions, `index` and `show`.  The `index` action will simply display all the users, and the `show` action will show a specific user, by their id.
+The above example creates a controller with two actions, `index` and `show`.  The `index` action will display all the users, and the `show` action will show a specific user by their id.
 
-The example's matching [routes.js](/router#routes.js) file:
+Example [routes.js](/router#routes.js) file:
 
 ```js
 module.exports = function(addRoute) {
@@ -55,7 +55,7 @@ module.exports = function(addRoute) {
 };
 ```
 
-Note how the `routes.js` file will match the controller's [name](#name) and the [action](#action)
+Note how the `routes.js` file will match the controller's [name](#name) and the [action](#action).
 
 {% include pageDoc.html name="controller" %}