diff --git a/develop/dev-guide-timeouts-in-tidb.md b/develop/dev-guide-timeouts-in-tidb.md
index f3185a789630..5f5088415b1a 100644
--- a/develop/dev-guide-timeouts-in-tidb.md
+++ b/develop/dev-guide-timeouts-in-tidb.md
@@ -30,7 +30,7 @@ Note that the system variable configuration takes effect globally and immediatel
 
 > **Tip:**
 >
-> Specifically, when Dumpling is exporting data from TiDB (less than 1 TB), if the TiDB version is later than or equal to v4.0.0 and Dumpling can access the PD address of the TiDB cluster, Dumpling automatically extends the GC time without affecting the original cluster.
+> Specifically, when Dumpling is exporting data from TiDB (less than 1 TB), if the TiDB version is v4.0.0 or later and Dumpling can access the PD address and the [`INFORMATION_SCHEMA.CLUSTER_INFO`](/information-schema/information-schema-cluster-info.md) table of the TiDB cluster, Dumpling automatically adjusts the GC safe point to block GC without affecting the original cluster.
 >
 > However, in either of the following scenarios, Dumpling cannot automatically adjust the GC time:
 >
diff --git a/dumpling-overview.md b/dumpling-overview.md
index 0bcd72e3864d..5e34ee5e8857 100644
--- a/dumpling-overview.md
+++ b/dumpling-overview.md
@@ -54,7 +54,7 @@ Dumpling has the following advantages:
 - Support exporting data to Amazon S3 cloud storage.
 - More optimizations are made for TiDB:
     - Support configuring the memory limit of a single TiDB SQL statement.
-    - If Dumpling can connect directly to PD, Dumpling supports automatic adjustment of TiDB GC time for TiDB v4.0.0 and later versions.
+    - If Dumpling can access the PD address and the [`INFORMATION_SCHEMA.CLUSTER_INFO`](/information-schema/information-schema-cluster-info.md) table of the TiDB cluster, Dumpling supports automatically adjusting the [GC](/garbage-collection-overview.md) safe point time to block GC for TiDB v4.0.0 and later versions.
     - Use TiDB's hidden column `_tidb_rowid` to optimize the performance of concurrent data export from a single table.
     - For TiDB, you can set the value of [`tidb_snapshot`](/read-historical-data.md#how-tidb-reads-data-from-history-versions) to specify the time point of the data backup. This ensures the consistency of the backup, instead of using `FLUSH TABLES WITH READ LOCK` to ensure the consistency.
 
@@ -344,7 +344,7 @@ When Dumpling is exporting a large single table from TiDB, Out of Memory (OOM) m
 
 ### Manually set the TiDB GC time
 
-When exporting data from TiDB (less than 1 TB), if the TiDB version is later than or equal to v4.0.0 and Dumpling can access the PD address of the TiDB cluster, Dumpling automatically extends the GC time without affecting the original cluster.
+When exporting data from TiDB (less than 1 TB), if the TiDB version is v4.0.0 or later and Dumpling can access the PD address and the [`INFORMATION_SCHEMA.CLUSTER_INFO`](/information-schema/information-schema-cluster-info.md) table of the TiDB cluster, Dumpling automatically adjusts the GC safe point to block GC without affecting the original cluster.
 
 However, in either of the following scenarios, Dumpling cannot automatically adjust the GC time:
 
diff --git a/migrate-from-tidb-to-mysql.md b/migrate-from-tidb-to-mysql.md
index 2daa1afc6b21..a2c35105e748 100644
--- a/migrate-from-tidb-to-mysql.md
+++ b/migrate-from-tidb-to-mysql.md
@@ -56,7 +56,7 @@ After setting up the environment, you can use [Dumpling](/dumpling-overview.md)
 
 1. Disable Garbage Collection (GC).
 
-    To ensure that newly written data is not deleted during incremental migration, you should disable GC for the upstream cluster before exporting full data. In this way, history data is not deleted. For TiDB v4.0.0 and later versions, Dumpling might [automatically extend the GC time](/dumpling-overview.md#manually-set-the-tidb-gc-time). Nevertheless, manually disabling GC is still necessary because the GC process might begin after Dumpling exits, leading to the failure of incremental changes migration.
+    To ensure that newly written data is not deleted during incremental migration, you should disable GC for the upstream cluster before exporting full data. In this way, history data is not deleted. For TiDB v4.0.0 and later versions, Dumpling might [automatically adjust the GC safe point to block GC](/dumpling-overview.md#manually-set-the-tidb-gc-time). Nevertheless, manually disabling GC is still necessary because the GC process might begin after Dumpling exits, leading to the failure of incremental changes migration.
 
     Run the following command to disable GC: