Apply suggestions from code review

Co-authored-by: Ben Hong <[email protected]>

Author: posva

docs/guide/advanced/navigation-failures.md

@@ -2,16 +2,16 @@
 
 > New in 3.4.0
 
-When using `router-link`, Vue Router internally calls `router.push` to trigger a navigation. Depending on the current location and existing [Navigation Guards](./navigation-guards.md), this navigation might end up in a new page being shown, but there are a couple of situations where we will stay on the same page:
+When using `router-link`, Vue Router calls `router.push` to trigger a navigation. While the expected behavior for most links is to navigate a user to a new page, there are a few situations where users will remain on the same page:
 
 - We are already on the page we are trying to go to
-- A navigation guard aborts the navigation by calling `next(false)`
-- A navigation guard throws an error or calls `next(new Error())`
+- A [navigation guard](./navigation-guards.md) aborts the navigation by calling `next(false)`
+- A [navigation guard](./navigation-guards.md) throws an error or calls `next(new Error())`
 
 When using a regular `router-link`, **none of these failures will log an error**. However, if you are using `router.push` or `router.replace`, you might come across an _"Uncaught (in promise) Error"_ message followed by a more specific message in your console. Let's understand how to differentiate _Navigation Failures_.
 
 ::: tip Background story
- _Navigation Failures_ were exposed on version 3.2.0 but existed for a long time before: through the two optional callbacks of `router.push`, `onComplete` and `onAbort` that can be passed to `router.push`. Since version 3.1.0, `router.push` and `router.replace` return a _Promise_ if no `onComplete`/`onAbort` callback is provided. This _Promise_ resolves instead of invoking `onComplete` and rejects instead of invoking `onAbort`.
+ In v3.2.0, _Navigation Failures_ were exposed through the two optional callbacks of `router.push`: `onComplete` and `onAbort`. Since version 3.1.0, `router.push` and `router.replace` return a _Promise_ if no `onComplete`/`onAbort` callback is provided. This _Promise_ resolves instead of invoking `onComplete` and rejects instead of invoking `onAbort`.
  :::
 
 ## Detecting Navigation Failures
@@ -36,7 +36,7 @@ If you omit the second parameter: `isNavigationFailure(failure)`, it will only c
 
 ## `NavigationFailureType`
 
-`NavigationFailureType` exposes the following properties to differentiate _Navigation Failures_:
+`NavigationFailureType` help developers to differentiate between the various types of _Navigation Failures_. There are four different types:
 
 - `redirected`: `next(newLocation)` was called inside of a navigation guard to redirect somewhere else.
 - `aborted`: `next(false)` was called inside of a navigation guard to the navigation.
@@ -57,4 +57,4 @@ router.push('/admin').catch(failure => {
 })
 ```
 
-In all cases, `from` and `to` are normalized route locations.
+In all cases, `to` and `from` are normalized route locations.