some more corrections

Author: uanders

README.md

@@ -10,7 +10,12 @@ The idea is to help new and existing Redux users to understand how the general m
 
 ## Article
 
-This repo furthermore holds an [article](/article/react-redux-concept-workflow_v105.md) that walks you though an extended version of this cheatsheet. It has been extended by two very common libraries: 'react-router' and 'immutable'.
+This repo furthermore holds an [article](/article/react-redux-concept-workflow_v105.md) that walks you though an extended version of this cheatsheet. Two very common libraries have been added to the extended version: 'react-router' and 'immutable'.
+
+The article runs through the Redux workflow starting at the dominant Redux player: the store.
+While going the full circle the article introduces the main Redux concepts and touches briefly on some external libraries such as: 'redux-persist', 'redux-thunk', 'redux-saga', 'redux-promise', 'reselect' and 'normalizr'.
+
+Please, raise an issue in case you find errors or things to be not clear enough.
 
 
 ## Notes

article/react-redux-concept-workflow_v105.md

@@ -148,7 +148,7 @@ I'd like to start with a graphical cheat sheet explaining the workflow in a Reac
     }
     ```
 
-    Just as a side note, since this is the first time we are showing class methods: remember, that there are two types of notations for method declarations with a different effect to [*autobinding*](https://facebook.github.io/react/docs/react-without-es6.html#autobinding) the methods to the *this* operator of the classes. Here, you would need to bind manageSomeDate() and applySomeBusinessLogic() manually to the *this* operator, whereas makeSomeCalculations() would have been autobound.
+    Just as a side note, since this is the first time we are showing class methods: remember, that there are two types of notations for method declarations with a different effect to [*autobinding*](https://facebook.github.io/react/docs/react-without-es6.html#autobinding) the methods to the *this* operator of the classes. Here, you would need to bind manageSomeDate() and applySomeBusinessLogic() manually to the *this* operator, whereas *makeSomeCalculations()* would have been autobound.
 
 
 1. Since only smart container components manage data only they need to receive state data from the store. This works via a function called [*connect()*](https://github.com/reactjs/react-redux/blob/master/docs/api.md#connectmapstatetoprops-mapdispatchtoprops-mergeprops-options) which you need to import from 'react-redux'. The *connect()* function returns a higher order component, i.e. a component that expects a component as an argument. This argument is the smart component that you want to connect. The higher order component then returns a new instance of the smart component that is now connected. 
@@ -183,15 +183,15 @@ I'd like to start with a graphical cheat sheet explaining the workflow in a Reac
 
 1. Whenever the state in the store is updated, all your *mapStateToProps()* mapping functions for connecting components will be called and the new state data mapped to the properties of the connected components.
     
-1. If you only want to map a subset of your slice to certain properties in your component you can make a selection from the slice of your state tree. A function that makes a selection is called a *selector*. But remember each time the store gets an update all mapping functions are called independent of whether the state change is relevant for a component. That means that also all the selector functions are called. If a selector function now is computationally expensive, it might slow down your app. In this case you should optimize your selectors by help of [reselect](https://github.com/reactjs/reselect).
+1. If you only want to map a subset of your slice to certain properties in your component you can make a selection from the slice of your state tree. A function that makes a selection is called a *selector*. But remember each time the store gets an update all mapping functions are called independent of whether the state change is relevant for a component. That means that also all the selector functions are called. If a selector function now is computationally expensive, it might slow down your app. In this case you should optimize your selectors by help of ['reselect'](https://github.com/reactjs/reselect).
 
     ```JavaScript
     function mapStateToProps(state) {
         return {
           // component gets this.props.selection1
           selection1: selector1(state.slice01),
           // component gets this.props.selection2   
-          selection2: selector2(state.slice01)   
+          selection2: selector2(state.slice01)
         }
     }
     ```