Fix minor errors in README.md

Changes involve:
- Removal of dead links: data flow.png and vuex.png
- Removal of discourse markers (although, also, in addition) to make sentences precise

docs/README.md

@@ -31,17 +31,13 @@ new Vue({
 
 It is a self-contained app with the following parts:
 
-- The **state**, which is the source of truth that drives our app;
-- The **view**, which is just a declarative mapping of the **state**;
-- The **actions**, which are the possible ways the state could change in reaction to user inputs from the **view**.
+- The **state**, the source of truth that drives our app;
+- The **view**, a declarative mapping of the **state**;
+- The **actions**, the possible ways the state could change in reaction to user inputs from the **view**.
 
-This is an extremely simple representation of the concept of "one-way data flow":
+This is an simple representation of the concept of "one-way data flow":
 
-<p style="text-align: center; margin: 2em">
-  <img style="width:100%;max-width:450px;" src="/flow.png">
-</p>
-
-However, the simplicity quickly breaks down when we have **multiple components that share common state**:
+However, the simplicity quickly breaks down when we have **multiple components that share a common state**:
 
 - Multiple views may depend on the same piece of state.
 - Actions from different views may need to mutate the same piece of state.
@@ -50,17 +46,15 @@ For problem one, passing props can be tedious for deeply nested components, and
 
 So why don't we extract the shared state out of the components, and manage it in a global singleton? With this, our component tree becomes a big "view", and any component can access the state or trigger actions, no matter where they are in the tree!
 
-In addition, by defining and separating the concepts involved in state management and enforcing certain rules, we also give our code more structure and maintainability.
+By defining and separating the concepts involved in state management and enforcing rules that maintain independece between views and states, we give our code more structure and maintainability.
 
 This is the basic idea behind Vuex, inspired by [Flux](https://facebook.github.io/flux/docs/overview.html), [Redux](http://redux.js.org/) and [The Elm Architecture](https://guide.elm-lang.org/architecture/). Unlike the other patterns, Vuex is also a library implementation tailored specifically for Vue.js to take advantage of its granular reactivity system for efficient updates.
 
 If you want to learn Vuex in an interactive way you can check out this [Vuex course on Scrimba](https://scrimba.com/g/gvuex), which gives you a mix of screencast and code playground that you can pause and play around with anytime.
 
-![vuex](/vuex.png)
-
 ### When Should I Use It?
 
-Although Vuex helps us deal with shared state management, it also comes with the cost of more concepts and boilerplate. It's a trade-off between short term and long term productivity.
+Vuex helps us deal with shared state management with the cost of more concepts and boilerplate. It's a trade-off between short term and long term productivity.
 
 If you've never built a large-scale SPA and jump right into Vuex, it may feel verbose and daunting. That's perfectly normal - if your app is simple, you will most likely be fine without Vuex. A simple [store pattern](https://vuejs.org/v2/guide/state-management.html#Simple-State-Management-from-Scratch) may be all you need. But if you are building a medium-to-large-scale SPA, chances are you have run into situations that make you think about how to better handle state outside of your Vue components, and Vuex will be the natural next step for you. There's a good quote from Dan Abramov, the author of Redux: