Update 11_usingovermindwithvue: remove duplicate chapters

Author: mieky

packages/overmind-website/guides/beginner/11_usingovermindwithvue.md

@@ -3,7 +3,7 @@
 There are two approaches to connecting Overmind to Vue.
 
 ```marksy
-h(Notice, null, "Please use Vue version **2.6** or later")
+h(Notice, null, "Please use Vue version **2.6** or later".)
 ```
 
 ## Plugin
@@ -21,7 +21,7 @@ h(Example, { name: "guide/usingovermindwithvue/connect_plugin_config" })
 ```
 
 ### Rendering
-Any state accessed in the component will cause the component to render when a mutation occurs on that state. Overmind actually uses the same approach to change detection as Vue itself. When using the plugin any component can access any state, though the only overhead that is added to the application is an instance of a "tracking tree" per component. This might sound scary, but it is a tiny little object that adds a callback function to Overmind as long as the component lives.These tracking trees are even reused as components unmount.
+Any state accessed in the component will cause the component to render when a mutation occurs on that state. Overmind actually uses the same approach to change detection as Vue itself. When using the plugin any component can access any state, though the only overhead that is added to the application is an instance of a "tracking tree" per component. This might sound scary, but it is a tiny little object that adds a callback function to Overmind as long as the component lives. These tracking trees are even reused as components unmount.
 
 ### Pass state as props
 
@@ -41,7 +41,7 @@ h(Example, { name: "guide/usingovermindwithvue/effect" })
 
 ## Connect
 
-If you want more manual control of what components connect to Overmind you can rather use the connector.
+If you want more manual control of what components connect to Overmind you can use the connector.
 
 ```marksy
 h(Example, { name: "guide/usingovermindwithvue/connect" })
@@ -56,25 +56,6 @@ h(Example, { name: "guide/usingovermindwithvue/connect_custom" })
 You can now access the **admin** state and actions directly with **state** and **actions**.
 
 
-### Rendering
-Any state accessed in the component will cause the component to render when a mutation occurs on that state. Overmind actually uses the same approach to change detection as Vue itself.
-
-### Pass state as props
-
-If you pass a state object or array as a property to a child component you will also in the child component need to **connect**. This ensures that the property you passed is tracked within that component, even though you do not access any state or actions from Overmind. The devtools will help you identify where any components are left "unconnected".
-
-```marksy
-h(Example, { name: "guide/usingovermindwithvue/passprops" })
-```
-
-### State effects
-
-To run effects in components based on changes to state you use the **addMutationListener** function in the lifecycle hooks of Vue.
-
-```marksy
-h(Example, { name: "guide/usingovermindwithvue/effect" })
-```
-
 ## Computed
 
 Vue has its own observable concept that differs from Overmind. That means you can not use Overmind state inside a computed and expect the computed cache to be busted when the Overmind state changes. But computeds are really for caching expensive computation, which you will not do inside a component using Overmind anyways.
@@ -83,4 +64,4 @@ What you might want is to introduce some logic, maybe combine som data from prop
 
 ```marksy
 h(Example, { name: "guide/usingovermindwithvue/computed" })
-```
+```