diff --git a/README.md b/README.md index 34ea444214..651c5e2a3a 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ $ hexo server ## On Translations -Translation for this documentation project are currently mantained in separate repositories forked from this original one. +Translation for this documentation project are currently maintained in separate repositories forked from this original one. ### French diff --git a/src/_posts/011-component.md b/src/_posts/011-component.md index 2be314f1ac..c95230e530 100644 --- a/src/_posts/011-component.md +++ b/src/_posts/011-component.md @@ -54,7 +54,7 @@ The only exception to the rule is `v-with` (and `paramAttributes` which compiles ### Cleaner Event Communication -Previously the standard way for a child component to communicate to its parent is via dispatching events. However, with this approach, the event listeners on the parent component are not guaranteed to be listening on the desired child component only. It's also possible to trigger undesired listners further up the chain if we do not cancel the event. +Previously the standard way for a child component to communicate to its parent is via dispatching events. However, with this approach, the event listeners on the parent component are not guaranteed to be listening on the desired child component only. It's also possible to trigger undesired listeners further up the chain if we do not cancel the event. The most common use case is for a parent to react to the events from a specific, direct child component. So in 0.11.4, [a new directive `v-events`](/api/directives.html#v-events) has been introduced to enable exactly this behavior. diff --git a/src/_posts/vue-next.md b/src/_posts/vue-next.md index f30cd9c625..fe324b223d 100644 --- a/src/_posts/vue-next.md +++ b/src/_posts/vue-next.md @@ -5,7 +5,7 @@ date: 2014-07-29 00:04:55 ## 0.10.6 -Vue.js 0.10.6 has been released! This is another small bug-fix release and will be the last maintainance version before the next major release. +Vue.js 0.10.6 has been released! This is another small bug-fix release and will be the last maintenance version before the next major release. @@ -22,6 +22,6 @@ Some of you might have noticed there is a [next](https://github.com/yyx990803/vu - Fix some issues that are caused by design flaws in the current version. Because these changes affect the design of some core modules, it is actually easier to rewrite than to apply on the current codebase. - Improve general code quality (in particular, `compiler.js` as of now is a big pile of mess, and comments are not consistent across the codebase.) -Take note that the `next` branch is still in **very** early stage. The internals will change a lot, and when it comes out it **will** break current applications. Despite that I will try to keep the API changes to a minimum. Major differences with current 0.10 branch are documented in [`changes.md`](https://github.com/yyx990803/vue/blob/next/changes.md). The list is obviously incomplete and subject to change, some of them are simply ideas, but it at least gives you a taste of what to expect, and I'd appreicate your feedback on any of the topics. +Take note that the `next` branch is still in **very** early stage. The internals will change a lot, and when it comes out it **will** break current applications. Despite that I will try to keep the API changes to a minimum. Major differences with current 0.10 branch are documented in [`changes.md`](https://github.com/yyx990803/vue/blob/next/changes.md). The list is obviously incomplete and subject to change, some of them are simply ideas, but it at least gives you a taste of what to expect, and I'd appreciate your feedback on any of the topics. Share your thoughts at [vuejs/Discussion](https://github.com/vuejs/Discussion/issues). diff --git a/src/v2/guide/migration-vuex.md b/src/v2/guide/migration-vuex.md index 1e5aa28bdf..f15e6f0667 100644 --- a/src/v2/guide/migration-vuex.md +++ b/src/v2/guide/migration-vuex.md @@ -9,7 +9,7 @@ order: 28 Both Vuex 1.0 and 2.0: - fully support both Vue 1.0 and 2.0 -- will be maintained for the forseeable future +- will be maintained for the foreseeable future They have slightly different target users however.