revise translation

Author: qiancai

pd-configuration-file.md

@@ -295,7 +295,7 @@ Configuration items related to scheduling
 
 ### `max-affinity-merge-region-size` <span class="version-mark">Introduced in versions v8.5.5 and v9.0.0</span>
 
-+ Controls the threshold for automatically merging small adjacent Regions that belong to the same [affinity](/table-affinity.md) group. When a Region belongs to an affinity group and its size is less than this configuration value, PD will attempt to merge this Region with other small adjacent Regions within the same affinity group to reduce the number of Regions and maintain the affinity effect.
++ Controls the threshold for automatically merging small adjacent Regions that belong to the same [affinity](/table-affinity.md) group. When a Region belongs to an affinity group and its size is smaller than this threshold, PD attempts to merge this Region with other small adjacent Regions in the same affinity group to reduce the number of Regions and maintain the affinity effect.
 + Setting it to `0` disables the automatic merging of small adjacent Regions within an affinity group.
 + Default value: 256
 + Unit: MiB
@@ -382,8 +382,8 @@ Configuration items related to scheduling
 
 ### `affinity-schedule-limit` <span class="version-mark">Introduced in versions v8.5.5 and v9.0.0</span>
 
-+ Controls the number of concurrent [affinity](/table-affinity.md) scheduling tasks. Setting it to `0` disables affinity scheduling.
-+ Default value: 0
++ Controls the number of [affinity](/table-affinity.md) scheduling tasks that can be performed concurrently. Setting it to `0` disables affinity scheduling.
++ Default value: `0`
 
 ### `high-space-ratio`
 

sql-statements/sql-statement-alter-table.md

@@ -55,6 +55,7 @@ AlterTableSpec ::=
         | TTLEnable EqOpt ( 'ON' | 'OFF' )
         | TTLJobInterval EqOpt stringLit
     )
+|   'AFFINITY' EqOpt stringLit
 |   PlacementPolicyOption
 
 PlacementPolicyOption ::=
@@ -182,7 +183,7 @@ The following major restrictions apply to `ALTER TABLE` in TiDB:
 
 - Changes of some data types (for example, some TIME, Bit, Set, Enum, and JSON types) are not supported due to the compatibility issues of the `CAST` function's behavior between TiDB and MySQL.
 
-- `AFFINITY` option is a TiDB extension syntax. After enabling `AFFINITY`, changing the table's partition scheme (e.g., adding, deleting, reorganizing, or swapping partitions) is not supported. You need to remove `AFFINITY` first.
+- `AFFINITY` option is a TiDB extension syntax. After `AFFINITY` is enabled for a table, modifying the partition scheme (such as adding, dropping, reorganizing, or swapping partitions) of that table is not supported. You need to remove `AFFINITY` first.
 
 - Spatial data types are not supported.
 

sql-statements/sql-statement-create-table.md

@@ -173,12 +173,25 @@ The following *table_options* are supported. Other options such as `AVG_ROW_LENG
 | `CHARACTER SET` | To specify the [character set](/character-set-and-collation.md) for the table | `CHARACTER SET` =  'utf8mb4' |
 | `COLLATE` | To specify the character set collation for the table | `COLLATE` = 'utf8mb4_bin' |
 | `COMMENT` | The comment information | `COMMENT` = 'comment info' |
-| `AFFINITY` | Enables affinity scheduling for a table or partition. For non-partitioned tables, it can be set to `'table'`; for partitioned tables, it can be set to `'partition'`. Setting it to `'none'` or leaving it empty disables affinity scheduling. | `AFFINITY` = 'table' |
+| `AFFINITY` | Enables affinity scheduling for a table or partition. It can be set to `'table'` for non-partitioned tables and `'partition'` for partitioned tables. Setting it to `'none'` or leaving it empty disables affinity scheduling. | `AFFINITY` = 'table' |
+
+<CustomContent platform="tidb">
 
 > **Note:**
 >
 > - The `split-table` configuration option is enabled by default. When it is enabled, a separate Region is created for each newly created table. For details, see [TiDB configuration file](/tidb-configuration-file.md).
-> - When using `AFFINITY`, changing the partitioning scheme of a table (such as adding, deleting, reorganizing, or swapping partitions) is not supported, nor is setting this option on temporary tables or views.
+> - Before using `AFFINITY`, note that modifying the partitioning scheme (such as adding, dropping, reorganizing, or swapping partitions) of a table with affinity enabled is not supported, and configuring `AFFINITY` on temporary tables or views is not supported.
+
+</CustomContent>
+
+<CustomContent platform="tidb-cloud">
+
+> **Note:**
+>
+> - TiDB creates a separate Region for each newly created table.
+> - Before using `AFFINITY`, note that modifying the partitioning scheme (such as adding, dropping, reorganizing, or swapping partitions) of a table with affinity enabled is not supported, and configuring `AFFINITY` on temporary tables or views is not supported.
+
+</CustomContent>
 
 ## Examples
 

sql-statements/sql-statement-show-affinity.md

@@ -1,13 +1,13 @@
 ---
 title: SHOW AFFINITY
-summary: Overview of using SHOW AFFINITY in TiDB database.
+summary: An overview of the usage of SHOW AFFINITY for the TiDB database.
 ---
 
-# SHOW AFFINITY <span class="version-mark">Introduced in v8.5.5 and v9.0.0</span>
+# SHOW AFFINITY <span class="version-mark">New in v8.5.5 and v9.0.0</span>
 
-The `SHOW AFFINITY` statement is used to view the [affinity](/table-affinity.md) scheduling information of tables configured with the `AFFINITY` option, and the target replica distribution currently recorded by PD.
+The `SHOW AFFINITY` statement shows [affinity](/table-affinity.md) scheduling information for tables configured with the `AFFINITY` option, as well as the target replica distribution currently recorded by PD.
 
-## Grammar Diagram
+## Synopsis
 
 ```ebnf+diagram
 ShowAffinityStmt ::=
