tidb-cloud: fix code fences, duplicated text, and wrong values in TiDB Cloud docs

releases/release-7.6.0.md

@@ -176,7 +176,7 @@ Quick access: [Quick start](https://docs-archive.pingcap.com/tidb/v7.6/quick-sta
 
     ```sql
     FLASHBACK CLUSTER TO TSO 445494839813079041;
-    ````
+    ```
 
     For more information, see [documentation](/sql-statements/sql-statement-flashback-cluster.md).
 

tidb-cloud/dedicated-external-storage.md

@@ -51,7 +51,7 @@ Configure the bucket access for TiDB Cloud and get the Role ARN as follows:
     4. On the **Create policy** page, click the **JSON** tab.
     5. Copy the following access policy template and paste it into the policy text field.
 
-        ````json
+        ```json
         {
             "Version": "2012-10-17",
             "Statement": [

tidb-cloud/migrate-from-op-tidb.md

@@ -325,7 +325,7 @@ To replicate incremental data, do the following:
     SET GLOBAL tidb_gc_enable = TRUE;
     ```
 
-    The following is an example output, in which `1` indicates that GC is disabled.
+    The following is an example output, in which `1` indicates that GC is enabled.
 
     ```sql
     SELECT @@global.tidb_gc_enable;

tidb-cloud/serverless-private-link-connection-to-self-hosted-kafka-in-alicloud.md

@@ -501,7 +501,7 @@ The following configuration applies to a Kafka KRaft cluster. The ZK mode config
 
     # Add EXTERNAL advertised listeners based on the "Kafka Advertised Listener Pattern" in "Prerequisites" section
     # 1. The pattern is "<broker_id>.unique_name.alicloud.plc.tidbcloud.com:<port>"
-    # 2. So the EXTERNAL can be "b2.unique_name.alicloud.plc.tidbcloud.com:9095". Replace <broker_id> with "b" prefix plus "node.id" properties, and replace <port> with a unique port(9095) in EXTERNAL advertised listener ports range.
+    # 2. So the EXTERNAL can be "b3.unique_name.alicloud.plc.tidbcloud.com:9095". Replace <broker_id> with "b" prefix plus "node.id" properties, and replace <port> with a unique port(9095) in EXTERNAL advertised listener ports range.
     advertised.listeners=...,EXTERNAL://b3.unique_name.alicloud.plc.tidbcloud.com:9095
 
     # Configure EXTERNAL map

tidb-cloud/serverless-private-link-connection-to-self-hosted-kafka-in-aws.md

@@ -569,7 +569,7 @@ The following configuration applies to a Kafka KRaft cluster. The ZK mode config
 
     # Add EXTERNAL advertised listeners based on the "Kafka Advertised Listener Pattern" in "Prerequisites" section
     # 1. The pattern for AZ(ID: usw2-az3) is "<broker_id>.usw2-az3.unique_name.aws.plc.tidbcloud.com:<port>"
-    # 2. So the EXTERNAL can be "b2.usw2-az3.unique_name.aws.plc.tidbcloud.com:9095". Replace <broker_id> with "b" prefix plus "node.id" properties, and replace <port> with a unique port(9095) in EXTERNAL advertised listener ports range.
+    # 2. So the EXTERNAL can be "b3.usw2-az3.unique_name.aws.plc.tidbcloud.com:9095". Replace <broker_id> with "b" prefix plus "node.id" properties, and replace <port> with a unique port(9095) in EXTERNAL advertised listener ports range.
     advertised.listeners=...,EXTERNAL://b3.usw2-az3.unique_name.aws.plc.tidbcloud.com:9095
 
     # Configure EXTERNAL map

tidb-cloud/set-up-private-endpoint-connections.md

@@ -207,6 +207,6 @@ The possible statuses of a private endpoint service are explained as follows:
 
 ### I cannot connect to a TiDB cluster via a private endpoint after enabling private DNS. Why?
 
-You might need to properly set the security group for your VPC endpoint in the AWS Management Console. Go to **VPC** > **Endpoints**. To do so, go to **VPC** > **Endpoints**, right-click your VPC endpoint, and select **Manage security groups**. Ensure that the selected security group allows inbound access from your EC2 instances on port `4000` or a customer-defined port.
+You might need to properly set the security group for your VPC endpoint in the AWS Management Console. To do so, go to **VPC** > **Endpoints**, right-click your VPC endpoint, and select **Manage security groups**. Ensure that the selected security group allows inbound access from your EC2 instances on port `4000` or a customer-defined port.
 
 ![Manage security groups](/media/tidb-cloud/private-endpoint/manage-security-groups.png)

tidb-cloud/setup-aws-self-hosted-kafka-private-link-service.md

@@ -615,7 +615,7 @@ The following configuration applies to a Kafka KRaft cluster. The ZK mode config
 
     # Add EXTERNAL advertised listeners based on the "Kafka Advertised Listener Pattern" in "Prerequisites" section
     # 1. The pattern for AZ(ID: usw2-az3) is "<broker_id>.usw2-az3.abc.us-west-2.aws.3199015.tidbcloud.com:<port>"
-    # 2. So the EXTERNAL can be "b2.usw2-az3.abc.us-west-2.aws.3199015.tidbcloud.com:9095". Replace <broker_id> with "b" prefix plus "node.id" properties, and replace <port> with a unique port(9095) in EXTERNAL advertised listener ports range.
+    # 2. So the EXTERNAL can be "b3.usw2-az3.abc.us-west-2.aws.3199015.tidbcloud.com:9095". Replace <broker_id> with "b" prefix plus "node.id" properties, and replace <port> with a unique port(9095) in EXTERNAL advertised listener ports range.
     advertised.listeners=...,EXTERNAL://b3.usw2-az3.abc.us-west-2.aws.3199015.tidbcloud.com:9095
 
     # Configure EXTERNAL map

tidb-cloud/sql-concepts.md

@@ -55,7 +55,7 @@ For more information, see [AUTO_INCREMENT](/auto-increment.md).
 
 ### AUTO_RANDOM
 
-`AUTO_RANDOM` is a column attribute that is used to automatically assign values to a `BIGINT` column. Values assigned automatically are random and unique. Since the value of `AUTO_RANDOM` is random and unique, `AUTO_RANDOM` is often used in place of [`AUTO_INCREMENT`](/auto-increment.md) to avoid write hotspots in a single storage node caused by TiDB assigning consecutive IDs.
+`AUTO_RANDOM` is a column attribute that is used to automatically assign values to a `BIGINT` column. Values assigned automatically are random and unique.
 
 Since the value of `AUTO_RANDOM` is random and unique, `AUTO_RANDOM` is often used in place of [`AUTO_INCREMENT`](/auto-increment.md) to avoid write hotspots in a single storage node caused by TiDB assigning consecutive IDs. If the current `AUTO_INCREMENT` column is a primary key and the type is `BIGINT`, you can execute the `ALTER TABLE t MODIFY COLUMN id BIGINT AUTO_RANDOM(5);` statement to switch from `AUTO_INCREMENT` to `AUTO_RANDOM`.
 

tidb-cloud/terraform-get-tidbcloud-provider.md

@@ -119,6 +119,7 @@ By setting `sync` to `true`, you can create, update, or delete resources synchro
 provider "tidbcloud" {
   public_key = "your_public_key"
   private_key = "your_private_key"
+  sync = true
 }
 ```
 

tidb-cloud/tidb-cloud-password-authentication.md

@@ -58,7 +58,7 @@ The default password policy is as follows:
 
 > **Note:**
 >
-> This section is only applicable to TiDB Cloud registration with email and password. If you sign up for TiDB Cloud with Google SSO or GitHub SSO, your password is managed by Google or GitHub and you cannot change it using the TiDB Cloud console.
+> This section is only applicable to TiDB Cloud registration with email and password. If you sign up for TiDB Cloud with Google, GitHub, or Microsoft SSO, your password is managed by Google, GitHub, or Microsoft and you cannot change it using the TiDB Cloud console.
 
 If you forget your password, you can reset it by email as follows:
 

tidb-cloud/use-chat2query-api.md

@@ -114,7 +114,7 @@ TiDB Cloud Data Service provides the following Chat2Query v3 endpoints and v2 en
 | POST   | `/v3/knowledgeBases/{knowledge_base_id}/data` | This endpoint adds data to a specific knowledge base. |
 | GET    | `/v3/knowledgeBases/{knowledge_base_id}/data` | This endpoint retrieves data from a specific knowledge base. |
 | PUT    | `/v3/knowledgeBases/{knowledge_base_id}/data/{knowledge_data_id}` | This endpoint updates specific data in a knowledge base. |
-| DEL    | `/v3/knowledgeBases/{knowledge_base_id}/data/{knowledge_data_id}` | This endpoint deletes specific data from a knowledge base. |
+| DELETE | `/v3/knowledgeBases/{knowledge_base_id}/data/{knowledge_data_id}` | This endpoint deletes specific data from a knowledge base. |
 | POST   | `/v3/sessions` | This endpoint creates a new session. For more information about the usage of session-related endpoints, see [Start multi-round Chat2Query](/tidb-cloud/use-chat2query-sessions.md). |
 | GET    | `/v3/sessions` | This endpoint retrieves a list of all sessions. |
 | GET    | `/v3/sessions/{session_id}` | This endpoint retrieves the details of a specific session. |