Apply suggestions from code review

pingcap · Aug 20, 2021 · d7cca2f · d7cca2f
1 parent 1bf5648
commit d7cca2f
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/config-templates/geo-redundancy-deployment.yaml b/config-templates/geo-redundancy-deployment.yaml
@@ -29,7 +29,7 @@ server_configs:
   pd:
     replication.location-labels: ["zone","dc","rack","host"]
     replication.max-replicas: 5
-    label-property:  # Since TiDB 5.2, the `label-property` configuration is not supported by default. To set the replica policy, use the Placement Rules.
+    label-property:  # Since TiDB 5.2, the `label-property` configuration is not supported by default. To set the replica policy, use the placement rules.
       reject-leader:
         - key: "dc"
           value: "sha"

diff --git a/geo-distributed-deployment-topology.md b/geo-distributed-deployment-topology.md
@@ -86,7 +86,7 @@ This section describes the key parameter configuration of the TiDB geo-distribut
 
    > **Note:**
    >
-   > Since TiDB 5.2, the `label-property` configuration is not supported by default. To set the replica policy, use the [Placement Rules](/configure-placement-rules.md).
+   > Since TiDB 5.2, the `label-property` configuration is not supported by default. To set the replica policy, use the [placement rules](/configure-placement-rules.md).
 
 For the further information about labels and the number of Raft Group replicas, see [Schedule Replicas by Topology Labels](/schedule-replicas-by-topology-labels.md).
 

diff --git a/multi-data-centers-in-one-city-deployment.md b/multi-data-centers-in-one-city-deployment.md
@@ -73,7 +73,7 @@ member leader_priority pdName3 3
 
 > **Note:**
 > 
-> Since TiDB 5.2, the `label-property` configuration is not supported by default. To set the replica policy, use the [Placement Rules](/configure-placement-rules.md).
+> Since TiDB 5.2, the `label-property` configuration is not supported by default. To set the replica policy, use the [placement rules](/configure-placement-rules.md).
 
 **Disadvantages:**
 

diff --git a/three-data-centers-in-two-cities-deployment.md b/three-data-centers-in-two-cities-deployment.md
@@ -195,7 +195,7 @@ In the deployment of three DCs in two cities, to optimize performance, you need
 
    > **Note:**
    >
-   > Since TiDB 5.2, the `label-property` configuration is not supported by default. To set the replica policy, use the [Placement Rules](/configure-placement-rules.md).
+   > Since TiDB 5.2, the `label-property` configuration is not supported by default. To set the replica policy, use the [placement rules](/configure-placement-rules.md).
 
 - Configure the priority of PD. To avoid the situation where the PD leader is in another city (IDC3), you can increase the priority of local PD (in Seattle) and decrease the priority of PD in another city (San Francisco). The larger the number, the higher the priority.