From 631b7a477988bce1a485a1221df1f8cd6d89a0ef Mon Sep 17 00:00:00 2001
From: TomShawn <41534398+TomShawn@users.noreply.github.com>
Date: Thu, 23 Sep 2021 11:59:11 +0800
Subject: [PATCH] Fix wrong wording in mysql-compatibility.md

---
 mysql-compatibility.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mysql-compatibility.md b/mysql-compatibility.md
index df926f834c17c..093a96a7943fe 100644
--- a/mysql-compatibility.md
+++ b/mysql-compatibility.md
@@ -5,7 +5,7 @@ summary: Learn about the compatibility of TiDB with MySQL, and the unsupported a
 
 # MySQL Compatibility
 
-TiDB is fully compatible with the MySQL 5.7 protocol and the common features and syntax of MySQL 5.7. The ecosystem tools for MySQL 5.7 (PHPMyAdmin, Navicat, MySQL Workbench, mysqldump, and Mydumper/myloader) and the MySQL client can be used for TiDB.
+TiDB is highly compatible with the MySQL 5.7 protocol and the common features and syntax of MySQL 5.7. The ecosystem tools for MySQL 5.7 (PHPMyAdmin, Navicat, MySQL Workbench, mysqldump, and Mydumper/myloader) and the MySQL client can be used for TiDB.
 
 However, some features of MySQL are not supported. This could be because there is now a better way to solve the problem (such as XML functions superseded by JSON), or a lack of current demand versus effort required (such as stored procedures and functions). Some features might also be difficult to implement as a distributed system.