diff --git a/faq/tidb-faq.md b/faq/tidb-faq.md
index 6b84f74f0bb7e..2b9dd0ad7083e 100644
--- a/faq/tidb-faq.md
+++ b/faq/tidb-faq.md
@@ -112,9 +112,9 @@ As a standalone database, MySQL can only implement across-database transactions
 - [TiFlash](/tiflash/tiflash-overview.md) introduces a special structure named DeltaTree to process the modification of the columnar engine.
 - TiFlash acts as the learner role in a Raft group, so it does not vote for the log commit or writes. This means that DML operations do not have to wait for the acknowledgment of TiFlash, which is why TiFlash does not slow down the OLTP performance. In addition, TiFlash and TiKV work in separate instances, so they do not affect each other.
 
-### Is TiFlash eventually consistent?
+### What kind of consistency does TiFlash provide?
 
-Yes. TiFlash maintains strong data consistency by default.
+TiFlash maintains strong data consistency by default. The raft learner process updates the data. There is also a TSO check to ensure the data in queries is fully consistent with the transaction. For more information, see [Asynchronous replication](/tiflash/tiflash-overview.md#asynchronous-replication) and [Consistency](/tiflash/tiflash-overview.md#consistency).
 
 ## TiDB techniques
 
diff --git a/schedule-replicas-by-topology-labels.md b/schedule-replicas-by-topology-labels.md
index dd0bce09e1564..188c3f5e57343 100644
--- a/schedule-replicas-by-topology-labels.md
+++ b/schedule-replicas-by-topology-labels.md
@@ -140,21 +140,25 @@ server_configs:
 tikv_servers:
 # z1
   - host: tikv-1
+    port：20160
     config:
       server.labels:
         zone: z1
         host: h1
-   - host: tikv-2
+   - host: tikv-1
+     port：20161
     config:
       server.labels:
         zone: z1
         host: h1
-  - host: tikv-3
+  - host: tikv-2
+    port：20160
     config:
       server.labels:
         zone: z1
         host: h2
-  - host: tikv-4
+  - host: tikv-2
+    port：20161
     config:
       server.labels:
         zone: z1