Grammatical improvement

Author: uanders

article/react-redux-concept-workflow.md

@@ -298,7 +298,7 @@ I'd like to start with a graphical cheat sheet explaining the workflow in a Reac
 
 1. In this way, the store receives a new state. When the store is updated with a new state state a re-render of the components that have subscribed to the store is triggered.
 
-1. Note, action creators are often used to create actions that lead to a change if the state in the store. But no all actions are used generate state changes. Some action objects may simply be generated by action creators to make temporary state changes to the app that are not stored.
+1. Note that action creators are most often used to create actions that lead to a change of the state in the store. But not all action creators are used to generate state changes. Some action objects may simply be generated by action creators to make temporary state changes to the app which are not stored.
 
 1. An arbitrary number of functions can register at the store to be also triggered whenever the store got updated with a new state. The functions registered at the store to be triggered have been named listeners, probably because they are "listening" to updates of the state. But in fact, they are not actively listening themselves. Quite the opposite, they are not actively in control, they are just passively triggered. The triggering function is a method that belongs to the store named [*store.subscribe()*](http://redux.js.org/docs/api/Store.html#subscribe). This name also takes a little bit getting used to as the store itself actually does not subscribe to anything. So, mentally you could think *trigger* when you use *subscribe()*.^[Don't confuse a component actually *subscribing* to a state change by help of the *connect()* function with a function that can be registered with the *store.subscribe()* method in order to be triggered whenever there is a new state.]