@@ -18,7 +18,7 @@ ShowAffinityStmt ::=
 
 ## Examples
 
-The following examples create two tables with affinity scheduling enabled and view their scheduling information:
+The following examples create two tables with affinity scheduling enabled and show how to view their scheduling information:
 
 ```sql
 CREATE TABLE t1 (a INT) AFFINITY = 'table';
@@ -41,21 +41,21 @@ The example output is as follows:
 
 The meaning of each column is as follows:
 
-- `Leader_store_id`, `Voter_store_ids`: The TiKV Store IDs where PD records the target Leader replica and Voter replicas for this table or partition. If the affinity group has not yet determined the target replica locations or if [`schedule.affinity-schedule-limit`](/pd-configuration-file.md#affinity-schedule-limit-从-v855-和-v900-版本开始引入) is `0`, it displays as `NULL`.
-- `Status`: Indicates the current status of affinity scheduling. Possible values are:
-    - `Pending`: PD has not yet performed affinity scheduling for this table or partition (e.g., when Leader or Voter is not determined).
+- `Leader_store_id`, `Voter_store_ids`: the IDs of TiKV stores recorded by PD, indicating which stores host the target Leader and Voter replicas for the table or partitions. If the target replica locations for the affinity group are not determined, or if [`schedule.affinity-schedule-limit`](/pd-configuration-file.md#affinity-schedule-limit-new-in-v855-and-v900) is set to `0`, the value is displayed as `NULL`.
+- `Status`: indicates the current status of affinity scheduling. Possible values are:
+    - `Pending`: PD has not started affinity scheduling for the table or partition, such as when Leaders or Voters are not yet determined.
     - `Preparing`: PD is scheduling Regions to meet affinity requirements.
-    - `Stable`: All Regions have reached the target distribution.
-- `Region_count`: The current number of Regions in this affinity group.
-- `Affinity_region_count`: The number of Regions that currently satisfy the affinity replica distribution requirements.
-    - When `Affinity_region_count` is less than `Region_count`, it indicates that some Regions have not yet completed replica scheduling based on affinity.
-    - When `Affinity_region_count` equals `Region_count`, it indicates that the Region replica migration scheduling based on affinity is complete, meaning that the distribution of all Regions meets the affinity requirements. However, this does not imply that related Region merge operations are complete.
+    - `Stable`: all Regions have reached the target distribution.
+- `Region_count`: the current number of Regions in the affinity group.
+- `Affinity_region_count`: the number of Regions that currently meet the affinity replica distribution requirements.
+    - When `Affinity_region_count` is less than `Region_count`, it indicates that some Regions have not yet completed affinity-replica scheduling.
+    - When `Affinity_region_count` equals `Region_count`, it indicates that affinity-replica scheduling is complete, meaning the distribution of all related Regions meets the affinity requirements. However, it does not indicate that related Region merge operations are completed.
 
-## MySQL Compatibility
+## MySQL compatibility
 
-This statement is an extension of MySQL syntax by TiDB.
+This statement is a TiDB extension to MySQL syntax.
 
-## See Also
+## See also
 
 - [`CREATE TABLE`](/sql-statements/sql-statement-create-table.md)
 - [`ALTER TABLE`](/sql-statements/sql-statement-alter-table.md)