Skip to content

fix: typos using misspell #916

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from May 20, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion src/_posts/011-component.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
4 changes: 2 additions & 2 deletions src/_posts/vue-next.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<!-- more -->

Expand All @@ -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).
2 changes: 1 addition & 1 deletion src/v2/guide/migration-vuex.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down