From bb1123c324e24e6ec9cb315ae5290460caa46cd6 Mon Sep 17 00:00:00 2001 From: Shawn Flanagan Date: Mon, 24 Apr 2017 12:07:47 -0500 Subject: [PATCH] Spelling correction Changed `beforeRouteUpadte` to `beforeRouteUpdate` --- docs/en/advanced/navigation-guards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/advanced/navigation-guards.md b/docs/en/advanced/navigation-guards.md index e627f4094..8ff4cc730 100644 --- a/docs/en/advanced/navigation-guards.md +++ b/docs/en/advanced/navigation-guards.md @@ -2,7 +2,7 @@ As the name suggests, the navigation guards provided by `vue-router` are primarily used to guard navigations either by redirecting it or canceling it. There are a number of ways to hook into the route navigation process: globally, per-route, or in-component. -Remember that **params or query changes won't trigger enter/leave navigation guards**. You can either [watch the `$route` object](../essentials/dynamic-matching.md#reacting-to-params-changes) to react to those changes, or use the `beforeRouteUpadte` in-component guard. +Remember that **params or query changes won't trigger enter/leave navigation guards**. You can either [watch the `$route` object](../essentials/dynamic-matching.md#reacting-to-params-changes) to react to those changes, or use the `beforeRouteUpdate` in-component guard. ### Global Guards