diff --git a/docs/nightly/en/user-guide/operations/region-failover.md b/docs/nightly/en/user-guide/operations/region-failover.md
index 6c236ba05..3e2b1fd00 100644
--- a/docs/nightly/en/user-guide/operations/region-failover.md
+++ b/docs/nightly/en/user-guide/operations/region-failover.md
@@ -50,7 +50,7 @@ A simple model to estimate the read amplification factor (replay data size/actua
 - For a single topic, if we try to replay all regions that belong to the topic, then the amplification factor would be 7+6+...+1 = 28 times. (The Region WAL data distribution is shown in the Figure 1. Replaying Region 3 will read 7 times redundant data larger than the actual size; Region 6 will read 6 times, and so on)
 - When recovering 100 regions (requiring about 13 topics), the amplification factor is approximately 28 \* 13 = 364 times.
 
-Assuming we have 100 regions to recover, and the actual data size of all region is 0.5GB, the following table shows the replay data size based on the number of regions per topic.
+Assuming we have 100 regions to recover, and the actual data size of all regions is 0.5GB, the following table shows the replay data size based on the number of regions per topic.
 
 | Number of regions per Topic | Number of topics required for 100 Regions | Single topic read amplification factor | Total reading amplification factor | Replay data size (GB) |
 | --------------------------- | ----------------------------------------- | -------------------------------------- | ---------------------------------- | ---------------- |