diff --git a/docs/en/essentials/navigation.md b/docs/en/essentials/navigation.md
index af6dc4f94..7c421e938 100644
--- a/docs/en/essentials/navigation.md
+++ b/docs/en/essentials/navigation.md
@@ -45,6 +45,8 @@ The same rules apply for the `to` property of the `router-link` component.
 
 In 2.2.0+, optionally provide `onComplete` and `onAbort` callbacks to `router.push` or `router.replace` as the 2nd and 3rd arguments. These callbacks will be called when the navigation either successfully completed (after all async hooks are resolved), or aborted (navigated to the same route, or to a different route before current navigation has finished), respectively.
 
+**Note:** If the destination is the same as the current route and only params are changing (eg: going from one profile to another `/users/1` -> `/users/2`), you will have to use [beforeRouteUpdate](./dynamic-matching.html#reacting-to-params-changes) to react to changes (eg: fetching the user information).
+
 #### `router.replace(location, onComplete?, onAbort?)`
 
 It acts like `router.push`, the only difference is that it navigates without pushing a new history entry, as its name suggests - it replaces the current entry.