edit docs

Author: yyx990803

docs/en/advanced/navigation-guards.md

@@ -40,7 +40,7 @@ Every guard function receives three arguments:
 
 > New in 2.5.0
 
-In 2.5.0+ you can register a global guard with `router.onResolve`. This is similar to `router.beforeEach`, with the difference that resolve guards will be called right before the navigation is confirmed, **after all in-component guards and async route components are resolved**.
+In 2.5.0+ you can register a global guard with `router.beforeResolve`. This is similar to `router.beforeEach`, with the difference that resolve guards will be called right before the navigation is confirmed, **after all in-component guards and async route components are resolved**.
 
 ### Global After Hooks
 
@@ -118,7 +118,7 @@ beforeRouteEnter (to, from, next) {
 
 You can directly access `this` inside `beforeRouteLeave`. The leave guard is usually used to prevent the user from accidentally leaving the route with unsaved edits. The navigation can be canceled by calling `next(false)`.
 
-### The Full Guard Resolution Flow
+### The Full Navigation Resolution Flow
 
 1. Navigation triggered
 2. Call leave guards in deactivated components

docs/en/essentials/dynamic-matching.md

@@ -53,6 +53,18 @@ const User = {
 }
 ```
 
+Or, use the `beforeRouteUpdate` guard introduced in 2.2:
+
+``` js
+const User = {
+  template: '...',
+  beforeRouteUpdate (to, from, next) {
+    // react to route changes...
+    // don't forget to call next()
+  }
+}
+```
+
 ### Advanced Matching Patterns
 
 `vue-router` uses [path-to-regexp](https://github.com/pillarjs/path-to-regexp) as its path matching engine, so it supports many advanced matching patterns such as optional dynamic segments, zero or more / one or more requirements, and even custom regex patterns. Check out its [documentation](https://github.com/pillarjs/path-to-regexp#parameters) for these advanced patterns, and [this example](https://github.com/vuejs/vue-router/blob/dev/examples/route-matching/app.js) of using them in `vue-router`.