Update 03_about-state-and-meet-redux.js

Him to it as we're talking about a library rather than a person.
Various changes to sentence fragments.

Not keen on this line //     Using subscribers to state's modifications.

Author: ChrisMcKee

03_about-state-and-meet-redux.js

@@ -1,7 +1,7 @@
 // Tutorial 3 - about-state-and-meet-redux.js
 
-// Sometimes, the actions that we'll handle in our application will not only be made to inform us
-// that something happened but also to tell us that a data needs to be updated.
+// Sometimes the actions that we'll handle in our application will not only inform us
+// that something happened but also tell us that data needs to be updated.
 
 // This is actually quite a big challenge in any apps.
 // Where do I keep all the data regarding my application along its lifetime?
@@ -12,13 +12,13 @@
 
 // Redux (https://github.com/gaearon/redux) is a "predictable state container for JavaScript apps"
 
-// Let's take again those questions above and reply to them with 
+// Let's review the above questions and reply to them with 
 // Redux vocabulary (flux vocabulary too for some of them):
 
 // Where do I keep all the data regarding my application along its lifetime?
 //     You keep it the way you want (JS object, array, Immutable structure, ...).
 //     Data of your application will be called state. Makes sense since we're talking about
-//     all the application's data that will evolve over time, it's really the application's state.
+//     all the applications data that will evolve over time, it's really the applications state.
 //     But you hand it over to Redux (Redux is "state container", remember?).
 // How do I handle modification of such data?
 //     Using reducers.
@@ -28,22 +28,22 @@
 // How do I propagate modifications to all parts of my application?
 //     Using subscribers to state's modifications.
 
-// Redux tie all this up together for you.
+// Redux ties all this together for you.
 // To sum up, Redux will provide you:
 //     1) a place to put your application state
 //     2) a mechanism to subscribe to state updates
-//     3) a mechanism to dispatch actions to modifiers of your application state AKA reducers
+//     3) a mechanism to dispatch actions to modifiers of your application state, AKA reducers
 
 // The Redux instance is called a store and can be created like this:
 /*
     import { createStore } from 'redux'
     var store = createStore()
 */
 
-// but if you run the code above, you'll notice that it throw an error:
+// But if you run the code above, you'll notice that it throw an error:
 //     Error: Invariant Violation: Expected the reducer to be a function.
 
-// That's because createStore expect at least a function that will allow him to reduce your state
+// That's because createStore expects a function that will allow it to reduce your state.
 
 // Let's try again
 
@@ -53,4 +53,4 @@ var store = createStore(() => {})
 
 // Seems good for now...
 
-// Go to next tutorial: simple-reducer.js
+// Go to next tutorial: simple-reducer.js