pingcap · ti-chi-bot · Jun 15, 2022 · May 12, 2022 · May 12, 2022 · May 12, 2022
diff --git a/clinic/clinic-user-guide-for-tiup.md b/clinic/clinic-user-guide-for-tiup.md
@@ -48,7 +48,7 @@ Before using PingCAP Clinic, you need to install Diag (a component to collect da
 
     > **Note:**
     >
-    > - For clusters without an internet connection, you need to deploy Diag offline. For details, refer to [Deploy TiUP offline: Method 2](/production-deployment-using-tiup.md#method-2-deploy-tiup-offline).
+    > - For clusters without an internet connection, you need to deploy Diag offline. For details, refer to [Deploy TiUP offline: Method 2](/production-deployment-using-tiup.md#deploy-tiup-offline).
     > - Diag is **only** provided in the TiDB Server offline mirror package of v5.4.0 or later.
 
 2. Get and set an access token (token) to upload data.

diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md
@@ -40,7 +40,7 @@ Other Linux OS versions such as Debian Linux and Fedora Linux might work but are
 
 > **Note:**
 >
-> It is required that you [deploy TiUP on the control machine](/production-deployment-using-tiup.md#step-2-install-tiup-on-the-control-machine) to operate and manage TiDB clusters.
+> It is required that you [deploy TiUP on the control machine](/production-deployment-using-tiup.md#step-2-deploy-tiup-on-the-control-machine) to operate and manage TiDB clusters.
 
 ### Target machines
 

diff --git a/migration-tools.md b/migration-tools.md
@@ -101,5 +101,5 @@ tiup update --self && tiup update dm
 
 ## See also
 
-- [Deploy TiUP offline](/production-deployment-using-tiup.md#method-2-deploy-tiup-offline)
+- [Deploy TiUP offline](/production-deployment-using-tiup.md#deploy-tiup-offline)
 - [Download and install tools in binary](/download-ecosystem-tools.md)
diff --git a/production-deployment-using-tiup.md b/production-deployment-using-tiup.md
diff --git a/scale-tidb-using-tiup.md b/scale-tidb-using-tiup.md
diff --git a/tiup/tiup-cluster.md b/tiup/tiup-cluster.md
@@ -220,7 +220,7 @@ For the PD component, `|L` or `|UI` might be appended to `Up` or `Down`. `|L` in
 
 > **Note:**
 >
-> This section describes only the syntax of the scale-in command. For detailed steps of online scaling, refer to [Scale the TiDB Cluster Using TiUP](/scale-tidb-using-tiup.md).
+> This section describes only the syntax of the scale-in command. For detailed steps of online scaling, refer to [Scale a TiDB Cluster Using TiUP](/scale-tidb-using-tiup.md).
 
 Scaling in a cluster means making some node(s) offline. This operation removes the specific node(s) from the cluster and deletes the remaining files.
 
@@ -289,7 +289,7 @@ After PD schedules the data on the node to other TiKV nodes, this node will be d
 
 > **Note:**
 >
-> This section describes only the syntax of the scale-out command. For detailed steps of online scaling, refer to [Scale the TiDB Cluster Using TiUP](/scale-tidb-using-tiup.md).
+> This section describes only the syntax of the scale-out command. For detailed steps of online scaling, refer to [Scale a TiDB Cluster Using TiUP](/scale-tidb-using-tiup.md).
 
 The scale-out operation has an inner logic similar to that of deployment: the TiUP cluster component firstly ensures the SSH connection of the node, creates the required directories on the target node, then executes the deployment operation, and starts the node service.
 

diff --git a/tiup/tiup-mirror.md b/tiup/tiup-mirror.md
@@ -124,7 +124,7 @@ tiup list
 If you run the `tiup mirror clone` command again with the same `target-dir`, the machine will create new manifests and download the latest versions of components available.
 
 > **Note:**
-> 
+>
 > Before recreating the manifest, ensure that all components and versions (including earlier ones downloaded previously) are included.
 
 ## Custom repository
@@ -192,15 +192,15 @@ tiup mirror grant jdoe
     ```bash
     $ tiup hello
     ```
-    
+
     ```
     The component `hello` version  is not installed; downloading from repository.
     Starting component `hello`: /home/dvaneeden/.tiup/components/hello/v0.0.1/hello
     hello
     ```
-    
+
     With `tiup mirror merge`, you can merge a repository with custom components into another one. This assumes that all components in `/data/my_custom_components` are signed by the current `$USER`.
-    
+
     ```bash
     $ tiup mirror set /data/my_mirror
     $ tiup mirror grant $USER

diff --git a/upgrade-tidb-using-tiup.md b/upgrade-tidb-using-tiup.md
@@ -73,7 +73,7 @@ Before upgrading your TiDB cluster, you first need to upgrade TiUP or TiUP mirro
 >
 > If the cluster to upgrade was deployed not using the offline method, skip this step.
 
-Refer to [Deploy a TiDB Cluster Using TiUP - Deploy TiUP offline](/production-deployment-using-tiup.md#method-2-deploy-tiup-offline) to download the TiUP mirror of the new version and upload it to the control machine. After executing `local_install.sh`, TiUP will complete the overwrite upgrade.
+Refer to [Deploy a TiDB Cluster Using TiUP - Deploy TiUP offline](/production-deployment-using-tiup.md#deploy-tiup-offline) to download the TiUP mirror of the new version and upload it to the control machine. After executing `local_install.sh`, TiUP will complete the overwrite upgrade.
 
 {{< copyable "shell-regular" >}}