pingcap · qiancai · Oct 27, 2025 · Oct 27, 2025 · Nov 6, 2025 · Nov 18, 2025
diff --git a/partitioned-table.md b/partitioned-table.md
@@ -1704,7 +1704,7 @@ ERROR 8264 (HY000): Global Index is needed for index 'a', since the unique index
 
 Before the introduction of global indexes, TiDB created a local index for each partition, leading to [a limitation](#partitioning-keys-primary-keys-and-unique-keys) that primary keys and unique keys had to include the partition key to ensure data uniqueness. Additionally, when querying data across multiple partitions, TiDB needed to scan the data of each partition to return results.
 
-To address these issues, TiDB introduces the global indexes feature in v8.3.0. A global index covers the data of the entire table with a single index, allowing primary keys and unique keys to maintain global uniqueness without including all partition keys. Moreover, global indexes can access index data across multiple partitions in a single operation instead of looking up the local index for each partition, significantly improving query performance for non-partitioned keys. Starting from v9.0.0, non-unique indexes can also be created as global indexes.
+To address these issues, TiDB introduces the global indexes feature in v8.3.0. A global index covers the data of the entire table with a single index, allowing primary keys and unique keys to maintain global uniqueness without including all partition keys. Moreover, global indexes can access index data across multiple partitions in a single operation instead of looking up the local index for each partition, significantly improving query performance for non-partitioned keys. Starting from v8.5.4 and v9.0.0, non-unique indexes can also be created as global indexes.
 
 To create a global index, you can add the `GLOBAL` keyword in the index definition.
 

diff --git a/sql-statements/sql-statement-cancel-distribution-job.md b/sql-statements/sql-statement-cancel-distribution-job.md
@@ -3,7 +3,7 @@ title: CANCEL DISTRIBUTION JOB
 summary: An overview of the usage of CANCEL DISTRIBUTION JOB in TiDB.
 ---
 
-# CANCEL DISTRIBUTION JOB <span class="version-mark">New in v9.0.0</span>
+# CANCEL DISTRIBUTION JOB <span class="version-mark">New in v8.5.4 and v9.0.0</span>
 
 The `CANCEL DISTRIBUTION JOB` statement is used to cancel a Region scheduling task created using the [`DISTRIBUTE TABLE`](/sql-statements/sql-statement-distribute-table.md) statement in TiDB.
 

diff --git a/sql-statements/sql-statement-distribute-table.md b/sql-statements/sql-statement-distribute-table.md
@@ -3,7 +3,7 @@ title: DISTRIBUTE TABLE
 summary: An overview of the usage of DISTRIBUTE TABLE for the TiDB database.
 ---
 
-# DISTRIBUTE TABLE <span class="version-mark">New in v9.0.0</span>
+# DISTRIBUTE TABLE <span class="version-mark">New in v8.5.4 and v9.0.0</span>
 
 > **Warning:**
 >

diff --git a/sql-statements/sql-statement-show-distribution-jobs.md b/sql-statements/sql-statement-show-distribution-jobs.md
@@ -3,7 +3,7 @@ title: SHOW DISTRIBUTION JOBS
 summary: An overview of the usage of SHOW DISTRIBUTION JOBS for the TiDB database.
 ---
 
-# SHOW DISTRIBUTION JOBS <span class="version-mark">New in v9.0.0</span>
+# SHOW DISTRIBUTION JOBS <span class="version-mark">New in v8.5.4 and v9.0.0</span>
 
 The `SHOW DISTRIBUTION JOBS` statement shows all current Region distribution jobs.
 

diff --git a/sql-statements/sql-statement-show-table-distribution.md b/sql-statements/sql-statement-show-table-distribution.md
@@ -3,7 +3,7 @@ title: SHOW TABLE DISTRIBUTION
 summary: An overview of the usage of SHOW TABLE DISTRIBUTION for the TiDB database.
 ---
 
-# SHOW TABLE DISTRIBUTION <span class="version-mark">New in v9.0.0</span>
+# SHOW TABLE DISTRIBUTION <span class="version-mark">New in v8.5.4 and v9.0.0</span>
 
 The `SHOW TABLE DISTRIBUTION` statement shows the Region distribution information for a specified table.
 
@@ -27,7 +27,7 @@ TableName ::=
 
 ## Examples
 
-Show the Region distribution of the table `t1`:
+Show the Region distribution of the table `t`:
 
 ```sql
 CREATE TABLE `t` (
@@ -37,8 +37,8 @@ CREATE TABLE `t` (
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin 
 PARTITION BY RANGE (`a`)
 (PARTITION `p1` VALUES LESS THAN (10000),
- PARTITION `p2` VALUES LESS THAN (MAXVALUE)) |
-SHOW TABLE t1 DISTRIBUTIONS;
+ PARTITION `p2` VALUES LESS THAN (MAXVALUE));
+SHOW TABLE t DISTRIBUTIONS;
 ```
 
 ```

diff --git a/ticdc/ticdc-architecture.md b/ticdc/ticdc-architecture.md
@@ -156,7 +156,7 @@ To deploy TiCDC nodes in the new architecture using TiUP, take the following ste
 
 1. If your TiDB cluster does not have TiCDC nodes yet, refer to [Scale out a TiCDC cluster](/scale-tidb-using-tiup.md#scale-out-a-ticdc-cluster) to add new TiCDC nodes in the cluster. Otherwise, skip this step.
 
-2. If your TiDB cluster version is earlier than v8.5.4, you need to manually download the TiCDC binary package of new architecture, and then patch the downloaded file to your TiDB cluster. Otherwise, skip this step.
+2. If your TiDB cluster version is earlier than v8.5.4, you need to manually download the TiCDC binary package of the new architecture, and then patch the downloaded file to your TiDB cluster. Otherwise, skip this step.
 
     The download link follows this format: `https://tiup-mirrors.pingcap.com/cdc-${version}-${os}-${arch}.tar.gz`, where `${version}` is the TiCDC version (see [TiCDC releases for the new architecture](https://github.com/pingcap/ticdc/releases) for available versions), `${os}` is your operating system, and `${arch}` is the platform the component runs on (`amd64` or `arm64`).