pingcap · ti-chi-bot · Sep 6, 2023 · Aug 30, 2023 · Aug 31, 2023 · Aug 31, 2023
diff --git a/dr-secondary-cluster.md b/dr-secondary-cluster.md
@@ -413,4 +413,4 @@ To build a bidirectional DR cluster, see [TiCDC bidirectional replication](/ticd
 
 ## Troubleshooting
 
-If you encounter any problem in the preceding steps, you can first find the solution to the problem in [TiDB FAQs](/faq/faq-overview.md). If the problem is not resolved, you can report an [issue](https://github.com/pingcap/tidb/issues/new/choose) on GitHub.
+If you encounter any problem in the preceding steps, you can first find the solution to the problem in [TiDB FAQs](/faq/faq-overview.md). If the problem is not resolved, you can [report a bug](/support.md).
diff --git a/sql-statements/sql-statement-admin-check-table-index.md b/sql-statements/sql-statement-admin-check-table-index.md
@@ -13,7 +13,7 @@ It does not support the following:
 - Checking [FOREIGN KEY constraints](/foreign-key.md).
 - Checking the PRIMARY KEY index if a [clustered primary key](/clustered-indexes.md) is used.
 
-If `ADMIN CHECK [TABLE|INDEX]` finds any issues, you can resolve them by dropping and recreating the index. If the issue is not resolved, you can report an [issue](https://github.com/pingcap/tidb/issues/new/choose) on GitHub.
+If `ADMIN CHECK [TABLE|INDEX]` finds any issues, you can resolve them by dropping and recreating the index. If the issue is not resolved, you can [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## Principles
 
@@ -69,4 +69,4 @@ This statement is a TiDB extension to MySQL syntax.
 
 ## See also
 
-* [`ADMIN REPAIR`](/sql-statements/sql-statement-admin.md#admin-repair-statement)
+* [`ADMIN REPAIR`](/sql-statements/sql-statement-admin.md#admin-repair-statement)
diff --git a/sql-statements/sql-statement-alter-database.md b/sql-statements/sql-statement-alter-database.md
@@ -36,7 +36,7 @@ Currently, TiDB only supports some character sets and collations. See [Character
 
 ## MySQL compatibility
 
-The `ALTER DATABASE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `ALTER DATABASE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-create-database.md b/sql-statements/sql-statement-create-database.md
@@ -74,7 +74,7 @@ mysql> SHOW TABLES;
 
 ## MySQL compatibility
 
-The `CREATE DATABASE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `CREATE DATABASE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-create-role.md b/sql-statements/sql-statement-create-role.md
@@ -129,7 +129,7 @@ SHOW TABLES IN test;
 
 ## MySQL compatibility
 
-The `CREATE ROLE` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `CREATE ROLE` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-create-table-like.md b/sql-statements/sql-statement-create-table-like.md
@@ -60,7 +60,7 @@ If the table to be copied is defined with the `PRE_SPLIT_REGIONS` attribute, the
 
 ## MySQL compatibility
 
-The `CREATE TABLE LIKE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `CREATE TABLE LIKE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-deallocate.md b/sql-statements/sql-statement-deallocate.md
@@ -48,7 +48,7 @@ Query OK, 0 rows affected (0.00 sec)
 
 ## MySQL compatibility
 
-The `DEALLOCATE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `DEALLOCATE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-delete.md b/sql-statements/sql-statement-delete.md
@@ -54,7 +54,7 @@ mysql> SELECT * FROM t1;
 
 ## MySQL compatibility
 
-The `DELETE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `DELETE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-do.md b/sql-statements/sql-statement-do.md
@@ -54,7 +54,7 @@ Query OK, 0 rows affected (2.50 sec)
 
 ## MySQL compatibility
 
-The `DO` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `DO` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-drop-database.md b/sql-statements/sql-statement-drop-database.md
@@ -47,7 +47,7 @@ mysql> SHOW DATABASES;
 
 ## MySQL compatibility
 
-The `DROP DATABASE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `DROP DATABASE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-drop-role.md b/sql-statements/sql-statement-drop-role.md
@@ -162,7 +162,7 @@ ERROR 3530 (HY000): `analyticsteam`@`%` is is not granted to jennifer@%
 
 ## MySQL compatibility
 
-The `DROP ROLE` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `DROP ROLE` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-drop-view.md b/sql-statements/sql-statement-drop-view.md
@@ -74,7 +74,7 @@ mysql> SELECT * FROM t1;
 
 ## MySQL compatibility
 
-The `DROP VIEW` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `DROP VIEW` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-execute.md b/sql-statements/sql-statement-execute.md
@@ -38,7 +38,7 @@ Query OK, 0 rows affected (0.00 sec)
 
 ## MySQL compatibility
 
-The `EXECUTE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `EXECUTE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-flush-privileges.md b/sql-statements/sql-statement-flush-privileges.md
@@ -35,7 +35,7 @@ Query OK, 0 rows affected (0.01 sec)
 
 ## MySQL compatibility
 
-The `FLUSH PRIVILEGES` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `FLUSH PRIVILEGES` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-grant-role.md b/sql-statements/sql-statement-grant-role.md
@@ -129,7 +129,7 @@ SHOW TABLES IN test;
 
 ## MySQL compatibility
 
-The `GRANT <role>` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `GRANT <role>` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-insert.md b/sql-statements/sql-statement-insert.md
@@ -98,7 +98,7 @@ mysql> SELECT * FROM t2;
 
 ## MySQL compatibility
 
-The `INSERT` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `INSERT` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-load-data.md b/sql-statements/sql-statement-load-data.md
@@ -147,7 +147,7 @@ In the above example, `x'2c'` is the hexadecimal representation of the `,` chara
 
 ## MySQL compatibility
 
-The syntax of the `LOAD DATA` statement is compatible with that of MySQL, except for character set options which are parsed but ignored. If you find any syntax compatibility difference, you can [report it via an issue](https://github.com/pingcap/tidb/issues/new/choose) on GitHub.
+The syntax of the `LOAD DATA` statement is compatible with that of MySQL, except for character set options which are parsed but ignored. If you find any syntax compatibility difference, you can [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 <CustomContent platform="tidb">
 
@@ -190,4 +190,4 @@ The syntax of the `LOAD DATA` statement is compatible with that of MySQL, except
 * [TiDB Optimistic Transaction Model](/optimistic-transaction.md)
 * [TiDB Pessimistic Transaction Mode](/pessimistic-transaction.md)
 
-</CustomContent>
+</CustomContent>
diff --git a/sql-statements/sql-statement-prepare.md b/sql-statements/sql-statement-prepare.md
@@ -42,7 +42,7 @@ Query OK, 0 rows affected (0.00 sec)
 
 ## MySQL compatibility
 
-The `PREPARE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `PREPARE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-rename-index.md b/sql-statements/sql-statement-rename-index.md
@@ -52,7 +52,7 @@ Create Table: CREATE TABLE `t1` (
 
 ## MySQL compatibility
 
-The `RENAME INDEX` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `RENAME INDEX` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-rename-table.md b/sql-statements/sql-statement-rename-table.md
@@ -46,7 +46,7 @@ mysql> SHOW TABLES;
 
 ## MySQL compatibility
 
-The `RENAME TABLE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `RENAME TABLE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-rename-user.md b/sql-statements/sql-statement-rename-user.md
@@ -72,7 +72,7 @@ ERROR 1141 (42000): There is no such grant defined for user 'newuser' on host '%
 
 ## MySQL compatibility
 
-`RENAME USER` is expected to be fully compatible with MySQL. If you find any compatibility difference, submit a GitHub [issue](https://github.com/pingcap/tidb/issues/new/choose).
+`RENAME USER` is expected to be fully compatible with MySQL. If you find any compatibility difference, you can [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-replace.md b/sql-statements/sql-statement-replace.md
@@ -69,7 +69,7 @@ mysql> SELECT * FROM t1;
 
 ## MySQL compatibility
 
-The `REPLACE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `REPLACE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-revoke-role.md b/sql-statements/sql-statement-revoke-role.md
@@ -160,7 +160,7 @@ SHOW GRANTS;
 
 ## MySQL compatibility
 
-The `REVOKE <role>` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `REVOKE <role>` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-set-default-role.md b/sql-statements/sql-statement-set-default-role.md
@@ -141,7 +141,7 @@ ERROR 3530 (HY000): `analyticsteam`@`%` is is not granted to jennifer@%
 
 ## MySQL compatibility
 
-The `SET DEFAULT ROLE` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SET DEFAULT ROLE` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-set-names.md b/sql-statements/sql-statement-set-names.md
@@ -95,7 +95,7 @@ mysql> SHOW VARIABLES LIKE 'character_set%';
 
 ## MySQL compatibility
 
-The `SET [NAMES|CHARACTER SET]` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SET [NAMES|CHARACTER SET]` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-set-password.md b/sql-statements/sql-statement-set-password.md
@@ -56,7 +56,7 @@ mysql> SHOW CREATE USER 'newuser';
 
 ## MySQL compatibility
 
-The `SET PASSWORD` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SET PASSWORD` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-set-role.md b/sql-statements/sql-statement-set-role.md
@@ -109,7 +109,7 @@ SELECT CURRENT_ROLE();
 
 ## MySQL compatibility
 
-The `SET ROLE` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SET ROLE` statement in TiDB is fully compatible with the roles feature in MySQL 8.0. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-character-set.md b/sql-statements/sql-statement-show-character-set.md
@@ -36,7 +36,7 @@ mysql> SHOW CHARACTER SET;
 
 ## MySQL compatibility
 
-The usage of `SHOW CHARACTER SET` statement in TiDB is fully compatible with MySQL. However, charsets in TiDB might have different default collations compared with MySQL. For details, refer to [Compatibility with MySQL](/mysql-compatibility.md). If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The usage of `SHOW CHARACTER SET` statement in TiDB is fully compatible with MySQL. However, charsets in TiDB might have different default collations compared with MySQL. For details, refer to [Compatibility with MySQL](/mysql-compatibility.md). If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-collation.md b/sql-statements/sql-statement-show-collation.md
@@ -60,7 +60,7 @@ mysql> SHOW COLLATION;
 
 ## MySQL compatibility
 
-The usage of the `SHOW COLLATION` statement in TiDB is fully compatible with MySQL. However, charsets in TiDB might have different default collations compared with MySQL. For details, refer to [Compatibility with MySQL](/mysql-compatibility.md). If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The usage of the `SHOW COLLATION` statement in TiDB is fully compatible with MySQL. However, charsets in TiDB might have different default collations compared with MySQL. For details, refer to [Compatibility with MySQL](/mysql-compatibility.md). If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-columns-from.md b/sql-statements/sql-statement-show-columns-from.md
@@ -158,7 +158,7 @@ mysql> show full columns from mysql.user;
 
 ## MySQL compatibility
 
-The `SHOW [FULL] COLUMNS FROM` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SHOW [FULL] COLUMNS FROM` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-create-database.md b/sql-statements/sql-statement-show-create-database.md
@@ -54,7 +54,7 @@ SHOW CREATE SCHEMA IF NOT EXISTS test;
 
 ## MySQL compatibility
 
-`SHOW CREATE DATABASE` is expected to be fully compatible with MySQL. If you find any compatibility differences, submit a GitHub [issue](https://github.com/pingcap/tidb/issues/new/choose).
+`SHOW CREATE DATABASE` is expected to be fully compatible with MySQL. If you find any compatibility differences, you can [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-create-table.md b/sql-statements/sql-statement-show-create-table.md
@@ -37,7 +37,7 @@ mysql> SHOW CREATE TABLE t1;
 
 ## MySQL compatibility
 
-The `SHOW CREATE TABLE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SHOW CREATE TABLE` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-databases.md b/sql-statements/sql-statement-show-databases.md
@@ -52,7 +52,7 @@ mysql> SHOW DATABASES;
 
 ## MySQL compatibility
 
-The `SHOW DATABASES` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SHOW DATABASES` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-errors.md b/sql-statements/sql-statement-show-errors.md
@@ -48,7 +48,7 @@ Empty set (0.00 sec)
 
 ## MySQL compatibility
 
-The `SHOW ERRORS` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SHOW ERRORS` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-grants.md b/sql-statements/sql-statement-show-grants.md
@@ -61,7 +61,7 @@ mysql> SHOW GRANTS FOR u1;
 
 ## MySQL compatibility
 
-The `SHOW GRANTS` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SHOW GRANTS` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-indexes.md b/sql-statements/sql-statement-show-indexes.md
@@ -72,7 +72,7 @@ mysql> SHOW KEYS FROM t1;
 
 ## MySQL compatibility
 
-The `SHOW INDEXES [FROM|IN]` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SHOW INDEXES [FROM|IN]` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
 

diff --git a/sql-statements/sql-statement-show-plugins.md b/sql-statements/sql-statement-show-plugins.md
@@ -52,4 +52,4 @@ SHOW PLUGINS LIKE 'a%';
 
 ## MySQL compatibility
 
-The `SHOW PLUGINS` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SHOW PLUGINS` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
diff --git a/sql-statements/sql-statement-show-privileges.md b/sql-statements/sql-statement-show-privileges.md
@@ -76,7 +76,7 @@ mysql> show privileges;
 
 ## MySQL compatibility
 
-The `SHOW PRIVILEGES` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
+The `SHOW PRIVILEGES` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).
 
 ## See also
Original file line number	Diff line number	Diff line change
Expand Up		@@ -413,4 +413,4 @@ To build a bidirectional DR cluster, see [TiCDC bidirectional replication](/ticd

		## Troubleshooting

		If you encounter any problem in the preceding steps, you can first find the solution to the problem in [TiDB FAQs](/faq/faq-overview.md). If the problem is not resolved, you can report an [issue](https://github.com/pingcap/tidb/issues/new/choose) on GitHub.
		If you encounter any problem in the preceding steps, you can first find the solution to the problem in [TiDB FAQs](/faq/faq-overview.md). If the problem is not resolved, you can [report a bug](/support.md).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -52,4 +52,4 @@ SHOW PLUGINS LIKE 'a%';

		## MySQL compatibility

		The `SHOW PLUGINS` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, report them via [an issue on GitHub](https://github.com/pingcap/tidb/issues/new/choose).
		The `SHOW PLUGINS` statement in TiDB is fully compatible with MySQL. If you find any compatibility differences, [report a bug](https://docs.pingcap.com/tidb/stable/support).