events doc change

Author: Evan You

source/guide/events.md

@@ -27,8 +27,6 @@ new Vue({
 })
 ```
 
-One thing to note is that internally, Vue.js uses event delegation for all `v-on` handlers. Vue.js ensures that `event.stopPropagation()` and `event.preventDefault()` will work like normal listeners, but `event.currentTarget` will always point to the ViewModel's root element. In cases where `event.target` is a childNode of the actual element that the `v-on` directive is bound to, the element with `v-on` will be available as `event.delegationTarget`.
-
 ## Invoke Handler with Expression
 
 `targetVM` could be useful when `v-on` is used with `v-repeat`, since the latter creates a lot of child ViewModels. However, it is often more convenient to use an invocation expression passing in `this`, which equals the current context ViewModel:
@@ -98,7 +96,6 @@ You might be concerned about this whole event listening approach violates the go
 
 1. It makes it easier to locate the handler function implementations within your JS code by simply skimming the HTML template.
 2. Since you don't have to manually attach event listeners in JS, your ViewModel code can be pure logic and DOM-free. This makes it easier to test.
-3. When a ViewModel is destroyed, all event listeners are automatically removed.
-4. Vue.js automatically uses event delegation on each VM's root element instead of attaching a listner on every Node. Listeners on `v-repeat` instances are delegated together on their parent ViewModel.
+3. When a ViewModel is destroyed, all event listeners are automatically removed. You don't need to worry about cleaning it up yourself.
 
 Next up: [Handling Forms](/guide/forms.html).