Doc EN: navigation-guards.md: minor adjustements (#1600)

Signed-off-by: Bruno Lesieur <bruno.lesieur@gmail.com>

Author: MachinisteWeb

docs/en/advanced/navigation-guards.md

@@ -91,8 +91,8 @@ const Foo = {
   beforeRouteUpdate (to, from, next) {
     // called when the route that renders this component has changed,
     // but this component is reused in the new route.
-    // For example, for a route with dynamic params /foo/:id, when we
-    // navigate between /foo/1 and /foo/2, the same Foo component instance
+    // For example, for a route with dynamic params `/foo/:id`, when we
+    // navigate between `/foo/1` and `/foo/2`, the same `Foo` component instance
     // will be reused, and this hook will be called when that happens.
     // has access to `this` component instance.
   },
@@ -120,14 +120,14 @@ You can directly access `this` inside `beforeRouteLeave`. The leave guard is usu
 
 ### The Full Navigation Resolution Flow
 
-1. Navigation triggered
-2. Call leave guards in deactivated components
-3. Call global `beforeEach` guards
-4. Call `beforeRouteUpdate` guards in reused components (2.2+)
-5. Call `beforeEnter` in route configs
-6. Resolve async route components
-7. Call `beforeRouteEnter` in activated components
-8. Call global `beforeResolve` guards (2.5+)
+1. Navigation triggered.
+2. Call leave guards in deactivated components.
+3. Call global `beforeEach` guards.
+4. Call `beforeRouteUpdate` guards in reused components (2.2+).
+5. Call `beforeEnter` in route configs.
+6. Resolve async route components.
+7. Call `beforeRouteEnter` in activated components.
+8. Call global `beforeResolve` guards (2.5+).
 9. Navigation confirmed.
 10. Call global `afterEach` hooks.
 11. DOM updates triggered.