Skip to content

Commit 23d87d8

Browse files
committed
docs: improve wording on next callback
1 parent e014630 commit 23d87d8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/guide/advanced/navigation-guards.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Every guard function receives three arguments:
3434

3535
- **`next(error)`**: (2.4.0+) if the argument passed to `next` is an instance of `Error`, the navigation will be aborted and the error will be passed to callbacks registered via [`router.onError()`](../../api/#router-onerror).
3636

37-
**Make sure that the `next` function is called exactly once in any given navigation guard. It can appear more than once, but only if the logical paths have no overlap, otherwise the hook will never be resolved or produce errors.** Here is an example of redirecting to user to `/login` if they are not authenticated:
37+
**Make sure that the `next` function is called exactly once in any given pass through the navigation guard. It can appear more than once, but only if the logical paths have no overlap, otherwise the hook will never be resolved or produce errors.** Here is an example of redirecting to user to `/login` if they are not authenticated:
3838

3939
```js
4040
// BAD

0 commit comments

Comments
 (0)