diff --git a/grafana-tikv-dashboard.md b/grafana-tikv-dashboard.md
index cc432eb915c3e..6e164034f225d 100644
--- a/grafana-tikv-dashboard.md
+++ b/grafana-tikv-dashboard.md
@@ -452,17 +452,17 @@ The following metrics are related to [TiKV MVCC In-Memory Engine](/tikv-in-memor
 - Total pessimistic locks memory size: The memory size occupied by the in-memory pessimistic locks
 - In-memory pessimistic locking result: The result of only saving pessimistic locks to memory. `full` means the number of times that the pessimistic lock is not saved to memory because the memory limit is exceeded.
 
-### Resolved-TS
+### Resolved TS
 
-- Resolved-TS worker CPU: The CPU utilization of the resolved-ts worker threads
-- Advance-TS worker CPU: The CPU utilization of the advance-ts worker threads
-- Scan lock worker CPU: The CPU utilization of the scan lock worker threads
+- Resolved TS Worker CPU: The CPU utilization of the resolved-ts worker threads
+- Advance ts Worker CPU: The CPU utilization of the advance-ts worker threads
+- Scan lock Worker CPU: The CPU utilization of the scan lock worker threads
 - Max gap of resolved-ts: The maximum time difference between the resolved-ts of all active Regions in this TiKV and the current time
-- Max gap of safe-ts: The maximum time difference between the safe-ts of all active Regions in this TiKV and the current time
+- Max gap of follower safe-ts: The maximum time difference between the minimum non-zero safe-ts of followers in this TiKV and the current time
 - Min Resolved TS Region: The ID of the Region whose resolved-ts is the minimal
-- Min Safe TS Region: The ID of the Region whose safe-ts is the minimal
-- Check Leader Duration: The distribution of time spent on processing leader requests. The duration is from sending requests to receiving responses in leader
-- Max gap of resolved-ts in Region leaders: The maximum time difference between the resolved-ts of all active Regions in this TiKV and the current time, only for Region leaders
+- Min Safe TS Follower Region: The ID of the follower Region whose safe-ts is the minimal
+- Check leader duration: The distribution of time spent on processing leader requests. The duration is from sending requests to receiving responses in leader
+- Max gap of resolved-ts in region leaders: The maximum time difference between the resolved-ts of all active Regions in this TiKV and the current time, only for Region leaders
 - Min Leader Resolved TS Region: The ID of the Region whose resolved-ts is the minimal, only for Region leaders
 - Lock heap size: The size of the heap that tracks locks in the resolved-ts module
 
diff --git a/tikv-control.md b/tikv-control.md
index e1049099c57f2..0206bd786dded 100644
--- a/tikv-control.md
+++ b/tikv-control.md
@@ -648,7 +648,7 @@ From the output above, you can see that the information of the damaged SST file
 
 ### Get the state of a Region's `RegionReadProgress`
 
-Starting from v6.5.4 and v7.3.0, TiKV introduces the `get-region-read-progress` subcommand to get up-to-date details of the resolver and `RegionReadProgress`. You need to specify a Region ID and a TiKV, which can be obtained from Grafana (`Min Resolved TS Region` and `Min Safe TS Region`) or `DataIsNotReady` logs.
+Starting from v6.5.4 and v7.3.0, TiKV introduces the `get-region-read-progress` subcommand to get up-to-date details of the resolver and `RegionReadProgress`. You need to specify a Region ID and a TiKV, which can be obtained from Grafana (`Min Resolved TS Region` and `Min Safe TS Follower Region`) or `DataIsNotReady` logs.
 
 - `--log` (optional): If specified, TiKV logs the smallest `start_ts` of locks in the Region's resolver in this TiKV at `INFO` level. This option helps you identify locks that might block resolved-ts in advance.
 
diff --git a/troubleshoot-stale-read.md b/troubleshoot-stale-read.md
index 112e1ac045943..d242d8ceb1ade 100644
--- a/troubleshoot-stale-read.md
+++ b/troubleshoot-stale-read.md
@@ -160,7 +160,7 @@ To address this issue:
 
 ### Address CheckLeader issues
 
-To address CheckLeader issues, you can check the network and the **Check Leader Duration** metric in [**TiKV-Details** > **Resolved-TS** dashboard](/grafana-tikv-dashboard.md#resolved-ts).
+To address CheckLeader issues, you can check the network and the **Check leader duration** metric in [**TiKV-Details** > **Resolved TS** dashboard](/grafana-tikv-dashboard.md#resolved-ts).
 
 ## Example