diff --git a/old_version_shardingsphere b/old_version_shardingsphere
index 55114fc..f2e4f46 100644
--- a/old_version_shardingsphere
+++ b/old_version_shardingsphere
@@ -1,779 +1,585 @@
-commit 02024a8bda7d0c295c9bae4f5d2c47bc8aaa4434
-Author: Mike0601 <40025573+Mike0601@users.noreply.github.com>
-Date:   Wed Aug 10 18:29:19 2022 +0800
+commit aa7e385877d7c538da16cce3c9117a3e04372df8
+Author: Jieker <jieker_mail@163.com>
+Date:   Thu Aug 11 15:52:23 2022 +0800
 
-    modify overview part according to today's discussion (#20054)
+    Add `CREATE DEFAULT SINGLE TABLE RULE` docs. (#20050)
     
-    * modify according to today's discussion
+    * Add `CREATE DEFAULT SINGLE TABLE RULE` docs.
     
-    * add enhance part content
+    * Problems fixed.
     
-    * add application scenarios of traffic governance
-    
-    * fix a link bug
+    * change punctuation.
 
-diff --git a/docs/document/content/features/management/_index.cn.md b/docs/document/content/features/management/_index.cn.md
-index 513ba18a5a8..ac7f744506f 100644
---- a/docs/document/content/features/management/_index.cn.md
-+++ b/docs/document/content/features/management/_index.cn.md
-@@ -21,3 +21,13 @@ chapter = true
- ## 目标
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/add-resource.cn.md b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/add-resource.cn.md
+index 22bca068b5a..0ad58e29bc1 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/add-resource.cn.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/add-resource.cn.md
+@@ -54,9 +54,9 @@ value ::=
  
- 实现从数据库到计算节点打通的一体化管理能力，在故障中为组件提供细粒度的控制能力，并尽可能的提供自愈的可能，是 Apache ShardingSphere 管控模块的主要设计目标。
-+
-+## 应用场景
-+
-+### 计算节点过载保护
-+
-+当 ShardingSphere 集群内某个计算节点超过负载后，通过熔断功能，阻断应用到该计算节点的流量，保证整个集群继续提供稳定服务。
-+
-+### 存储节点限流
-+
-+在读写分离的场景下，当 ShardingSphere 集群内某个负责读流量的存储节点承接超负荷的请求时，通过限流功能，阻断集群内计算节点到该存储节点的流量，以保证存储节点集群正常响应。
-diff --git a/docs/document/content/features/management/_index.en.md b/docs/document/content/features/management/_index.en.md
-index 4ed136f33e3..7f6b1a0e9d9 100644
---- a/docs/document/content/features/management/_index.en.md
-+++ b/docs/document/content/features/management/_index.en.md
-@@ -21,4 +21,14 @@ In the overload traffic scenario, circuit breaker and request limiting for a nod
+ - 添加资源前请确认已经在 Proxy 中创建逻辑数据库，并执行 `use` 命令成功选择一个逻辑数据库；
+ - 确认添加的资源是可以正常连接的， 否则将不能添加成功；
+-- `dataSourceName` 区分大小写；
+-- `dataSourceName` 在当前逻辑库中需要唯一；
+-- `dataSourceName` 命名只允许使用字母、数字以及 `_` ，且必须以字母开头；
++- `resourceName` 区分大小写；
++- `resourceName` 在当前逻辑库中需要唯一；
++- `resourceName` 命名只允许使用字母、数字以及 `_` ，且必须以字母开头；
+ - `poolProperty` 用于自定义连接池参数，`key` 必须和连接池参数名一致，`value` 支持 int 和 String 类型；
+ - 当 `password` 包含特殊字符时，建议使用 string 形式；例如 `password@123`的 string 形式为 `"password@123"`。
  
- ## Goal
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/add-resource.en.md b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/add-resource.en.md
+index 7f3e43c52f5..019a3e4a9d9 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/add-resource.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/add-resource.en.md
+@@ -53,15 +53,15 @@ value ::=
+ ### Supplement
  
--**The goal of Apache ShardingSphere management module is to realize the integrated management ability from database to computing node, and provide control ability for components in case of failure.**
-+The goal of Apache ShardingSphere management module is to realize the integrated management ability from database to computing node, and provide control ability for components in case of failure.
+ - Before adding resources, please confirm that a database has been created in Proxy, and execute the `use` command to
+-  successfully select a database
+-- Confirm that the added resource can be connected normally, otherwise it will not be added successfully
+-- `dataSourceName` is case-sensitive
+-- `dataSourceName` needs to be unique within the current database
+-- `dataSourceName` name only allows letters, numbers and `_`, and must start with a letter
++  successfully select a database;
++- Confirm that the added resource can be connected normally, otherwise it will not be added successfully;
++- `resourceName` is case-sensitive;
++- `resourceName` needs to be unique within the current database;
++- `resourceName` name only allows letters, numbers and `_`, and must start with a letter;
+ - `poolProperty` is used to customize connection pool parameters, `key` must be the same as the connection pool
+-  parameter name, `value` supports int and String types
+-- When `password` contains special characters, it is recommended to use the string form; for example, the string form
+-  of `password@123` is `"password@123"`
++  parameter name, `value` supports int and String types;
++- When `password` contains special characters, it is recommended to use the string form; For example, the string form
++  of `password@123` is `"password@123"`.
+ 
+ ### Example
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/alter-resource.cn.md b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/alter-resource.cn.md
+index e3d9cd94eba..937d8f4d9d9 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/alter-resource.cn.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/alter-resource.cn.md
+@@ -56,9 +56,9 @@ value ::=
+ - `ALTER RESOURCE`不允许改变该资源关联的真实数据源；
+ - `ALTER RESOURCE`会发生连接池的切换，这个操作可能对进行中的业务造成影响，请谨慎使用；
+ - 确认添加的资源是可以正常连接的， 否则将不能添加成功；
+-- `dataSourceName` 区分大小写；
+-- `dataSourceName` 在当前逻辑库中需要唯一；
+-- `dataSourceName` 命名只允许使用字母、数字以及 `_` ，且必须以字母开头；
++- `resourceName` 区分大小写；
++- `resourceName` 在当前逻辑库中需要唯一；
++- `resourceName` 命名只允许使用字母、数字以及 `_` ，且必须以字母开头；
+ - `poolProperty` 用于自定义连接池参数，`key` 必须和连接池参数名一致，`value` 支持 int 和 String 类型；
+ - 当 `password` 包含特殊字符时，建议使用 string 形式；例如 `password@123`的 string 形式为 `"password@123"`。
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/alter-resource.en.md b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/alter-resource.en.md
+index 42e5847c95d..03a09b2c107 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/alter-resource.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/alter-resource.en.md
+@@ -53,17 +53,17 @@ value ::=
+ ### Supplement
+ 
+ - Before altering the resources, please confirm that a database exists in Proxy, and execute the `use` command to
+-  successfully select a database
+-- `ALTER RESOURCE` is not allowed to change the real data source associated with this resource
++  successfully select a database;
++- `ALTER RESOURCE` is not allowed to change the real data source associated with this resource;
+ - `ALTER RESOURCE` will switch the connection pool. This operation may affect the ongoing business, please use it with
+-  caution
+-- `dataSourceName` is case-sensitive
+-- `dataSourceName` needs to be unique within the current database
+-- `dataSourceName` name only allows letters, numbers and `_`, and must start with a letter
++  caution;
++- `resourceName` is case-sensitive;
++- `resourceName` needs to be unique within the current database;
++- `resourceName` name only allows letters, numbers and `_`, and must start with a letter;
+ - `poolProperty` is used to customize connection pool parameters, `key` must be the same as the connection pool
+-  parameter name, `value` supports int and String types
++  parameter name, `value` supports int and String types;
+ - When `password` contains special characters, it is recommended to use the string form; for example, the string form
+-  of `password@123` is `"password@123"`
++  of `password@123` is `"password@123"`.
+ 
+ ### Example
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/drop-resource.en.md b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/drop-resource.en.md
+index 71f592193af..dcef7cda59b 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/resource-definition/drop-resource.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/resource-definition/drop-resource.en.md
+@@ -20,11 +20,11 @@ resourceName ::=
+ ### Supplement
+ 
+ - `DROP RESOURCE` will only drop resources in Proxy, the real data source corresponding to the resource will not be
+-  dropped
++  dropped;
+ - Unable to drop resources already used by rules. `Resources are still in used.` will be prompted when removing
+-  resources used by rules
++  resources used by rules;
+ - The resource need to be removed only contains `SINGLE TABLE RULE`, and when the user confirms that this restriction
+-  can be ignored, the `IGNORE SINGLE TABLES` keyword can be added to remove the resource
++  can be ignored, the `IGNORE SINGLE TABLES` keyword can be added to remove the resource.
+ 
+ ### Example
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/alter-sharding-table-rule.cn.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/alter-sharding-table-rule.cn.md
+index 1869b7b4b4e..6f7d1e15ba3 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/alter-sharding-table-rule.cn.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/alter-sharding-table-rule.cn.md
+@@ -47,20 +47,20 @@ algorithmName ::=
+ ### 补充说明
+ 
+ - `tableDefinition` 为标准分片规则定义；
+-- `autoTableDefinition`为自动分片规则定义。标准分片规则和自动分片规则可参考[数据分片](/cn/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/)。
++- `autoTableDefinition`为自动分片规则定义。标准分片规则和自动分片规则可参考[数据分片](/cn/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/)；
+ - 当使用标准分片时：
+-    - `DATANODES` 只能使用已经添加到当前逻辑库的资源，且只能使用 INLINE 表达式指定需要的资源
+-    - `DATABASE_STRATEGY`、`TABLE_STRATEGY` 表示分库和分表策略，均为可选项，未配置时使用默认策略
++    - `DATANODES` 只能使用已经添加到当前逻辑库的资源，且只能使用 INLINE 表达式指定需要的资源；
++    - `DATABASE_STRATEGY`、`TABLE_STRATEGY` 表示分库和分表策略，均为可选项，未配置时使用默认策略；
+     - `strategyDefinition` 中属性 `TYPE` 用于指定[分片算法](/cn/features/sharding/concept/sharding/#自定义分片算法)的类型，目前仅支持 `STANDARD`
+       、`COMPLEX`。使用 `COMPLEX` 时需要用 `SHARDING_COLUMNS` 指定多个分片键。
+ - 当使用自动分片时：
+-    - `RESOURCES` 只能使用已经添加到当前逻辑库的资源，可通过枚举或 INLINE 表达式指定需要的资源
+-    - 只能使用自动分片算法，可参考[自动分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/#自动分片算法)
+-- `algorithmType` 为分片算法类型，分片算法类型请参考[分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)
+-- 自动生成的算法命名规则为  `tableName` _ `strategyType` _ `algorithmType`
+-- 自动生成的主键策略命名规则为 `tableName` _ `strategyType`
++    - `RESOURCES` 只能使用已经添加到当前逻辑库的资源，可通过枚举或 INLINE 表达式指定需要的资源；
++    - 只能使用自动分片算法，可参考[自动分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/#自动分片算法)。
++- `algorithmType` 为分片算法类型，分片算法类型请参考[分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)；
++- 自动生成的算法命名规则为  `tableName` _ `strategyType` _ `algorithmType`；
++- 自动生成的主键策略命名规则为 `tableName` _ `strategyType`；
+ - `KEY_GENERATE_STRATEGY`
+-  用于指定主键生成策略，为可选项，关于主键生成策略可参考[分布式主键](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/)
++  用于指定主键生成策略，为可选项，关于主键生成策略可参考[分布式主键](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/)。
+ 
+ ### 示例
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/alter-sharding-table-rule.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/alter-sharding-table-rule.en.md
+index 8a10bcec23c..bee5e68fa72 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/alter-sharding-table-rule.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/alter-sharding-table-rule.en.md
+@@ -48,28 +48,28 @@ algorithmName ::=
+ 
+ - `tableDefinition` is defined for standard sharding table rule; `autoTableDefinition` is defined for auto sharding
+   table rule. For standard sharding rules and auto sharding rule, refer
+-  to [Data Sharding](en/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/).
+-- use standard sharding table rule
++  to [Data Sharding](en/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/);
++- use standard sharding table rule:
+     - `DATANODES` can only use resources that have been added to the current database, and can only use INLINE
+-      expressions to specify required resources
++      expressions to specify required resources;
+     - `DATABASE_STRATEGY`, `TABLE_STRATEGY` are the database sharding strategy and the table sharding strategy, which
+-      are optional, and the default strategy is used when not configured
++      are optional, and the default strategy is used when not configured;
+     - The attribute `TYPE` in `strategyDefinition` is used to specify the type
+       of [Sharding Algorithm](/en/features/sharding/concept/sharding/#user-defined-sharding-algorithm), currently only
+       supports `STANDARD`, `COMPLEX`. Using `COMPLEX` requires specifying multiple sharding columns
+       with `SHARDING_COLUMNS`.
+-- use auto sharding table rule
++- use auto sharding table rule:
+     - `RESOURCES` can only use resources that have been added to the current database, and the required resources can be
+-      specified by enumeration or INLINE expression
++      specified by enumeration or INLINE expression;
+     - Only auto sharding algorithm can be used, please refer
+-      to [Auto Sharding Algorithm](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/#auto-sharding-algorithm)
++      to [Auto Sharding Algorithm](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/#auto-sharding-algorithm).
+ - `algorithmType` is the sharding algorithm type, please refer
+-  to [Sharding Algorithm](en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding)
+-- The auto-generated algorithm naming rule is `tableName` _ `strategyType` _ `shardingAlgorithmType`
+-- The auto-generated primary key strategy naming rule is `tableName` _ `strategyType`
++  to [Sharding Algorithm](en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding);
++- The auto-generated algorithm naming rule is `tableName` _ `strategyType` _ `shardingAlgorithmType`;
++- The auto-generated primary key strategy naming rule is `tableName` _ `strategyType`;
+ - `KEY_GENERATE_STRATEGY` is used to specify the primary key generation strategy, which is optional. For the primary key
+   generation strategy, please refer
+-  to [Distributed Primary Key](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/)
++  to [Distributed Primary Key](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/).
+ 
+ ### Example
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-default-sharding-strategy.cn.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-default-sharding-strategy.cn.md
+index a67ba5b1782..2cea20077ce 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-default-sharding-strategy.cn.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-default-sharding-strategy.cn.md
+@@ -34,8 +34,8 @@ algorithmType ::=
+ 
+ ### 补充说明
+ 
+-- 当使用复合分片算法时，需要通过 `SHARDING_COLUMNS` 指定多个分片键
+-- `algorithmType` 为分片算法类型，详细的分片算法类型信息请参考[分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)
++- 当使用复合分片算法时，需要通过 `SHARDING_COLUMNS` 指定多个分片键；
++- `algorithmType` 为分片算法类型，详细的分片算法类型信息请参考[分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)。
+ 
+ ### 示例
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-default-sharding-strategy.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-default-sharding-strategy.en.md
+index 2e5a6b901e2..e7fd8333e4e 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-default-sharding-strategy.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-default-sharding-strategy.en.md
+@@ -34,9 +34,9 @@ algorithmType ::=
+ 
+ ### Supplement
+ 
+-- When using the complex sharding algorithm, multiple sharding columns need to be specified using `SHARDING_COLUMNS`
++- When using the complex sharding algorithm, multiple sharding columns need to be specified using `SHARDING_COLUMNS`;
+ - `algorithmType` is the sharding algorithm type. For detailed sharding algorithm type information, please refer
+-  to [Sharding Algorithm](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)
++  to [Sharding Algorithm](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/).
+ 
+ ### Example
+ 
+@@ -69,5 +69,5 @@ CREATE DEFAULT SHARDING TABLE STRATEGY (
+ 
+ ### Related links
+ 
+-- [Reserved word](/cn/reference/distsql/syntax/reserved-word/)
++- [Reserved word](/en/reference/distsql/syntax/reserved-word/)
+ - [CREATE SHARDING ALGORITHM](/en/reference/distsql/syntax/rdl/rule-definition/create-sharding-algorithm/)
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-algorithm.cn.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-algorithm.cn.md
+index 71c158b5bdc..40fc90ce014 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-algorithm.cn.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-algorithm.cn.md
+@@ -28,7 +28,7 @@ algorithmType ::=
+ 
+ ### 补充说明
+ 
+-- `algorithmType` 为分片算法类型，详细的分片算法类型信息请参考[分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)
++- `algorithmType` 为分片算法类型，详细的分片算法类型信息请参考[分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)。
+ 
+ ### 示例
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-algorithm.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-algorithm.en.md
+index 330d0f810d2..5b494021f7e 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-algorithm.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-algorithm.en.md
+@@ -28,7 +28,7 @@ algorithmType ::=
+ 
+ ### Supplement
+ 
+-- `algorithmType` is the sharding algorithm type. For detailed sharding algorithm type information, please refer to [Sharding Algorithm](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)
++- `algorithmType` is the sharding algorithm type. For detailed sharding algorithm type information, please refer to [Sharding Algorithm](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/).
+ 
+ ### Example
+ 
+@@ -52,4 +52,4 @@ CREATE SHARDING ALGORITHM interval_algorithm (
+ 
+ ### Related links
+ 
+-- [Reserved word](/cn/reference/distsql/syntax/reserved-word/)
++- [Reserved word](/en/reference/distsql/syntax/reserved-word/)
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-binding-table-rule.cn.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-binding-table-rule.cn.md
+index 91c4eeefec9..afe3899539d 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-binding-table-rule.cn.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-binding-table-rule.cn.md
+@@ -22,12 +22,12 @@ tableName ::=
+ 
+ ### 补充说明
+ 
+-- 只有分片表才能创建绑定关系
+-- 一个分片表只能具有一个绑定关系
+-- 添加绑定关系的分片表需要使用相同的资源，并且分片节点个数相同。例如 `ds_${0..1}.t_order_${0..1}` 与 `ds_${0..1}.t_order_item_${0..1}`
+-- 添加绑定关系的分片表需要对分片键使用相同的分片算法。例如 `t_order_${order_id % 2}` 与 `t_order_item_${order_item_id % 2}`
+-- 只能存在一个绑定规则，但可包含多个绑定关系，因此无法重复执行 `CREATE SHARDING BINDING TABLE RULE`。 
+-  当绑定规则已经存在但还需要添加绑定关系时，需要使用 `ALTER SHARDING BINDING TABLE RULE` 来修改绑定规则
++- 只有分片表才能创建绑定关系；
++- 一个分片表只能具有一个绑定关系；
++- 添加绑定关系的分片表需要使用相同的资源，并且分片节点个数相同。例如 `ds_${0..1}.t_order_${0..1}` 与 `ds_${0..1}.t_order_item_${0..1}`；
++- 添加绑定关系的分片表需要对分片键使用相同的分片算法。例如 `t_order_${order_id % 2}` 与 `t_order_item_${order_item_id % 2}`；
++- 只能存在一个绑定规则，但可包含多个绑定关系，因此无法重复执行 `CREATE SHARDING BINDING TABLE RULE`。
++  当绑定规则已经存在但还需要添加绑定关系时，需要使用 `ALTER SHARDING BINDING TABLE RULE` 来修改绑定规则。
+ 
+ ### 示例
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-binding-table-rule.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-binding-table-rule.en.md
+index 2571631a2da..bc28e24aae3 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-binding-table-rule.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-binding-table-rule.en.md
+@@ -23,16 +23,16 @@ tableName ::=
+ 
+ ### Supplement
+ 
+-- Creating binding relationships rules can only use sharding tables
+-- A sharding table can only have one binding relationships
++- Creating binding relationships rules can only use sharding tables;
++- A sharding table can only have one binding relationships;
+ - The sharding table for creating binding relationships needs to use the same resources and the same actual tables. For
+-  example `ds_${0..1}.t_order_${0..1}` 与 `ds_${0..1}.t_order_item_${0..1}`
++  example `ds_${0..1}.t_order_${0..1}` 与 `ds_${0..1}.t_order_item_${0..1}`;
+ - The sharding table for creating binding relationships needs to use the same sharding algorithm for the sharding
+-  column. For example `t_order_{order_id % 2}` and `t_order_item_{order_item_id % 2}`
++  column. For example `t_order_{order_id % 2}` and `t_order_item_{order_item_id % 2}`;
+ - Only one binding rule can exist, but can contain multiple binding relationships, so can not
+   execute `CREATE SHARDING BINDING TABLE RULE` more than one time. When a binding table rule already exists but a
+   binding relationship needs to be added, you need to use `ALTER SHARDING BINDING TABLE RULE` to modify the binding
+-  table rule
++  table.
+ 
+ ### Example
+ 
+@@ -56,5 +56,5 @@ CREATE SHARDING BINDING TABLE RULES (t_order,t_order_item),(t_product,t_product_
+ 
+ ### Related links
+ 
+-- [Reserved word](/cn/reference/distsql/syntax/reserved-word/)
++- [Reserved word](/en/reference/distsql/syntax/reserved-word/)
+ - [CREATE SHARDING TABLE RULE](/en/reference/distsql/syntax/rdl/rule-definition/create-sharding-table-rule/)
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-broadcast-table-rule.cn.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-broadcast-table-rule.cn.md
+index 1007b31d17d..bec25a6c457 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-broadcast-table-rule.cn.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-broadcast-table-rule.cn.md
+@@ -34,9 +34,9 @@ algorithmType ::=
+ 
+ ### 补充说明
+ 
+-- `tableName` 可使用已经存在的表或者将要创建的表
++- `tableName` 可使用已经存在的表或者将要创建的表；
+ - 只能存在一个广播规则，但可包含多个广播表，因此无法重复执行 `CREATE SHARDING BROADCAST TABLE RULE`。
+- 当广播规则已经存在但还需要添加广播表时，需要使用 `ALTER BROADCAST TABLE RULE` 来修改广播规则
++ 当广播规则已经存在但还需要添加广播表时，需要使用 `ALTER BROADCAST TABLE RULE` 来修改广播规则。
+ 
+ ### 示例
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-broadcast-table-rule.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-broadcast-table-rule.en.md
+index 4b640f94395..e2f51f37bc0 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-broadcast-table-rule.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-broadcast-table-rule.en.md
+@@ -20,10 +20,10 @@ tableName ::=
+ 
+ ### Supplement
+ 
+-- `tableName` can use an existing table or a table that will be created
++- `tableName` can use an existing table or a table that will be created;
+ - Only one broadcast rule can exist, but can contain multiple broadcast tables, so can not
+   execute `CREATE SHARDING BROADCAST TABLE RULE` more than one time. When the broadcast table rule already exists but
+-  the broadcast table needs to be added, you need to use `ALTER BROADCAST TABLE RULE` to modify the broadcast table rule
++  the broadcast table needs to be added, you need to use `ALTER BROADCAST TABLE RULE` to modify the broadcast table rule.
+ 
+ ### Example
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-key-generator.cn.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-key-generator.cn.md
+index aba53536bb7..c7c2a6fd1d1 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-key-generator.cn.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-key-generator.cn.md
+@@ -29,7 +29,7 @@ algorithmType ::=
+ ### 补充说明
+ 
+ - `algorithmType`
+-  为分布式主键生成算法类型，详细的分布式主键生成算法类型信息请参考[分布式序列算法类型](cn/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/)
++  为分布式主键生成算法类型，详细的分布式主键生成算法类型信息请参考[分布式序列算法类型](cn/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/)。
+ 
+ ### 示例
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-key-generator.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-key-generator.en.md
+index 44cdd3347fb..c211b5719db 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-key-generator.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-key-generator.en.md
+@@ -30,7 +30,7 @@ algorithmType ::=
+ ### Supplement
+ 
+ - `algorithmType` is the key generate algorithm type. For detailed key generate algorithm type information, please refer
+-  to [KEY GENERATE ALGORITHM](en/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/)
++  to [KEY GENERATE ALGORITHM](en/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/).
+ 
+ ### Example
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-table-rule.cn.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-table-rule.cn.md
+index 6414cca6754..7526ad70904 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-table-rule.cn.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-table-rule.cn.md
+@@ -47,20 +47,20 @@ algorithmName ::=
+ ### 补充说明
+ 
+ - `tableDefinition` 为标准分片规则定义；`autoTableDefinition`
+-  为自动分片规则定义。标准分片规则和自动分片规则可参考[数据分片](/cn/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/)。
++  为自动分片规则定义。标准分片规则和自动分片规则可参考[数据分片](/cn/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/)；
+ - 当使用标准分片时：
+-    - `DATANODES` 只能使用已经添加到当前逻辑库的资源，且只能使用 INLINE 表达式指定需要的资源
+-    - `DATABASE_STRATEGY`、`TABLE_STRATEGY` 表示分库和分表策略，均为可选项，未配置时使用默认策略
++    - `DATANODES` 只能使用已经添加到当前逻辑库的资源，且只能使用 INLINE 表达式指定需要的资源；
++    - `DATABASE_STRATEGY`、`TABLE_STRATEGY` 表示分库和分表策略，均为可选项，未配置时使用默认策略；
+     - `strategyDefinition` 中属性 `TYPE` 用于指定[分片算法](/cn/features/sharding/concept/sharding/#自定义分片算法)的类型，目前仅支持 `STANDARD`
+       、`COMPLEX`。使用 `COMPLEX` 时需要用 `SHARDING_COLUMNS` 指定多个分片键。
+ - 当使用自动分片时：
+-    - `RESOURCES` 只能使用已经添加到当前逻辑库的资源，可通过枚举或 INLINE 表达式指定需要的资源
+-    - 只能使用自动分片算法，可参考[自动分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/#自动分片算法)
+-- `algorithmType` 为分片算法类型，分片算法类型请参考[分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)
+-- 自动生成的算法命名规则为  `tableName` _ `strategyType` _ `algorithmType`
+-- 自动生成的主键策略命名规则为 `tableName` _ `strategyType`
++    - `RESOURCES` 只能使用已经添加到当前逻辑库的资源，可通过枚举或 INLINE 表达式指定需要的资源；
++    - 只能使用自动分片算法，可参考[自动分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/#自动分片算法)。
++- `algorithmType` 为分片算法类型，分片算法类型请参考[分片算法](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/)；
++- 自动生成的算法命名规则为  `tableName` _ `strategyType` _ `algorithmType`；
++- 自动生成的主键策略命名规则为 `tableName` _ `strategyType；
+ - `KEY_GENERATE_STRATEGY`
+-  用于指定主键生成策略，为可选项，关于主键生成策略可参考[分布式主键](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/)
++  用于指定主键生成策略，为可选项，关于主键生成策略可参考[分布式主键](/cn/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/)。
+ 
+ ### 示例
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-table-rule.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-table-rule.en.md
+index c8301c7974a..9c8a44a9797 100644
+--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-table-rule.en.md
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/sharding/create-sharding-table-rule.en.md
+@@ -48,28 +48,28 @@ algorithmName ::=
+ 
+ - `tableDefinition` is defined for standard sharding table rule; `autoTableDefinition` is defined for auto sharding
+   table rule. For standard sharding rules and auto sharding rule, refer
+-  to [Data Sharding](en/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/).
+-- use standard sharding table rule
++  to [Data Sharding](en/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/);
++- use standard sharding table rule:
+     - `DATANODES` can only use resources that have been added to the current database, and can only use INLINE
+-      expressions to specify required resources
++      expressions to specify required resources;
+     - `DATABASE_STRATEGY`, `TABLE_STRATEGY` are the database sharding strategy and the table sharding strategy, which
+-      are optional, and the default strategy is used when not configured
++      are optional, and the default strategy is used when not configured;
+     - The attribute `TYPE` in `strategyDefinition` is used to specify the type
+       of [Sharding Algorithm](/en/features/sharding/concept/sharding/#user-defined-sharding-algorithm), currently only
+       supports `STANDARD`, `COMPLEX`. Using `COMPLEX` requires specifying multiple sharding columns
+       with `SHARDING_COLUMNS`.
+-- use auto sharding table rule
++- use auto sharding table rule:
+     - `RESOURCES` can only use resources that have been added to the current database, and the required resources can be
+-      specified by enumeration or INLINE expression
++      specified by enumeration or INLINE expression;
+     - Only auto sharding algorithm can be used, please refer
+-      to [Auto Sharding Algorithm](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/#auto-sharding-algorithm)
++      to [Auto Sharding Algorithm](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding/#auto-sharding-algorithm).
+ - `algorithmType` is the sharding algorithm type, please refer
+-  to [Sharding Algorithm](en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding)
+-- The auto-generated algorithm naming rule is `tableName` _ `strategyType` _ `shardingAlgorithmType`
+-- The auto-generated primary key strategy naming rule is `tableName` _ `strategyType`
++  to [Sharding Algorithm](en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding);
++- The auto-generated algorithm naming rule is `tableName` _ `strategyType` _ `shardingAlgorithmType`;
++- The auto-generated primary key strategy naming rule is `tableName` _ `strategyType`;
+ - `KEY_GENERATE_STRATEGY` is used to specify the primary key generation strategy, which is optional. For the primary key
+   generation strategy, please refer
+-  to [Distributed Primary Key](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/)
++  to [Distributed Primary Key](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen/).
+ 
+ ### Example
+ 
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/_index.cn.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/_index.cn.md
+new file mode 100644
+index 00000000000..3a0d0f8ccf0
+--- /dev/null
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/_index.cn.md
+@@ -0,0 +1,7 @@
+++++
++title = "单表"
++weight = 1
++chapter = true
+++++
 +
-+## Application Scenarios
++本章节将对单表特性的语法进行详细说明。
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/_index.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/_index.en.md
+new file mode 100644
+index 00000000000..8f47cf48efc
+--- /dev/null
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/_index.en.md
+@@ -0,0 +1,7 @@
+++++
++title = "Single Table"
++weight = 1
++chapter = true
+++++
 +
-+### Overloaded compute node protection
++This chapter describes the syntax of single table.
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/create-default-single-table-rule.cn.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/create-default-single-table-rule.cn.md
+new file mode 100644
+index 00000000000..3bc2ed649cc
+--- /dev/null
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/create-default-single-table-rule.cn.md
+@@ -0,0 +1,41 @@
+++++
++title = "CREATE DEFAULT SINGLE TABLE RULE"
++weight = 2
+++++
 +
-+When a compute node in a ShardingSphere cluster exceeds its load, the circuit breaker function is used to block the traffic to the compute node, to ensure that the whole cluster continues to provide stable services.
++## 描述
 +
-+### Storage node traffic limit
++`CREATE DEFAULT SINGLE TABLE RULE` 语法用于创建默认的单表规则
 +
-+In the read-write splitting scenario where a storage node responsible for the read traffic in a ShardingSphere cluster receives overloaded requests, the traffic limit function is used to block traffic from compute nodes to the storage node, to ensure normal response of the storage node cluster.
-diff --git a/docs/document/content/features/readwrite-splitting/_index.en.md b/docs/document/content/features/readwrite-splitting/_index.en.md
-index f26f213be47..6a2a507c517 100644
---- a/docs/document/content/features/readwrite-splitting/_index.en.md
-+++ b/docs/document/content/features/readwrite-splitting/_index.en.md
-@@ -21,7 +21,7 @@ Data in readwrite-splitting nodes are consistent, whereas that in shards is not.
- 
- Though readwrite-splitting can enhance system throughput and availability, it also brings inconsistent data, including that among multiple primary databases and among primary databases and replica databases. What’s more, it also brings the same problem as data sharding, complicating developer and operator’s maintenance and operation. The following diagram has shown the complex topological relations between applications and database groups when sharding used together with readwrite-splitting.
- 
--![chanllenges](https://shardingsphere.apache.org/document/current/img/readwrite-splitting/chanllenges.png)
-+![challenges](https://shardingsphere.apache.org/document/current/img/readwrite-splitting/challenges.png)
- 
- ## Goal
- 
-diff --git a/docs/document/content/overview/design.cn.md b/docs/document/content/overview/design.cn.md
-index 5236ca76548..5db77be4bee 100644
---- a/docs/document/content/overview/design.cn.md
-+++ b/docs/document/content/overview/design.cn.md
-@@ -7,22 +7,32 @@ chapter = true
- 
- ShardingSphere 采用 Database Plus 设计哲学，该理念致力于构建数据库上层的标准和生态，在生态中补充数据库所缺失的能力。
- 
--Apache ShardingSphere 的可插拔架构划分为 3 层，它们是：L1 内核层、L2 功能层、L3 生态层。
--
- ![ShardingSphere Architecture](https://shardingsphere.apache.org/document/current/img/overview.cn_v2.png)
- 
--## L1 内核层
-+## 连接：打造数据库上层标准
++### 语法定义
 +
-+通过对数据库协议、SQL 方言以及数据库存储的灵活适配，快速构建多模异构数据库上层的标准，同时通过内置 DistSQL 为应用提供标准化的连接方式。
++```sql
++CreateDefaultSingleTableRule ::=
++  'CREATE' 'DEFAULT' 'SINGLE` `TABLE` `RULE' singleTableDefinition
 +
-+## 增强：数据库计算增强引擎
++singleTableDefinition ::=
++  'RESOURCE' '=' resourceName
 +
-+获取数据库的访问流量，并提供流量重定向（数据分片、读写分离、影子库）、流量变形（数据加密、数据脱敏）、流量鉴权（安全、审计、权限）、流量治理（熔断、限流）以及流量分析（服务质量分析、可观察性）等透明化增量功能。
++resourceName ::=
++  identifier
++```
 +
-+## 可插拔：构建数据库功能生态
++### 补充说明
 +
-+Apache ShardingSphere 的可插拔架构划分为 3 层，它们是：L1 内核层、L2 功能层、L3 生态层。
++- `RESOURCE` 需使用 RDL 管理的数据源资源。
 +
-+### L1 内核层
- 
- 是数据库基本能力的抽象，其所有组件均必须存在，但具体实现方式可通过可插拔的方式更换。
- 主要包括查询优化器、分布式事务引擎、分布式执行引擎、权限引擎和调度引擎等。
- 
--## L2 功能层
-+### L2 功能层
- 
- 用于提供增量能力，其所有组件均是可选的，可以包含零至多个组件。
- 组件之间完全隔离，互无感知，多组件可通过叠加的方式相互配合使用。
- 主要包括数据分片、读写分离、数据库高可用、数据加密、影子库等。
- 用户自定义功能可完全面向 Apache ShardingSphere 定义的顶层接口进行定制化扩展，而无需改动内核代码。
- 
--## L3 生态层
-+### L3 生态层
- 
--用于对接和融入现有数据库生态，包括数据库协议、SQL 解析器和存储适配器，分别对应于 Apache ShardingSphere 以数据库协议提供服务的方式、SQL 方言操作数据的方式以及对接存储节点的数据库类型。
++### 示例
++
++#### 创建默认单表规则
++
++```sql
++CREATE DEFAULT SINGLE TABLE RULE RESOURCE = ds_0;
++```
++
++### 保留字
++
++`CREATE`、`SHARDING`、`SINGLE`、`TABLE`、`RULE`、`RESOURCE`
++
++### 相关链接
++
++- [保留字](/cn/reference/distsql/syntax/reserved-word/)
 \ No newline at end of file
-+用于对接和融入现有数据库生态，包括数据库协议、SQL 解析器和存储适配器，分别对应于 Apache ShardingSphere 以数据库协议提供服务的方式、SQL 方言操作数据的方式以及对接存储节点的数据库类型。
-diff --git a/docs/document/content/overview/design.en.md b/docs/document/content/overview/design.en.md
-index 1ed1ea4b8d7..a79b28c1cee 100644
---- a/docs/document/content/overview/design.en.md
-+++ b/docs/document/content/overview/design.en.md
-@@ -7,17 +7,27 @@ chapter = true
- 
- ShardingSphere adopts the database plus design philosophy, which is committed to building the standards and ecology of the upper layer of the database and supplementing the missing capabilities of the database in the ecology.
- 
--The pluggable architecture of Apache ShardingSphere is composed of three layers - L1 Kernel Layer, L2 Feature Layer and L3 Ecosystem Layer.
--
- ![Overview](https://shardingsphere.apache.org/document/current/img/overview.en.png)
- 
--## L1 Kernel Layer
-+## Connect: Create database upper level standard
+diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/create-default-single-table-rule.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/create-default-single-table-rule.en.md
+new file mode 100644
+index 00000000000..ae26257b766
+--- /dev/null
++++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/single-table/create-default-single-table-rule.en.md
+@@ -0,0 +1,41 @@
+++++
++title = "CREATE DEFAULT SINGLE TABLE RULE"
++weight = 2
+++++
 +
-+ Through flexible adaptation of database protocols, SQL dialects, and database storage, it can quickly build standards on top of multi-modal heterogeneous databases, while providing standardized connection mode for applications through built-in DistSQL.
++## Description
 +
-+## Enhance: Database computing enhancement engine
++The `CREATE DEFAULT SINGLE TABLE RULE` syntax is used to create a default single table rule.
 +
-+Capture database access entry to provide additional features transparently, such as: redirect (sharding, readwrite-splitting and shadow), transform (data encrypt and mask), authentication (security, audit and authority), governance (circuit breaker and access limitation and analyze, QoS and observability).
++### Syntax
 +
-+## Pluggable: Building database function ecology
++```sql
++CreateDefaultSingleTableRule ::=
++  'CREATE' 'DEFAULT' 'SINGLE` `TABLE` `RULE' singleTableDefinition
 +
-+The pluggable architecture of Apache ShardingSphere is composed of three layers - L1 Kernel Layer, L2 Feature Layer and L3 Ecosystem Layer.
++singleTableDefinition ::=
++  'RESOURCE' '=' resourceName
 +
-+### L1 Kernel Layer
- 
- An abstraction of databases' basic capabilities.
- All the components are required and the specific implementation method can be replaced thanks to plugins.
- It includes a query optimizer, distributed transaction engine, distributed execution engine, permission engine and scheduling engine.
- 
--## L2 Feature Layer
-+### L2 Feature Layer
- 
- Used to provide enhancement capabilities.
- All components are optional, allowing you to choose whether to include zero or multiple components.
-@@ -25,8 +35,7 @@ Components are isolated from each other, and multiple components can be used tog
- It includes data sharding, read/write splitting, database high availability, data encryption and shadow database and so on.
- The user-defined feature can be fully customized and extended for the top-level interface defined by Apache ShardingSphere without changing kernel codes.
- 
--## L3 Ecosystem Layer
-+### L3 Ecosystem Layer
- 
- It is used to integrate and merge the current database ecosystems.
- The ecosystem layer includes database protocol, SQL parser and storage adapter, corresponding to the way in which Apache ShardingSphere provides services by database protocol, the way in which SQL dialect operates data, and the database type that interacts with storage nodes.
--
-diff --git a/docs/document/content/overview/distsql.cn.md b/docs/document/content/overview/distsql.cn.md
-deleted file mode 100644
-index 07ccaf50aa3..00000000000
---- a/docs/document/content/overview/distsql.cn.md
-+++ /dev/null
-@@ -1,77 +0,0 @@
--+++
--pre = "<b>1.4 </b>"
--title = "DistSQL"
--weight = 4
--chapter = true
--+++
--
--## 定义
--
--DistSQL（Distributed SQL）是 Apache ShardingSphere 特有的操作语言。 它与标准 SQL 的使用方式完全一致，用于提供增量功能的 SQL 级别操作能力。
--
--灵活的规则配置和资源管控能力是 Apache ShardingSphere 的特点之一。
--
--在使用 4.x 及其之前版本时，开发者虽然可以像使用原生数据库一样操作数据，但却需要通过本地文件或注册中心配置资源和规则。然而，操作习惯变更，对于运维工程师并不友好。
--
--从 5.x 版本开始，DistSQL（Distributed SQL）让用户可以像操作数据库一样操作 Apache ShardingSphere，使其从面向开发人员的框架和中间件转变为面向运维人员的数据库产品。
--
--## 相关概念
--
--DistSQL 细分为 RDL、RQL、RAL 和 RUL 四种类型。
--
--### RDL
--
--Resource & Rule Definition Language，负责资源和规则的创建、修改和删除。
--
--### RQL
--
--Resource & Rule Query Language，负责资源和规则的查询和展现。
--
--### RAL
--
--Resource & Rule Administration Language，负责强制路由、熔断、配置导入导出、数据迁移控制等管理功能。
--
--### RUL
--
--Resource & Rule Utility Language，负责 SQL 解析、SQL 格式化、执行计划预览等功能。
--
--## 对系统的影响
--
--### 之前
--
--在拥有 DistSQL 以前，用户一边使用 SQL 语句操作数据，一边使用 YAML 文件来管理 ShardingSphere 的配置，如下图：
--
--![Before](https://shardingsphere.apache.org/document/current/img/distsql/before.png)
--
--这时用户不得不面对以下几个问题：
--- 需要通过不同类型的客户端来操作数据和管理 ShardingSphere 规则；
--- 多个逻辑库需要多个 YAML 文件；
--- 修改 YAML 需要文件的编辑权限；
--- 修改 YAML 后需要重启 ShardingSphere。
--
--### 之后
--
--随着 DistSQL 的出现，对 ShardingSphere 的操作方式也得到了改变：
--
--![After](https://shardingsphere.apache.org/document/current/img/distsql/after.png)
--
--现在，用户的使用体验得到了巨大改善：
--- 使用相同的客户端来管理数据和 ShardingSphere 配置；
--- 不再额外创建 YAML 文件，通过 DistSQL 管理逻辑库；
--- 不再需要文件的编辑权限，通过 DistSQL 来管理配置；
--- 配置的变更实时生效，无需重启 ShardingSphere。
--
--## 使用限制
--
--DistSQL 只能用于 ShardingSphere-Proxy，ShardingSphere-JDBC 暂不提供。
--
--## 原理介绍
--
--与标准 SQL 一样，DistSQL 由 ShardingSphere 的解析引擎进行识别，将输入语句转换为抽象语法树，进而生成各个语法对应的 `Statement`，最后由合适的 `Handler` 进行业务处理。
--整体流程如下图所示：
--
--![Overview](https://shardingsphere.apache.org/document/current/img/distsql/overview.png)
--
--## 相关参考
--
--[用户手册：DistSQL](/cn/user-manual/shardingsphere-proxy/distsql/)
-diff --git a/docs/document/content/overview/distsql.en.md b/docs/document/content/overview/distsql.en.md
-deleted file mode 100644
-index 2bd038a4153..00000000000
---- a/docs/document/content/overview/distsql.en.md
-+++ /dev/null
-@@ -1,76 +0,0 @@
--+++
--pre = "<b>1.4 </b>"
--title = "DistSQL"
--weight = 4
--chapter = true
--+++
--
--## Definition
--
--DistSQL (Distributed SQL) is Apache ShardingSphere's specific SQL, providing additional operation capabilities compared to standard SQL.
--
--Flexible rule configuration and resource management & control capabilities are one of the characteristics of Apache ShardingSphere.
--
--When using 4.x and earlier versions, developers can operate data just like using a database, but they need to configure resources and rules through YAML file (or registry center). However, the YAML file format and the changes brought by using the registry center made it unfriendly to DBAs.
--
--Starting from version 5.x, DistSQL enables users to operate Apache ShardingSphere just like a database, transforming it from a framework and middleware for developers to a database product for DBAs.
--
--## Related Concepts
--
--DistSQL is divided into RDL, RQL, RAL and RUL.
--
--### RDL
--
--Resource & Rule Definition Language, is responsible for the definition of resources and rules.
--
--### RQL
--
--Resource & Rule Query Language, is responsible for the query of resources and rules.
--
--### RAL
--
--Resource & Rule Administration Language, is responsible for hint, circuit breaker, configuration import and export, scaling control and other management functions.
--
--### RUL
--
--Resource & Rule Utility Language, is responsible for SQL parsing, SQL formatting, preview execution plan, etc.
--
--## Impact on the System
--
--### Before
--
--Before having DistSQL, users used SQL to operate data while using YAML configuration files to manage ShardingSphere, as shown below:
--
--![Before](https://shardingsphere.apache.org/document/current/img/distsql/before.png)
--
--At that time, users faced the following problems:
--- Different types of clients are required to operate data and manage ShardingSphere configuration.
--- Multiple logical databases require multiple YAML files.
--- Editing a YAML file requires writing permissions.
--- Need to restart ShardingSphere after editing YAML.
--
--### After
--
--With the advent of DistSQL, the operation of ShardingSphere has also changed:
--
--![After](https://shardingsphere.apache.org/document/current/img/distsql/after.png)
--
--Now, the user experience has been greatly improved:
--- Uses the same client to operate data and ShardingSphere configuration.
--- No need for additional YAML files, and the logical databases are managed through DistSQL.
--- Editing permissions for files are no longer required, and configuration is managed through DistSQL.
--- Configuration changes take effect in real-time without restarting ShardingSphere.
--
--## Limitations
--
--DistSQL can be used only with ShardingSphere-Proxy, not with ShardingSphere-JDBC for now.
--
--## How it works
--
--Like standard SQL, DistSQL is recognized by the parsing engine of ShardingSphere. It converts the input statement into an abstract syntax tree and then generates the `Statement` corresponding to each grammar, which is processed by the appropriate `Handler`.
--
--![Overview](https://shardingsphere.apache.org/document/current/img/distsql/overview.png)
--
--## Related References
--
--[User Manual: DistSQL](/en/user-manual/shardingsphere-proxy/distsql/)
-diff --git a/docs/document/content/overview/introduction.cn.md b/docs/document/content/overview/introduction.cn.md
-index c84f1592ed0..23d5567dbee 100644
---- a/docs/document/content/overview/introduction.cn.md
-+++ b/docs/document/content/overview/introduction.cn.md
-@@ -16,7 +16,44 @@ Apache ShardingSphere 项目理念，是提供数据库增强计算服务平台
- ShardingSphere 已于 2020 年 4 月 16 日成为 [Apache 软件基金会](https://apache.org/index.html#projects-list)的顶级项目。
- 欢迎通过[邮件列表](mailto:dev@shardingsphere.apache.org)参与讨论。
- 
--## 产品优势
-+### ShardingSphere-JDBC
++resourceName ::=
++  identifier
++```
 +
-+ShardingSphere-JDBC 是 Apache ShardingSphere 的第一个产品，也是 Apache ShardingSphere 的前身。定位为轻量级 Java 框架，在 Java 的 JDBC 层提供的额外服务。
-+它使用客户端直连数据库，以 jar 包形式提供服务，无需额外部署和依赖，可理解为增强版的 JDBC 驱动，完全兼容 JDBC 和各种 ORM 框架。
++### Supplement
 +
-+* 适用于任何基于 JDBC 的 ORM 框架，如：JPA, Hibernate, Mybatis, Spring JDBC Template 或直接使用 JDBC；
-+* 支持任何第三方的数据库连接池，如：DBCP, C3P0, BoneCP, HikariCP 等；
-+* 支持任意实现 JDBC 规范的数据库，目前支持 MySQL，PostgreSQL，Oracle，SQLServer 以及任何可使用 JDBC 访问的数据库。
++- `RESOURCE` needs to use data source resource managed by RDL.
 +
-+|           | ShardingSphere-JDBC | ShardingSphere-Proxy |
-+| --------- | ------------------- | -------------------- |
-+| 数据库     | `任意`               | MySQL/PostgreSQL     |
-+| 连接消耗数  | `高`                | 低                    |
-+| 异构语言   | `仅 Java`            | 任意                  |
-+| 性能      | `损耗低`              | 损耗略高               |
-+| 无中心化   | `是`                 | 否                    |
-+| 静态入口   | `无`                 | 有                    |
++### Example
 +
-+ShardingSphere-JDBC 的优势在于对 Java 应用的友好度。
++#### Create a default single table rule
 +
-+### ShardingSphere-Proxy
++```sql
++CREATE DEFAULT SINGLE TABLE RULE RESOURCE = ds_0;
++```
 +
-+ShardingSphere-Proxy 是 Apache ShardingSphere 的第二个产品。它定位为透明化的数据库代理端，提供封装了数据库二进制协议的服务端版本，用于完成对异构语言的支持。
-+目前提供 MySQL 和 PostgreSQL（兼容 openGauss 等基于 PostgreSQL 的数据库）版本，它可以使用任何兼容 MySQL/PostgreSQL 协议的访问客户端（如：MySQL Command Client, MySQL Workbench, Navicat 等）操作数据，对 DBA 更加友好。
++### Reserved word
 +
-+* 向应用程序完全透明，可直接当做 MySQL/PostgreSQL 使用；
-+* 适用于任何兼容 MySQL/PostgreSQL 协议的的客户端。
++`CREATE`, `SHARDING`, `SINGLE`, `TABLE`, `RULE`, `RESOURCE`
 +
-+|           | ShardingSphere-JDBC | ShardingSphere-Proxy |
-+| --------- | ------------------- | -------------------- |
-+| 数据库     | 任意                 | `MySQL/PostgreSQL`   |
-+| 连接消耗数  | 高                  | `低`                  |
-+| 异构语言   | 仅 Java              | `任意`                |
-+| 性能      | 损耗低                | `损耗略高`             |
-+| 无中心化   | 是                   | `否`                  |
-+| 静态入口   | 无                   | `有`                  |
++### Related links
 +
-+## 产品定位
- 
- * 构建异构数据库上层生态和标准
- 
-diff --git a/docs/document/content/overview/introduction.en.md b/docs/document/content/overview/introduction.en.md
-index 0ff2ab32a9e..6c35330170b 100644
---- a/docs/document/content/overview/introduction.en.md
-+++ b/docs/document/content/overview/introduction.en.md
-@@ -20,7 +20,47 @@ It can solve many digital transformation challenges faced by enterprises and emp
- ShardingSphere became an [Apache](https://apache.org/index.html#projects-list) Top-Level Project on April 16, 2020.
- You are welcome to check out the mailing list and discuss via [mail](mailto:dev@shardingsphere.apache.org).
- 
--## Advantages
-+### ShardingSphere-JDBC
-+
-+As the community's first product and the predecessor of Apache ShardingSphere, ShardingSphere-JDBC is a lightweight Java framework that provides additional services at Java's JDBC layer. With the client connecting directly to the database, it provides services in the form of jar and requires no extra deployment and dependence. It can be considered as an enhanced version of the JDBC driver, which is fully compatible with JDBC and all kinds of ORM frameworks.
-+- Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template, or direct use of JDBC;
-+- Support any third-party database connection pool, such as DBCP, C3P0, BoneCP, HikariCP;
-+- Support any kind of JDBC standard database: MySQL, PostgreSQL, Oracle, SQLServer and any JDBC adapted databases.
-+
-+|                        | ShardingSphere-JDBC | ShardingSphere-Proxy |
-+| ---------------------- | ------------------- | -------------------- |
-+| Database               | `Any`               | MySQL/PostgreSQL     |
-+| Connections Count Cost | `More`              | Less                 |
-+| Heterogeneous language | `Java Only`         | Any                  |
-+| Performance            | `Low loss`          | Relatively High loss |
-+| Decentralization       | `Yes`               | No                   |
-+| Static entry           | `No`                | Yes                  |
-+
-+ShardingSphere-JDBC is suitable for java applications.
-+
-+### ShardingSphere-Proxy
-+
-+ShardingSphere-Proxy is Apache ShardingSphere's second product.
-+It is a transparent database proxy, providing a database server that encapsulates database binary protocol to support heterogeneous languages. 
-+
-+Currently, MySQL and PostgreSQL (compatible with PostgreSQL-based databases, such as openGauss) versions are provided.
-+It can use any kind of terminal (such as MySQL Command Client, MySQL Workbench, etc.) that is compatible with MySQL or PostgreSQL protocol to operate data, which is more friendly to DBAs.
-+
-+- Transparent to applications, it can be used directly as MySQL/PostgreSQL;
-+- Applicable to any kind of client that is compatible with MySQL/PostgreSQL protocol.
-+
-+|                        | ShardingSphere-JDBC | ShardingSphere-Proxy   |
-+| ---------------------- | ------------------- | ---------------------- |
-+| Database               | Any                 | `MySQL/PostgreSQL`     |
-+| Connections Count Cost | More                | `Less`                 |
-+| Heterogeneous language | Java Only           | `Any`                  |
-+| Performance            | Low loss            | `Relatively High loss` |
-+| Decentralization       | Yes                 | `No`                   |
-+| Static entry           | No                  | `Yes`                  |
-+
-+The advantages of ShardingSphere-Proxy lie in supporting heterogeneous languages and providing operational entries for DBA.
-+
-+## Positioning
- 
- - Build a standard layer & ecosystem above heterogeneous databases
- 
-diff --git a/docs/document/content/overview/jdbc_proxy.cn.md b/docs/document/content/overview/jdbc_proxy.cn.md
-index 35f5c464f1e..d8b24e258e3 100644
---- a/docs/document/content/overview/jdbc_proxy.cn.md
-+++ b/docs/document/content/overview/jdbc_proxy.cn.md
-@@ -1,14 +1,15 @@
- +++
- pre = "<b>1.3 </b>"
--title = "JDBC & Proxy"
-+title = "部署形态"
- weight = 3
- chapter = true
- +++
- 
-+## 部署形态
- Apache ShardingSphere 由 ShardingSphere-JDBC 和 ShardingSphere-Proxy 这 2 款既能够独立部署，又支持混合部署配合使用的产品组成。
- 它们均提供标准化的基于数据库作为存储节点的增量功能，可适用于如 Java 同构、异构语言、云原生等各种多样化的应用场景。
- 
--## ShardingSphere-JDBC 独立部署
-+### ShardingSphere-JDBC 独立部署
- 
- [![Maven Status](https://img.shields.io/maven-central/v/org.apache.shardingsphere/shardingsphere-jdbc.svg?color=green)](https://mvnrepository.com/artifact/org.apache.shardingsphere/shardingsphere-jdbc)
- 
-@@ -32,9 +33,7 @@ ShardingSphere-JDBC 是 Apache ShardingSphere 的第一个产品，也是 Apache
- 
- ShardingSphere-JDBC 的优势在于对 Java 应用的友好度。
- 
--源码：[https://github.com/apache/shardingsphere/tree/master/shardingsphere-jdbc](https://github.com/apache/shardingsphere/tree/master/shardingsphere-jdbc)
--
--## ShardingSphere-Proxy 独立部署
-+### ShardingSphere-Proxy 独立部署
- 
- [![Nightly-Download](https://img.shields.io/badge/nightly--builds-download-orange.svg)](https://nightlies.apache.org/shardingsphere/)
- [![Download](https://img.shields.io/badge/release-download-orange.svg)](/cn/downloads/)
-@@ -58,9 +57,8 @@ ShardingSphere-Proxy 是 Apache ShardingSphere 的第二个产品。它定位为
- | 静态入口   | 无                   | `有`                  |
- 
- ShardingSphere-Proxy 的优势在于对异构语言的支持，以及为 DBA 提供可操作入口。
--源码：[https://github.com/apache/shardingsphere/tree/master/shardingsphere-proxy](https://github.com/apache/shardingsphere/tree/master/shardingsphere-proxy)
- 
--## 混合部署架构
-+### 混合部署架构
- 
- ShardingSphere-JDBC 采用无中心化架构，与应用程序共享资源，适用于 Java 开发的高性能的轻量级 OLTP 应用；
- ShardingSphere-Proxy 提供静态入口以及异构语言的支持，独立于应用程序部署，适用于 OLAP 应用以及对分片数据库进行管理和运维的场景。
-@@ -69,3 +67,22 @@ Apache ShardingSphere 是多接入端共同组成的生态圈。
- 通过混合使用 ShardingSphere-JDBC 和 ShardingSphere-Proxy，并采用同一注册中心统一配置分片策略，能够灵活的搭建适用于各种场景的应用系统，使得架构师更加自由地调整适合于当前业务的最佳系统架构。
- 
- ![ShardingSphere Hybrid Architecture](https://shardingsphere.apache.org/document/current/img/shardingsphere-hybrid-architecture_v2.png)
-+
-+## 运行模式
-+
-+Apache ShardingSphere 是一套完善的产品，使用场景非常广泛。
-+除生产环境的集群部署之外，还为工程师在开发和自动化测试等场景提供相应的运行模式。
-+Apache ShardingSphere 提供的 2 种运行模式分别是单机模式和集群模式。
-+
-+### 单机模式
-+
-+能够将数据源和规则等元数据信息持久化，但无法将元数据同步至多个 Apache ShardingSphere 实例，无法在集群环境中相互感知。
-+通过某一实例更新元数据之后，会导致其他实例由于获取不到最新的元数据而产生不一致的错误。
-+适用于工程师在本地搭建 Apache ShardingSphere 环境。
-+
-+### 集群模式
-+
-+提供了多个 Apache ShardingSphere 实例之间的元数据共享和分布式场景下状态协调的能力。
-+在真实部署上线的生产环境，必须使用集群模式。
-+它能够提供计算能力水平扩展和高可用等分布式系统必备的能力。
-+集群环境需要通过独立部署的注册中心来存储元数据和协调节点状态。
-diff --git a/docs/document/content/overview/jdbc_proxy.en.md b/docs/document/content/overview/jdbc_proxy.en.md
-index 9ddff65d4ce..81e11f6b2ff 100644
---- a/docs/document/content/overview/jdbc_proxy.en.md
-+++ b/docs/document/content/overview/jdbc_proxy.en.md
-@@ -1,13 +1,15 @@
- +++
- pre = "<b>1.3 </b>"
--title = "JDBC & Proxy"
-+title = "Deployment"
- weight = 3
- chapter = true
- +++
- 
-+## Deployment
-+
- Apache ShardingSphere includes two independent clients: ShardingSphere-JDBC & ShardingSphere-Proxy. They all provide functions of data scale-out, distributed transaction and distributed governance, applicable in a variety of scenarios such as Java isomorphism, heterogeneous languages, and a cloud-native environment.
- 
--## ShardingSphere-JDBC
-+### ShardingSphere-JDBC
- 
- [![Maven Status](https://img.shields.io/maven-central/v/org.apache.shardingsphere/shardingsphere-jdbc.svg?color=green)](https://mvnrepository.com/artifact/org.apache.shardingsphere/shardingsphere-jdbc)
- 
-@@ -29,9 +31,7 @@ As the community's first product and the predecessor of Apache ShardingSphere, S
- 
- ShardingSphere-JDBC is suitable for java applications.
- 
--Source Codes: [https://github.com/apache/shardingsphere/tree/master/shardingsphere-jdbc](https://github.com/apache/shardingsphere/tree/master/shardingsphere-jdbc)
--
--## ShardingSphere-Proxy
-+### ShardingSphere-Proxy
- 
- [![Nightly-Release](https://img.shields.io/badge/nightly--builds-download-orange.svg)](https://nightlies.apache.org/shardingsphere/)
- [![Download](https://img.shields.io/badge/release-download-orange.svg)](/cn/downloads/)
-@@ -59,9 +59,7 @@ It can use any kind of terminal (such as MySQL Command Client, MySQL Workbench,
- 
- The advantages of ShardingSphere-Proxy lie in supporting heterogeneous languages and providing operational entries for DBA.
- 
--Source Codes: [https://github.com/apache/shardingsphere/tree/master/shardingsphere-proxy](https://github.com/apache/shardingsphere/tree/master/shardingsphere-proxy)
--
--## Hybrid Architecture
-+### Hybrid Architecture
- 
- ShardingSphere-JDBC adopts a decentralized architecture, applicable to high-performance light-weight OLTP applications developed with Java.
- ShardingSphere-Proxy provides static entry and supports all languages, applicable to OLAP applications and the sharding databases management and operation situation.
-@@ -70,3 +68,22 @@ Apache ShardingSphere is an ecosystem composed of multiple access ports.
- By combining ShardingSphere-JDBC and ShardingSphere-Proxy, and using the same registry to configure sharding strategies, it can flexibly build application systems for various scenarios, allowing architects to freely adjust the system architecture according to the current businesses. 
- 
- ![ShardingSphere Hybrid Architecture](https://shardingsphere.apache.org/document/current/img/shardingsphere-hybrid-architecture_v2.png)
-+
-+## Operation Modes
-+
-+Apache ShardingSphere is a complete set of products applicable to a wide range of usage scenarios.
-+In addition to the cluster deployment of the production environment, it also provides corresponding operation modes for engineers in the development process and automated testing scenarios. Apache ShardingSphere provides two runtime modes: standalone mode and cluster mode.
-+
-+### Standalone mode
-+
-+It can achieve data persistence in terms of metadata information such as data sources and rules, but it is not able to synchronize metadata to multiple Apache ShardingSphere instances or be aware of each other in a cluster environment.
-+Updating metadata through one instance causes inconsistencies in other instances because they cannot get the latest metadata.
-+It is ideal for engineers to build a ShardingSphere environment locally.
-+
-+### Cluster mode
-+
-+It provides metadata sharing between multiple Apache ShardingSphere instances and the capability to coordinate states in distributed scenarios.
-+In an actual production environment for deployment and release, you must use the cluster mode. 
-+
-+It provides the capabilities necessary for distributed systems, such as horizontal scaling of computing capability and high availability.
-+Clustered environments need to store metadata and coordinate nodes' status through a separately deployed registry center.
-diff --git a/docs/document/content/overview/mode.cn.md b/docs/document/content/overview/mode.cn.md
-deleted file mode 100644
-index 8d257bd777c..00000000000
---- a/docs/document/content/overview/mode.cn.md
-+++ /dev/null
-@@ -1,23 +0,0 @@
--+++
--pre = "<b>1.5 </b>"
--title = "运行模式"
--weight = 5
--chapter = true
--+++
--
--Apache ShardingSphere 是一套完善的产品，使用场景非常广泛。
--除生产环境的集群部署之外，还为工程师在开发和自动化测试等场景提供相应的运行模式。
--Apache ShardingSphere 提供的 2 种运行模式分别是单机模式和集群模式。
--
--## 单机模式
--
--能够将数据源和规则等元数据信息持久化，但无法将元数据同步至多个 Apache ShardingSphere 实例，无法在集群环境中相互感知。
--通过某一实例更新元数据之后，会导致其他实例由于获取不到最新的元数据而产生不一致的错误。
--适用于工程师在本地搭建 Apache ShardingSphere 环境。
--
--## 集群模式
--
--提供了多个 Apache ShardingSphere 实例之间的元数据共享和分布式场景下状态协调的能力。
--在真实部署上线的生产环境，必须使用集群模式。
--它能够提供计算能力水平扩展和高可用等分布式系统必备的能力。
--集群环境需要通过独立部署的注册中心来存储元数据和协调节点状态。
-diff --git a/docs/document/content/overview/mode.en.md b/docs/document/content/overview/mode.en.md
-deleted file mode 100644
-index 9945dc2c33f..00000000000
---- a/docs/document/content/overview/mode.en.md
-+++ /dev/null
-@@ -1,23 +0,0 @@
--+++
--pre = "<b>1.5 </b>"
--title = "Mode"
--weight = 5
--chapter = true
--+++
--
--Apache ShardingSphere is a complete set of products applicable to a wide range of usage scenarios.
--In addition to the cluster deployment of the production environment, it also provides corresponding operation modes for engineers in the development process and automated testing scenarios. Apache ShardingSphere provides two runtime modes: standalone mode and cluster mode.
--
--## Standalone mode
--
--It can achieve data persistence in terms of metadata information such as data sources and rules, but it is not able to synchronize metadata to multiple Apache ShardingSphere instances or be aware of each other in a cluster environment.
--Updating metadata through one instance causes inconsistencies in other instances because they cannot get the latest metadata.
--It is ideal for engineers to build a ShardingSphere environment locally.
--
--## Cluster mode
--
--It provides metadata sharing between multiple Apache ShardingSphere instances and the capability to coordinate states in distributed scenarios.
--In an actual production environment for deployment and release, you must use the cluster mode. 
--
--It provides the capabilities necessary for distributed systems, such as horizontal scaling of computing capability and high availability.
--Clustered environments need to store metadata and coordinate nodes' status through a separately deployed registry center.
-diff --git a/docs/document/content/user-manual/shardingsphere-proxy/distsql/_index.cn.md b/docs/document/content/user-manual/shardingsphere-proxy/distsql/_index.cn.md
-index b06a7db5875..42fdb00b09f 100644
---- a/docs/document/content/user-manual/shardingsphere-proxy/distsql/_index.cn.md
-+++ b/docs/document/content/user-manual/shardingsphere-proxy/distsql/_index.cn.md
-@@ -4,4 +4,75 @@ weight = 3
- chapter = true
- +++
- 
--本章节将介绍 [DistSQL](/cn/overview/distsql/) 的详细语法。
-+本章节将介绍 DistSQL 的详细语法。
-+
-+## 定义
-+
-+DistSQL（Distributed SQL）是 Apache ShardingSphere 特有的操作语言。 它与标准 SQL 的使用方式完全一致，用于提供增量功能的 SQL 级别操作能力。
-+
-+灵活的规则配置和资源管控能力是 Apache ShardingSphere 的特点之一。
-+
-+在使用 4.x 及其之前版本时，开发者虽然可以像使用原生数据库一样操作数据，但却需要通过本地文件或注册中心配置资源和规则。然而，操作习惯变更，对于运维工程师并不友好。
-+
-+从 5.x 版本开始，DistSQL（Distributed SQL）让用户可以像操作数据库一样操作 Apache ShardingSphere，使其从面向开发人员的框架和中间件转变为面向运维人员的数据库产品。
-+
-+## 相关概念
-+
-+DistSQL 细分为 RDL、RQL、RAL 和 RUL 四种类型。
-+
-+### RDL
-+
-+Resource & Rule Definition Language，负责资源和规则的创建、修改和删除。
-+
-+### RQL
-+
-+Resource & Rule Query Language，负责资源和规则的查询和展现。
-+
-+### RAL
-+
-+Resource & Rule Administration Language，负责强制路由、熔断、配置导入导出、数据迁移控制等管理功能。
-+
-+### RUL
-+
-+Resource & Rule Utility Language，负责 SQL 解析、SQL 格式化、执行计划预览等功能。
-+
-+## 对系统的影响
-+
-+### 之前
-+
-+在拥有 DistSQL 以前，用户一边使用 SQL 语句操作数据，一边使用 YAML 文件来管理 ShardingSphere 的配置，如下图：
-+
-+![Before](https://shardingsphere.apache.org/document/current/img/distsql/before.png)
-+
-+这时用户不得不面对以下几个问题：
-+- 需要通过不同类型的客户端来操作数据和管理 ShardingSphere 规则；
-+- 多个逻辑库需要多个 YAML 文件；
-+- 修改 YAML 需要文件的编辑权限；
-+- 修改 YAML 后需要重启 ShardingSphere。
-+
-+### 之后
-+
-+随着 DistSQL 的出现，对 ShardingSphere 的操作方式也得到了改变：
-+
-+![After](https://shardingsphere.apache.org/document/current/img/distsql/after.png)
-+
-+现在，用户的使用体验得到了巨大改善：
-+- 使用相同的客户端来管理数据和 ShardingSphere 配置；
-+- 不再额外创建 YAML 文件，通过 DistSQL 管理逻辑库；
-+- 不再需要文件的编辑权限，通过 DistSQL 来管理配置；
-+- 配置的变更实时生效，无需重启 ShardingSphere。
-+
-+## 使用限制
-+
-+DistSQL 只能用于 ShardingSphere-Proxy，ShardingSphere-JDBC 暂不提供。
-+
-+## 原理介绍
-+
-+与标准 SQL 一样，DistSQL 由 ShardingSphere 的解析引擎进行识别，将输入语句转换为抽象语法树，进而生成各个语法对应的 `Statement`，最后由合适的 `Handler` 进行业务处理。
-+整体流程如下图所示：
-+
-+![Overview](https://shardingsphere.apache.org/document/current/img/distsql/overview.png)
-+
-+## 相关参考
-+
-+[用户手册：DistSQL](/cn/user-manual/shardingsphere-proxy/distsql/)
-diff --git a/docs/document/content/user-manual/shardingsphere-proxy/distsql/_index.en.md b/docs/document/content/user-manual/shardingsphere-proxy/distsql/_index.en.md
-index 62d39c4743f..ca1b9d4ab53 100644
---- a/docs/document/content/user-manual/shardingsphere-proxy/distsql/_index.en.md
-+++ b/docs/document/content/user-manual/shardingsphere-proxy/distsql/_index.en.md
-@@ -4,4 +4,74 @@ weight = 3
- chapter = true
- +++
- 
--This chapter will introduce the detailed syntax of [DistSQL](/en/overview/distsql/).
-+This chapter will introduce the detailed syntax of DistSQL.
-+
-+## Definition
-+
-+DistSQL (Distributed SQL) is Apache ShardingSphere's specific SQL, providing additional operation capabilities compared to standard SQL.
-+
-+Flexible rule configuration and resource management & control capabilities are one of the characteristics of Apache ShardingSphere.
-+
-+When using 4.x and earlier versions, developers can operate data just like using a database, but they need to configure resources and rules through YAML file (or registry center). However, the YAML file format and the changes brought by using the registry center made it unfriendly to DBAs.
-+
-+Starting from version 5.x, DistSQL enables users to operate Apache ShardingSphere just like a database, transforming it from a framework and middleware for developers to a database product for DBAs.
-+
-+## Related Concepts
-+
-+DistSQL is divided into RDL, RQL, RAL and RUL.
-+
-+### RDL
-+
-+Resource & Rule Definition Language, is responsible for the definition of resources and rules.
-+
-+### RQL
-+
-+Resource & Rule Query Language, is responsible for the query of resources and rules.
-+
-+### RAL
-+
-+Resource & Rule Administration Language, is responsible for hint, circuit breaker, configuration import and export, scaling control and other management functions.
-+
-+### RUL
-+
-+Resource & Rule Utility Language, is responsible for SQL parsing, SQL formatting, preview execution plan, etc.
-+
-+## Impact on the System
-+
-+### Before
-+
-+Before having DistSQL, users used SQL to operate data while using YAML configuration files to manage ShardingSphere, as shown below:
-+
-+![Before](https://shardingsphere.apache.org/document/current/img/distsql/before.png)
-+
-+At that time, users faced the following problems:
-+- Different types of clients are required to operate data and manage ShardingSphere configuration.
-+- Multiple logical databases require multiple YAML files.
-+- Editing a YAML file requires writing permissions.
-+- Need to restart ShardingSphere after editing YAML.
-+
-+### After
-+
-+With the advent of DistSQL, the operation of ShardingSphere has also changed:
-+
-+![After](https://shardingsphere.apache.org/document/current/img/distsql/after.png)
-+
-+Now, the user experience has been greatly improved:
-+- Uses the same client to operate data and ShardingSphere configuration.
-+- No need for additional YAML files, and the logical databases are managed through DistSQL.
-+- Editing permissions for files are no longer required, and configuration is managed through DistSQL.
-+- Configuration changes take effect in real-time without restarting ShardingSphere.
-+
-+## Limitations
-+
-+DistSQL can be used only with ShardingSphere-Proxy, not with ShardingSphere-JDBC for now.
-+
-+## How it works
-+
-+Like standard SQL, DistSQL is recognized by the parsing engine of ShardingSphere. It converts the input statement into an abstract syntax tree and then generates the `Statement` corresponding to each grammar, which is processed by the appropriate `Handler`.
-+
-+![Overview](https://shardingsphere.apache.org/document/current/img/distsql/overview.png)
-+
-+## Related References
-+
-+[User Manual: DistSQL](/en/user-manual/shardingsphere-proxy/distsql/)
-diff --git a/docs/document/static/img/overview.cn_v2.png b/docs/document/static/img/overview.cn_v2.png
-index f98ab199dc7..1115c973f5d 100644
-Binary files a/docs/document/static/img/overview.cn_v2.png and b/docs/document/static/img/overview.cn_v2.png differ
++- [Reserved word](/en/reference/distsql/syntax/reserved-word/)
diff --git a/pdf/shardingsphere_docs_cn.pdf b/pdf/shardingsphere_docs_cn.pdf
index 17bad2f..72d4f7d 100644
--- a/pdf/shardingsphere_docs_cn.pdf
+++ b/pdf/shardingsphere_docs_cn.pdf
Binary files differ
diff --git a/pdf/shardingsphere_docs_en.pdf b/pdf/shardingsphere_docs_en.pdf
index eae9fcc..ad74f6c 100644
--- a/pdf/shardingsphere_docs_en.pdf
+++ b/pdf/shardingsphere_docs_en.pdf
Binary files differ