docs: fix navigation-failures type count (#767)

Co-authored-by: xiaaa123 <3288432965@qq.com>

diff --git a/docs/guide/advanced/navigation-failures.md b/docs/guide/advanced/navigation-failures.md
index e9247c332bbd2c6c3b7d319951a16fb34305da79..54f34b61c2376c0ba0d2c3d8378b065a7efc5e71 100644 (file)
--- a/docs/guide/advanced/navigation-failures.md
+++ b/docs/guide/advanced/navigation-failures.md
@@ -59,7 +59,7 @@ If you omit the second parameter: `isNavigationFailure(failure)`, it will only c
 
 ## Differentiating Navigation Failures
 
-As we said at the beginning, there are different situations aborting a navigation, all of them resulting in different _Navigation Failures_. They can be differentiated using the `isNavigationFailure` and `NavigationFailureType`. There are four different types:
+As we said at the beginning, there are different situations aborting a navigation, all of them resulting in different _Navigation Failures_. They can be differentiated using the `isNavigationFailure` and `NavigationFailureType`. There are three different types:
 
 - `aborted`: `false` was returned inside of a navigation guard to the navigation.
 - `cancelled`: A new navigation took place before the current navigation could finish. e.g. `router.push` was called while waiting inside of a navigation guard.