fix dead links

Author: yyx990803

src/api/options-lifecycle.md

@@ -12,7 +12,7 @@ All lifecycle hooks automatically have their `this` context bound to the instanc
 
   Called synchronously immediately after the instance has been initialized, before data observation and event/watcher setup.
 
-- **See also:** [Lifecycle Diagram](/guide/components/lifecycle)
+- **See also:** [Lifecycle Diagram](/guide/essentials/lifecycle.html#lifecycle-diagram)
 
 ## created
 
@@ -22,7 +22,7 @@ All lifecycle hooks automatically have their `this` context bound to the instanc
 
   Called synchronously after the instance is created. At this stage, the instance has finished processing the options which means the following have been set up: data observation, computed properties, methods, watch/event callbacks. However, the mounting phase has not been started, and the `$el` property will not be available yet.
 
-- **See also:** [Lifecycle Diagram](/guide/components/lifecycle)
+- **See also:** [Lifecycle Diagram](/guide/essentials/lifecycle.html#lifecycle-diagram)
 
 ## beforeMount
 
@@ -34,7 +34,7 @@ All lifecycle hooks automatically have their `this` context bound to the instanc
 
   **This hook is not called during server-side rendering.**
 
-- **See also:** [Lifecycle Diagram](/guide/components/lifecycle)
+- **See also:** [Lifecycle Diagram](/guide/essentials/lifecycle.html#lifecycle-diagram)
 
 ## mounted
 
@@ -57,7 +57,7 @@ All lifecycle hooks automatically have their `this` context bound to the instanc
 
   **This hook is not called during server-side rendering.**
 
-- **See also:** [Lifecycle Diagram](/guide/components/lifecycle)
+- **See also:** [Lifecycle Diagram](/guide/essentials/lifecycle.html#lifecycle-diagram)
 
 ## beforeUpdate
 
@@ -69,7 +69,7 @@ All lifecycle hooks automatically have their `this` context bound to the instanc
 
   **This hook is not called during server-side rendering, because only the initial render is performed server-side.**
 
-- **See also:** [Lifecycle Diagram](/guide/components/lifecycle)
+- **See also:** [Lifecycle Diagram](/guide/essentials/lifecycle.html#lifecycle-diagram)
 
 ## updated
 
@@ -94,7 +94,7 @@ All lifecycle hooks automatically have their `this` context bound to the instanc
 
   **This hook is not called during server-side rendering.**
 
-- **See also:** [Lifecycle Diagram](/guide/components/lifecycle)
+- **See also:** [Lifecycle Diagram](/guide/essentials/lifecycle.html#lifecycle-diagram)
 
 ## activated
 
@@ -132,7 +132,7 @@ All lifecycle hooks automatically have their `this` context bound to the instanc
 
   **This hook is not called during server-side rendering.**
 
-- **See also:** [Lifecycle Diagram](/guide/components/lifecycle)
+- **See also:** [Lifecycle Diagram](/guide/essentials/lifecycle.html#lifecycle-diagram)
 
 ## unmounted
 
@@ -144,7 +144,7 @@ All lifecycle hooks automatically have their `this` context bound to the instanc
 
   **This hook is not called during server-side rendering.**
 
-- **See also:** [Lifecycle Diagram](/guide/components/lifecycle)
+- **See also:** [Lifecycle Diagram](/guide/essentials/lifecycle.html#lifecycle-diagram)
 
 ## errorCaptured
 

src/guide/advanced/ssr/universal.md

@@ -10,7 +10,7 @@ Because the actual rendering process needs to be deterministic, we will also be
 
 ## Component Lifecycle Hooks
 
-Since there are no dynamic updates, the only [lifecycle hooks](/guide/components/lifecycle.html) that will be called during SSR are `beforeCreate` and `created`. This means any code inside other lifecycle hooks such as `beforeMount` or `mounted` will only be executed on the client.
+Since there are no dynamic updates, the only [lifecycle hooks](/guide/essentials/lifecycle.html) that will be called during SSR are `beforeCreate` and `created`. This means any code inside other lifecycle hooks such as `beforeMount` or `mounted` will only be executed on the client.
 
 Another thing to note is that you should avoid code that produces global side effects in `beforeCreate` and `created`, for example setting up timers with `setInterval`. In client-side only code we may setup a timer and then tear it down in `beforeUnmount` or `unmounted`. However, because the destroy hooks will not be called during SSR, the timers will stay around forever. To avoid this, move your side-effect code into `beforeMount` or `mounted` instead.
 

src/guide/essentials/template-syntax.md

@@ -123,7 +123,7 @@ It is possible to call a component-exposed method inside a binding expression. A
 </span>
 ```
 
-Functions called inside binding expressions should **not** have any side effects, such as changing data or triggering asynchronous operations. If you find yourself tempted to do that you should probably use a [lifecycle hook](/guide/components/lifecycle.html) instead.
+Functions called inside binding expressions should **not** have any side effects, such as changing data or triggering asynchronous operations. If you find yourself tempted to do that you should probably use a [lifecycle hook](/guide/essentials/lifecycle.html) instead.
 
 ### Restricted Globals Access