diff --git a/TOC.md b/TOC.md
index 2c0c701c491bb..ac9947fe7296a 100644
--- a/TOC.md
+++ b/TOC.md
@@ -383,8 +383,8 @@
     + [Character Set and Collation](/character-set-and-collation.md)
     + System Tables
       + [`mysql`](/mysql-schema.md)
-      + `INFORMATION_SCHEMA`
-        + [Overview](/information-schema.md)
+      + INFORMATION_SCHEMA
+        + [Overview](/information-schema/information-schema.md)
         + [`ANALYZE_STATUS`](/information-schema/information-schema-analyze-status.md)
         + [`CHARACTER_SETS`](/information-schema/information-schema-character-sets.md)
         + [`CLUSTER_CONFIG`](/information-schema/information-schema-cluster-config.md)
diff --git a/faq/deploy-and-maintain-faq.md b/faq/deploy-and-maintain-faq.md
index 1d0ce65e0643e..e645a9af1b147 100644
--- a/faq/deploy-and-maintain-faq.md
+++ b/faq/deploy-and-maintain-faq.md
@@ -353,7 +353,7 @@ No. Currently, TiDB only supports the distributed storage engine and the Golevel
 
 #### Can the `Information_schema` support more real information?
 
-As part of MySQL compatibility, TiDB supports a number of `INFORMATION_SCHEMA` tables. Many of these tables also have a corresponding SHOW command. For more information, see [Information Schema](/information-schema.md).
+As part of MySQL compatibility, TiDB supports a number of `INFORMATION_SCHEMA` tables. Many of these tables also have a corresponding SHOW command. For more information, see [Information Schema](/information-schema/information-schema.md).
 
 #### What's the explanation of the TiDB Backoff type scenario?
 
diff --git a/information-schema.md b/information-schema/information-schema.md
similarity index 100%
rename from information-schema.md
rename to information-schema/information-schema.md