faq: refine the writing style of 3 faqs (#10586) (#10636)

pingcap · Oct 8, 2022 · 79b99f5 · 79b99f5
1 parent e745d3b
commit 79b99f5
Show file tree

Hide file tree

Showing 4 changed files with 56 additions and 53 deletions.
diff --git a/faq/high-availability-faq.md b/faq/high-availability-faq.md
@@ -9,10 +9,10 @@ This document summarizes the FAQs related to high availability of TiDB.
 
 ## How is TiDB strongly consistent?
 
-Data is redundantly copied between TiKV nodes using the [Raft consensus algorithm](https://raft.github.io/) to ensure recoverability should a node failure occur.
+Data is redundantly replicated between TiKV nodes using the [Raft consensus algorithm](https://raft.github.io/) to ensure recoverability when a node failure occurs.
 
 At the bottom layer, TiKV uses a model of replication log + State Machine to replicate data. For the write requests, the data is written to a Leader and the Leader then replicates the command to its Followers in the form of log. When the majority of nodes in the cluster receive this log, this log is committed and can be applied into the State Machine.
 
 ## What's the recommended solution for the deployment of three geo-distributed data centers?
 
-The architecture of TiDB guarantees that it fully supports geo-distribution and multi-activeness. Your data and applications are always-on. All the outages are transparent to your applications and your data can recover automatically. The operation depends on the network latency and stability. It is recommended to keep the latency within 5ms. Currently, we already have similar use cases. For details, contact [info@pingcap.com](mailto:info@pingcap.com).
+The architecture of TiDB guarantees that it fully supports geo-distribution and multi-activeness. Your data and applications are always-on. All the outages are transparent to your applications and your data can recover automatically. The operation depends on the network latency and stability. It is recommended to keep the latency within 5ms. Currently, TiDB already has similar use cases. For details, see [Three Data Centers in Two Cities Deployment](/three-data-centers-in-two-cities-deployment.md).
diff --git a/faq/high-reliability-faq.md b/faq/high-reliability-faq.md
@@ -13,15 +13,17 @@ Yes. To encrypt data in the network traffic, you can [enable TLS between TiDB cl
 
 ## Does TiDB support modifying the MySQL version string of the server to a specific one that is required by the security vulnerability scanning tool?
 
-Since v3.0.8, TiDB supports modifying the version string of the server by modifying [`server-version`](/tidb-configuration-file.md#server-version) in the configuration file. When you deploy TiDB using TiUP, you can also specify the proper version string by executing `tiup cluster edit-config <cluster-name>`:
+- Since v3.0.8, TiDB supports modifying the version string of the server by modifying [`server-version`](/tidb-configuration-file.md#server-version) in the configuration file.
 
-```
-server_configs:
-  tidb:
-    server-version: 'YOUR_VERSION_STRING'
-```
+- Since v4.0, if you deploy TiDB using TiUP, you can also specify the proper version string by executing `tiup cluster edit-config <cluster-name>` to edit the following section:
 
-Use the `tiup cluster reload <cluster-name> -R tidb` command to make the modification above take effect to avoid the failure of security vulnerability scan.
+    ```
+    server_configs:
+      tidb:
+        server-version: 'YOUR_VERSION_STRING'
+    ```
+
+    Then, use the `tiup cluster reload <cluster-name> -R tidb` command to make the preceding modification effective to avoid the failure of security vulnerability scan.
 
 ## What authentication protocols does TiDB support? What's the process?