*: update info on support resources

TOC.md

@@ -197,6 +197,7 @@
     - [Identify Expensive Queries Using Top SQL](/dashboard/top-sql.md)
     - [Identify Expensive Queries Using Logs](/identify-expensive-queries.md)
     - [Save and Restore the On-Site Information of a Cluster](/sql-plan-replayer.md)
+  - [Support Resources](/support.md)
 - Performance Tuning
   - Tuning Guide
     - [Performance Tuning Overview](/performance-tuning-overview.md)

alert-rules.md

@@ -464,7 +464,7 @@ This section gives the alert rules for the TiKV component.
 
     1. Perform `SELECT VARIABLE_VALUE FROM mysql.tidb WHERE VARIABLE_NAME = "tikv_gc_leader_desc"` to locate the `tidb-server` corresponding to the GC leader;
     2. View the log of the `tidb-server`, and grep gc_worker tidb.log;
-    3. If you find that the GC worker has been resolving locks (the last log is "start resolve locks") or deleting ranges (the last log is "start delete {number} ranges") during this time, it means the GC process is running normally. Otherwise, contact [support@pingcap.com](mailto:support@pingcap.com) to resolve this issue.
+    3. If you find that the GC worker has been resolving locks (the last log is "start resolve locks") or deleting ranges (the last log is "start delete {number} ranges") during this time, it means the GC process is running normally. Otherwise, [get support](/support.md) from PingCAP or the community.
 
 ### Critical-level alerts
 

error-codes.md

@@ -16,7 +16,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the
 >
 > Some error codes stand for internal errors. Normally, TiDB handles the error rather than return it to the user, so some error codes are not listed here.
 >
-> If you encounter an error code that is not listed here, [contact PingCAP](mailto:info@pingcap.com) for support.
+> If you encounter an error code that is not listed here, [get support](/support.md) from PingCAP or the community.
 
 * Error Number: 8001
 
@@ -34,7 +34,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the
 
     If the data in a row is not consistent with the index when executing the [`ADMIN CHECK TABLE`](/sql-statements/sql-statement-admin-check-table-index.md) command, TiDB returns this error. This error is commonly seen when you check the data corruption in the table.
 
-    You can [contact PingCAP](mailto:info@pingcap.com) for support.
+    You can [get support](/support.md) from PingCAP or the community.
 
 * Error Number: 8004
 
@@ -84,7 +84,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the
 
     Invalid transactions. If TiDB finds that no transaction ID (Start Timestamp) is obtained for the transaction that is being executed, which means this transaction is invalid, this error is returned.
 
-    Usually this error does not occur. If you encounter this error, [contact PingCAP](mailto:info@pingcap.com) for support.
+    Usually this error does not occur. If you encounter this error, [get support](/support.md) from PingCAP or the community.
 
 * Error Number: 8025
 
@@ -166,7 +166,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the
 
     Unknown data type is encountered when TiDB parses the Exec argument list sent by the client.
 
-    If you encounter this error, check the client. If the client is normal, [contact PingCAP](mailto:info@pingcap.com) for support.
+    If you encounter this error, check the client. If the client is normal, [get support](/support.md) from PingCAP or the community.
 
 * Error Number: 8052
 

support.md

@@ -0,0 +1,22 @@
+---
+title: Support Resources
+summary: Find support resources if you encounter a problem using TiDB.
+---
+
+# Support Resources
+
+If you encounter a problem when you use TiDB, you can reach out for support from PingCAP or the TiDB community via the following methods:
+
++ Get support from PingCAP (requires subscription to TiDB Enterprise Edition):
+
+    - [Submit a request](https://support.pingcap.com/hc/en-us)
+
++ Seek help from the TiDB community:
+
+    - The [TiDB Forum](https://ask.pingcap.com/)
+    - Slack channels: [#everyone](https://slack.tidb.io/invite?team=tidb-community&channel=everyone&ref=docs) (English), [#tidb-japan](https://slack.tidb.io/invite?team=tidb-community&channel=tidb-japan&ref=docs) (Japanese)
+    - [Stack Overflow](https://stackoverflow.com/questions/tagged/tidb) (questions tagged with #tidb)
+
++ Learn TiDB's implementation and design
+
+    - [TiDB Internals forum](https://internals.tidb.io/)

troubleshoot-data-inconsistency-errors.md

@@ -7,7 +7,17 @@ summary: Learn how to deal with errors reported by the consistency check between
 
 TiDB checks consistency between data and indexes when it executes transactions or the [`ADMIN CHECK [TABLE|INDEX]`](/sql-statements/sql-statement-admin-check-table-index.md) statement. If the check finds that a record key-value and the corresponding index key-value are inconsistent, that is, a key-value pair storing row data and the corresponding key-value pair storing its index are inconsistent (for example, more indexes or missing indexes), TiDB reports a data inconsistency error and prints the related errors in error logs.
 
-This document describes the meanings of data inconsistency errors and provides some methods to bypass the consistency check. When a data consistency error occurs, contact PingCAP technical support for troubleshooting.
+<CustomContent platform="tidb">
+
+This document describes the meanings of data inconsistency errors and provides some methods to bypass the consistency check. If a data consistency error occurs, you can [get support](/support.md) from PingCAP or the community.
+
+</CustomContent>
+
+<CustomContent platform="tidb-cloud">
+
+This document describes the meanings of data inconsistency errors and provides some methods to bypass the consistency check. If a data consistency error occurs, you can [get support](/tidb-cloud/tidb-cloud-support.md) from PingCAP.
+
+</CustomContent>
 
 ## Error explanation