en: fix dead external links (#613) (#615)

en/deploy-a-dm-cluster-using-tiup-offline.md

@@ -84,9 +84,9 @@ To switch the mirror to another directory, manually execute the `tiup mirror set
 
 ## Step 3: Edit the initialization configuration file
 
-You need to edit the cluster initialization configuration file according to different cluster topologies. 
+You need to edit the cluster initialization configuration file according to different cluster topologies.
 
-For the full configuration template, refer to the [TiUP configuration parameter template](https://github.com/pingcap/tiup/blob/master/examples/topology.example.yaml). Create a configuration file `topology.yaml`. In other combined scenarios, edit the configuration file as needed according to the templates.
+For the full configuration template, refer to the [TiUP configuration parameter template](https://github.com/pingcap/tiup/blob/master/embed/templates/examples/dm/topology.example.yaml). Create a configuration file `topology.yaml`. In other combined scenarios, edit the configuration file as needed according to the templates.
 
 The configuration of deploying three DM-masters, three DM-workers, and one monitoring component instance is as follows:
 
@@ -129,7 +129,7 @@ alertmanager_servers:
 >
 > - For parameters that should be effective on a specific node, configure these parameters in `config` of this node.
 >
-> - Use `.` to indicate the subcategory of the configuration, such as `log.slow-threshold`. For more formats, see [TiUP configuration template](https://github.com/pingcap/tiup/blob/master/examples/dm/topology.example.yaml).
+> - Use `.` to indicate the subcategory of the configuration, such as `log.slow-threshold`. For more formats, see [TiUP configuration template](https://github.com/pingcap/tiup/blob/master/embed/templates/examples/dm/topology.example.yaml).
 >
 > - For more parameter description, see [master `config.toml.example`](https://github.com/pingcap/dm/blob/master/dm/master/dm-master.toml) and [worker `config.toml.example`](https://github.com/pingcap/dm/blob/master/dm/worker/dm-worker.toml).
 >

en/deploy-a-dm-cluster-using-tiup.md

@@ -66,7 +66,7 @@ Log in to the control machine using a regular user account (take the `tidb` user
 
 According to the intended cluster topology, you need to manually create and edit the cluster initialization configuration file.
 
-You need to create a YAML configuration file (named `topology.yaml` for example) according to the [configuration file template](https://github.com/pingcap/tiup/blob/master/examples/dm/topology.example.yaml). For other scenarios, edit the configuration accordingly.
+You need to create a YAML configuration file (named `topology.yaml` for example) according to the [configuration file template](https://github.com/pingcap/tiup/blob/master/embed/templates/examples/dm/topology.example.yaml). For other scenarios, edit the configuration accordingly.
 
 The configuration of deploying three DM-masters, three DM-workers, and one monitoring component instance is as follows:
 
@@ -109,7 +109,7 @@ alertmanager_servers:
 >
 > - For parameters that should be effective on a specific node, configure these parameters in `config` of this node.
 >
-> - Use `.` to indicate the subcategory of the configuration, such as `log.slow-threshold`. For more formats, see [TiUP configuration template](https://github.com/pingcap/tiup/blob/master/examples/dm/topology.example.yaml).
+> - Use `.` to indicate the subcategory of the configuration, such as `log.slow-threshold`. For more formats, see [TiUP configuration template](https://github.com/pingcap/tiup/blob/master/embed/templates/examples/dm/topology.example.yaml).
 >
 > - For more parameter description, see [master `config.toml.example`](https://github.com/pingcap/dm/blob/master/dm/master/dm-master.toml) and [worker `config.toml.example`](https://github.com/pingcap/dm/blob/master/dm/worker/dm-worker.toml).
 >

en/maintain-dm-using-tiup.md

@@ -152,7 +152,7 @@ For example, to scale out a DM-worker node in the `prod-cluster` cluster, take t
     > **Note:**
     >
     > You need to create a topology file, which includes only the description of the new nodes, not the existing nodes.
-    > For more configuration items (such as the deployment directory), refer to this [TiUP configuration parameter example](https://github.com/pingcap/tiup/blob/master/examples/dm/topology.example.yaml).
+    > For more configuration items (such as the deployment directory), refer to this [TiUP configuration parameter example](https://github.com/pingcap/tiup/blob/master/embed/templates/examples/dm/topology.example.yaml).
 
     ```yaml
     ---
@@ -257,7 +257,7 @@ tiup dm patch prod-cluster /tmp/dm--hotfix.tar.gz -N 172.16.4.5:8261
 > **Note:**
 >
 > - TiUP does not support importing the DM Portal component in a DM 1.0 cluster.
-> - You need to stop the original cluster before importing. 
+> - You need to stop the original cluster before importing.
 > - Don't run `stop-task` for tasks that need to be upgraded to 2.0.
 > - TiUP only supports importing to a DM cluster of v2.0.0-rc.2 or a later version.
 > - The `import` command is used to import data from a DM 1.0 cluster to a new DM 2.0 cluster. If you need to import DM migration tasks to an existing DM 2.0 cluster, refer to [Manually Upgrade TiDB Data Migration from v1.0.x to v2.0.x](manually-upgrade-dm-1.0-to-2.0.md).
@@ -279,7 +279,7 @@ Execute `tiup list dm-master` to view the latest cluster version supported by Ti
 
 The process of using the `import` command is as follows:
 
-1. TiUP generates a topology file [`topology.yml`](https://github.com/pingcap/tiup/blob/master/examples/dm/topology.example.yaml) based on the DM cluster previously deployed using DM-Ansible.
+1. TiUP generates a topology file [`topology.yml`](https://github.com/pingcap/tiup/blob/master/embed/templates/examples/dm/topology.example.yaml) based on the DM cluster previously deployed using DM-Ansible.
 2. After confirming that the topology file has been generated, you can use it to deploy the DM cluster of v2.0 or later versions.
 
 After the deployment is completed, you can execute the `tiup dm start` command to start the cluster and begin the process of upgrading the DM kernel.