You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by zh...@apache.org on 2022/04/14 13:08:07 UTC
[shardingsphere] branch master updated: Correct punctuations in English documents (#16836)
This is an automated email from the ASF dual-hosted git repository.
zhangliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new bf787da3616 Correct punctuations in English documents (#16836)
bf787da3616 is described below
commit bf787da3616521a47202ee45cd088222dd9ff4ea
Author: 吴伟杰 <wu...@apache.org>
AuthorDate: Thu Apr 14 21:07:58 2022 +0800
Correct punctuations in English documents (#16836)
* Replace Chinese comma with English comma in English documents
* Replace Chinese semicolon with English semicolon in English documents
* Replace Chinese full stop with English full stop in English documents
* Replace Chinese comma with English comma in English documents
* Fix Nov_23_1_Integrate_SCTL_into_RAL.en.md
* Fix proxy.en.md
* Fix vote.en.md
* Replace Chinese brackets with English brackets in English documents
---
docs/blog/content/material/CNCF.en.md | 2 +-
...0_The_Ideal_Database_Management_Ecosystem.en.md | 2 +-
.../Nov_23_1_Integrate_SCTL_into_RAL.en.md | 26 +++++++++++-----------
...inute_Quick_Start_Guide_to_ShardingSphere.en.md | 4 ++--
...phere_Hulu_Story_Data_Processing_Shortcut.en.md | 2 +-
...aitiao_Story_of_an_Implementation_Journey.en.md | 2 +-
docs/blog/content/material/committer.en.md | 6 ++---
docs/blog/content/material/database.en.md | 2 +-
docs/blog/content/material/proxy.en.md | 4 ++--
docs/blog/content/material/realization.en.md | 8 +++----
docs/blog/content/material/solution.en.md | 6 ++---
.../content/contribute/code-conduct.en.md | 2 +-
.../community/content/contribute/contributor.en.md | 2 +-
docs/community/content/contribute/release.en.md | 4 ++--
docs/community/content/contribute/vote.en.md | 4 ++--
.../document/content/concepts/distsql/_index.en.md | 2 +-
.../content/features/observability/use-norms.en.md | 14 ++++++------
.../content/features/sharding/concept/table.en.md | 2 +-
.../shardingsphere-jdbc/java-api.en.md | 2 +-
.../shardingsphere-jdbc/spring-boot-starter.en.md | 6 ++---
.../shardingsphere-jdbc/yaml-configuration.en.md | 2 +-
.../shardingsphere-proxy/_index.en.md | 2 +-
.../rdl/resource-definition/add-resource.en.md | 4 ++--
.../rdl/resource-definition/drop-resource.en.md | 4 ++--
.../create-sharding-table-rule.en.md | 2 +-
docs/document/content/reference/faq/_index.en.md | 8 +++----
.../content/reference/management/_index.en.md | 2 +-
.../document/content/reference/shadow/_index.en.md | 4 ++--
.../content/reference/sharding/parse.en.md | 2 +-
.../reference/test/module-test/parser-test.en.md | 2 +-
.../reference/test/module-test/rewrite-test.en.md | 2 +-
.../builtin-algorithm/shadow.en.md | 2 +-
.../shardingsphere-jdbc/java-api/rules/ha.en.md | 2 +-
.../java-api/rules/readwrite-splitting.en.md | 4 ++--
.../special-api/observability/agent.en.md | 2 +-
.../spring-boot-starter/rules/ha.en.md | 4 ++--
.../spring-boot-starter/rules/shadow.en.md | 2 +-
.../spring-namespace/rules/ha.en.md | 2 +-
.../rules/readwrite-splitting.en.md | 4 ++--
.../shardingsphere-jdbc/yaml-config/rules/ha.en.md | 2 +-
.../distsql/syntax/ral/_index.en.md | 2 +-
.../syntax/rdl/rule-definition/sharding.en.md | 2 +-
.../rql/rule-query/readwrite-splitting.en.md | 2 +-
.../user-manual/shardingsphere-scaling/usage.en.md | 2 +-
44 files changed, 84 insertions(+), 84 deletions(-)
diff --git a/docs/blog/content/material/CNCF.en.md b/docs/blog/content/material/CNCF.en.md
index 10f59edd08b..d1d9014d67e 100644
--- a/docs/blog/content/material/CNCF.en.md
+++ b/docs/blog/content/material/CNCF.en.md
@@ -6,7 +6,7 @@ chapter = true
### CNCF
-(Cloud Native Computing Foundation)，is a cloud native computing open source software foundation founded by Google. It is committed to the popularization and sustainable development of Cloud Native technology. Cloud native technology helps enterprises and organizations to build and run agile and scalable applications in modern dynamic environments (such as public clouds, private clouds, and hybrid clouds) through a series of software, specifications, and standards. The representative clou [...]
+(Cloud Native Computing Foundation), is a cloud native computing open source software foundation founded by Google. It is committed to the popularization and sustainable development of Cloud Native technology. Cloud native technology helps enterprises and organizations to build and run agile and scalable applications in modern dynamic environments (such as public clouds, private clouds, and hybrid clouds) through a series of software, specifications, and standards. The representative clo [...]
### CNCF Landscape
diff --git a/docs/blog/content/material/Jan_28_Blog_X_Kernel_Optimizations_&_Upgrade_Guide_for_Apache_ShardingSphere_5.0.0_The_Ideal_Database_Management_Ecosystem.en.md b/docs/blog/content/material/Jan_28_Blog_X_Kernel_Optimizations_&_Upgrade_Guide_for_Apache_ShardingSphere_5.0.0_The_Ideal_Database_Management_Ecosystem.en.md
index 79877d6deb8..9a47251662b 100644
--- a/docs/blog/content/material/Jan_28_Blog_X_Kernel_Optimizations_&_Upgrade_Guide_for_Apache_ShardingSphere_5.0.0_The_Ideal_Database_Management_Ecosystem.en.md
+++ b/docs/blog/content/material/Jan_28_Blog_X_Kernel_Optimizations_&_Upgrade_Guide_for_Apache_ShardingSphere_5.0.0_The_Ideal_Database_Management_Ecosystem.en.md
@@ -480,7 +480,7 @@ Since the `t_order_item` table does not require encryption or decryption, its ro
As for the `t_order` table and the `t_user` table, we use the following SQL statements and manually create encrypt/decrypt tables on the underlying database of the routing result.
```
-# ds_0 Creare t_order_0、t_order_1 and t_user
+# ds_0 Creare t_order_0, t_order_1 and t_user
CREATE TABLE t_order_0(order_id INT(11) PRIMARY KEY, user_id INT(11), content_plain VARCHAR(100), content_cipher VARCHAR(100))
CREATE TABLE t_order_1(order_id INT(11) PRIMARY KEY, user_id INT(11), content_plain VARCHAR(100), content_cipher VARCHAR(100))
CREATE TABLE t_user(user_id INT(11) PRIMARY KEY, telephone_plain VARCHAR(100), telephone_cipher VARCHAR(100))
diff --git a/docs/blog/content/material/Nov_23_1_Integrate_SCTL_into_RAL.en.md b/docs/blog/content/material/Nov_23_1_Integrate_SCTL_into_RAL.en.md
index 06b8d74b0cf..f417d0139e7 100644
--- a/docs/blog/content/material/Nov_23_1_Integrate_SCTL_into_RAL.en.md
+++ b/docs/blog/content/material/Nov_23_1_Integrate_SCTL_into_RAL.en.md
@@ -12,7 +12,7 @@ Recently, the ShardingSphere community has redesigned the SCTL grammar and the e
## Review: What's RAL?
-RAL is a subtype of DistSQL. DistSQL contains three types: RDL、RQL and RAL.
+RAL is a subtype of DistSQL. DistSQL contains three types: RDL, RQL and RAL.
- Resource & Rule Definition Language (RDL)：to create, modify or delete resources and rules.
@@ -37,7 +37,7 @@ SCTL is made of the below commands：
| sctl:hint addDatabaseShardingValue xx=yy | For the current connection. Add database sharding value yy to the logical table xx.|
| sctl:hint addTableShardingValue xx=yy | For the current connection. Add table sharding value yy to the logical table xx.|
| sctl:hint clear | For the current connection only. Clear all hint setting.|
-| sctl:hint show status | For the current connection only. Query hint status: `primary_only:true/false，sharding_type:databases_only/databases_tables`|
+| sctl:hint show status | For the current connection only. Query hint status: `primary_only:true/false, sharding_type:databases_only/databases_tables`|
| sctl:hint show table status | For the current connection only. Query hint database sharding value of the logical table.|
## Why Integrate SCTL Now?
@@ -94,7 +94,7 @@ Input command
Output
-a. If successful, display "Query OK, 0 rows affected"；
+a. If successful, display "Query OK, 0 rows affected";
b. Execute `show variable transaction_type` again and the type is XA now.
@@ -179,7 +179,7 @@ Output
- `set readwrite_splitting hint source`
>For the current connection only. Set read-write splitting hint strategy (AUTO or WRITE).
-Supported source types include：AUTO and WRITE（case insensitive）.
+Supported source types include：AUTO and WRITE (case insensitive) .
> - AUTO： automated readwrite splitting hint
> - WRITE：compulsory hint at the master library
@@ -189,8 +189,8 @@ Input command
Output
-a. If sucessful，show "Query OK, 0 rows affected"；
-b. Re-execute `show readwrite_splitting hint status`; show the ource is changed into Write；
+a. If sucessful, show "Query OK, 0 rows affected";
+b. Re-execute `show readwrite_splitting hint status`; show the ource is changed into Write;
c. Execute `preview select * from t_order`and see the queried SQL will go to the master database.
mysql> preview select * from t_order;
@@ -269,7 +269,7 @@ Input command
Output
-a. If successful, show "Query OK, 0 rows affected"；
+a. If successful, show "Query OK, 0 rows affected";
b. Execute `show sharding hint status`; show `t_order_item`'s `database_sharding_values` as 1. Update `sharding_type value` as `databases_only`.
@@ -290,8 +290,8 @@ Input command
Output
-a. If successful，show "Query OK, 0 rows affected"；
-b. Execute `show sharding hint status`; Show `t_order_item`'s `database_sharding_values` as 5; update `sharding_type value` as `databases_tables`；
+a. If successful, show "Query OK, 0 rows affected";
+b. Execute `show sharding hint status`; Show `t_order_item`'s `database_sharding_values` as 5; update `sharding_type value` as `databases_tables`;
@@ -305,12 +305,12 @@ Enter the add command again to add an even value.
Output：
-a. If successful，show "Query OK, 0 rows affected"；
+a. If successful, show "Query OK, 0 rows affected";
b. Execute `show sharding hint status`; show `t_order_item`'s `database_sharding_values` = '5,10'：
-c. Execute `preview select * from t_order_item`; SQL hint contains ds_0 and ds_1：（ Because the hint values include both odd and even number so it contains all target data sources）
+c. Execute `preview select * from t_order_item`; SQL hint contains ds_0 and ds_1： ( Because the hint values include both odd and even number so it contains all target data sources)
@@ -324,7 +324,7 @@ Input command
Output
-a. If successful，show "Query OK, 0 rows affected"；
+a. If successful, show "Query OK, 0 rows affected";
b. Execute `show sharding hint status`; show `t_order_item`'s `database_sharding_values` as '5,10' while `table_sharding_values` is '0'：
@@ -360,7 +360,7 @@ Set hint value and then execute the command;
Output
-a. If successful，show "Query OK, 0 rows affected";
+a. If successful, show "Query OK, 0 rows affected";
b. Get readwrite_splitting hint default and sharding hint default; use `show readwrite_splitting hint status ;` or `show sharding hint status;` command to see the result.
**Note: Please remember: if you need to use DistSQL Hint, you need to enable the configuration`proxy-hint-enabled`of ShardingSphere-Proxy. For more information, please read:**
diff --git a/docs/blog/content/material/Oct_12_4_Updates_and_FAQ_Your_1_Minute_Quick_Start_Guide_to_ShardingSphere.en.md b/docs/blog/content/material/Oct_12_4_Updates_and_FAQ_Your_1_Minute_Quick_Start_Guide_to_ShardingSphere.en.md
index fcd5488a578..93b1c8365cd 100644
--- a/docs/blog/content/material/Oct_12_4_Updates_and_FAQ_Your_1_Minute_Quick_Start_Guide_to_ShardingSphere.en.md
+++ b/docs/blog/content/material/Oct_12_4_Updates_and_FAQ_Your_1_Minute_Quick_Start_Guide_to_ShardingSphere.en.md
@@ -8,7 +8,7 @@ chapter = true
Apache ShardingSphere is an Apache Top-Level project and is one of the most popular open-source big data projects. It was started about 5 years ago, and now ShardingSphere has over 14K+ stars and 270+ contributors in its community.
-The successful project has already launched and updated many versions. Apache ShardingSphere now supports many powerful features and keeps optimizing its configuration rules. We want to help users understand all features and configuration rules, to help them quickly test and run components，and ultimately help them achieve best performance, so we decide to start the shardingsphere-example project.
+The successful project has already launched and updated many versions. Apache ShardingSphere now supports many powerful features and keeps optimizing its configuration rules. We want to help users understand all features and configuration rules, to help them quickly test and run components, and ultimately help them achieve best performance, so we decide to start the shardingsphere-example project.
shardingsphere-example is an independent Maven project. It’s preserved in the “examples” file of Apache ShardingSphere. Link:
@@ -214,7 +214,7 @@ There are many modules in the project shardingsphere-example. But for now, we on
cd shardingsphere
mvn clean install -Prelease
-3. Import the shardingsphere-example project to your IDE;、
+3. Import the shardingsphere-example project to your IDE;
4. Prepare a manageable database environment, such as local MySQL examples;
diff --git a/docs/blog/content/material/Oct_12_5_E_Hualu_ShardingSphere_Hulu_Story_Data_Processing_Shortcut.en.md b/docs/blog/content/material/Oct_12_5_E_Hualu_ShardingSphere_Hulu_Story_Data_Processing_Shortcut.en.md
index 035347086b2..1438069fb9a 100644
--- a/docs/blog/content/material/Oct_12_5_E_Hualu_ShardingSphere_Hulu_Story_Data_Processing_Shortcut.en.md
+++ b/docs/blog/content/material/Oct_12_5_E_Hualu_ShardingSphere_Hulu_Story_Data_Processing_Shortcut.en.md
@@ -5,7 +5,7 @@ chapter = true
+++
> “ShardingSphere has greatly simplified sharding development and maintenance, which has played a very important role in our rapid product release. We estimate that ShardingSphere has saved us at least 4 months of R&D costs.”
-*— Shi Moxuan, Technical Director，E-Hualu*
+*— Shi Moxuan, Technical Director, E-Hualu*
At the beginning of this year, E-hualu officially launched its cloud service product “Hulu App” that targets non-business users. Since then, its architecture’s data stress has increased on a daily basis.
diff --git a/docs/blog/content/material/Oct_12_9_ShardingSphere_JD Baitiao_Story_of_an_Implementation_Journey.en.md b/docs/blog/content/material/Oct_12_9_ShardingSphere_JD Baitiao_Story_of_an_Implementation_Journey.en.md
index 3d40959714d..6d2c528ea95 100644
--- a/docs/blog/content/material/Oct_12_9_ShardingSphere_JD Baitiao_Story_of_an_Implementation_Journey.en.md
+++ b/docs/blog/content/material/Oct_12_9_ShardingSphere_JD Baitiao_Story_of_an_Implementation_Journey.en.md
@@ -8,7 +8,7 @@ chapter = true
>JD Baitiao, an internet credit products provider launched in 2014, has always been challenged by data explosion. Every shopping festival is like a technical test for us, but every time the technical staff professionals take proactive strategic initiatives in data architecture development to ensure everything goes smoothly.
-> --Dongfang Zhang，JD Batiao R&D Director
+> --Dongfang Zhang, JD Batiao R&D Director
## The Baitiao Data Architecture Evolution
diff --git a/docs/blog/content/material/committer.en.md b/docs/blog/content/material/committer.en.md
index 0bd1b8a66a5..874039fd904 100644
--- a/docs/blog/content/material/committer.en.md
+++ b/docs/blog/content/material/committer.en.md
@@ -22,7 +22,7 @@ To put it simply, whether it is showing off with other friends or writing on you
In addition, officially recognized committer will also get mailboxes with @apache suffix, and they can also be listed on the Apache website.
-（http://people.apache.org/committer-index.html）
+ (http://people.apache.org/committer-index.html)
Of the millions of engineers in the world, only a very small number of people can become a committer with these privileges, is it tempting?
@@ -63,9 +63,9 @@ P.S. ShardingSphere recently completed an important step in the transition to Ap
The following is the migrated URL:
-Official website（http://shardingsphere.apache.org/）
+Official website (http://shardingsphere.apache.org/)
-GitHub（https://github.com/apache/incubator-shardingsphere）
+GitHub (https://github.com/apache/incubator-shardingsphere)
### Conclusion
Since Apache ShardingSphere (Incubating) was open sourced in 2016, it has been constantly improving and developing, and is recognized by more and more enterprises and individuals: 6000+ stars and 70+ company success stories have been harvested on Github. In addition, more and more enterprises and individuals have joined the open source project of Apache ShardingSphere (Incubating), which has contributed tremendously to its growth and development.
diff --git a/docs/blog/content/material/database.en.md b/docs/blog/content/material/database.en.md
index 0a7ac59552a..6aa27450b14 100644
--- a/docs/blog/content/material/database.en.md
+++ b/docs/blog/content/material/database.en.md
@@ -46,7 +46,7 @@ Defines itself as a transparent database proxy, providing a database server that
-**Sharding-Sidecar（Planned）**
+**Sharding-Sidecar (Planned) **
Defines itself as a cloud native database agent of the Kubernetes environment, in charge of all the access to the database in the form of sidecar. It provides a mesh layer interacting with the database, we call this as Database Mesh.
diff --git a/docs/blog/content/material/proxy.en.md b/docs/blog/content/material/proxy.en.md
index 828f57a3240..b3d955c5eb9 100644
--- a/docs/blog/content/material/proxy.en.md
+++ b/docs/blog/content/material/proxy.en.md
@@ -200,8 +200,8 @@ Let's analyze the reason, and then I'll introduce second optimization: Current l
Main settings about cache as follows::
-* SO_RCVBUF/SO_SNDBUF is for TCP cache；
-
+* SO_RCVBUF/SO_SNDBUF is for TCP cache;
+
* ChannelOutboundBuffer is for Netty writing cache.
diff --git a/docs/blog/content/material/realization.en.md b/docs/blog/content/material/realization.en.md
index 67939bc46c0..1232e72a061 100644
--- a/docs/blog/content/material/realization.en.md
+++ b/docs/blog/content/material/realization.en.md
@@ -17,7 +17,7 @@ Senior Java Development Engineer
<!-- 高级Java开发工程师 -->
<!-- - 多年互联网开发经验，热爱开源技术，对分布式存储有浓厚的兴趣。熟悉ElasticSearch、HBase、Presto、Storm等离线和实时数据处理 -->
-- Years of internet development experience, love open source technology, full of interested in distributed storage. And familiar with online and realtime data processing with ElasticSearch、HBase、Presto、Storm and et.
+- Years of internet development experience, love open source technology, full of interested in distributed storage. And familiar with online and realtime data processing with ElasticSearch, HBase, Presto, Storm and et.
<!-- - 目前主要在Sharding-Sphere团队负责分布式事务的开发 -->
- Be responsible for distributed transaction implementation in Sharding-Sphere team.
@@ -126,7 +126,7 @@ TM needs a global transaction id(xid) to call XAResource interfaces and coordina
<!-- 弱XA通过去掉XA的Prepare阶段，以达到减少资源锁定范围而提升并发性能的效果。典型的实现为在一个业务线程中，遍历所有的数据库连接，依次做commit或者rollback。弱XA同本地事务相比，性能损耗低，但在事务提交的执行过程中，若出现网络故障、数据库宕机等预期之外的异常，将会造成数据不一致，且无法进行回滚。基于弱XA的事务无需额外的实现成本，因此Sharding-Sphere默认支持。 -->
-Comparing to 2PC, weak XA without prepare phase can benefit for reducing resource blocking and improving concurrency. The implementation only needs to iterate and call commit/callback on each datasource connection in a business thread. Performance of weak XA almost without reducing compares to local transaction. When has network failures、database crash and et., weak XA will lead inconsistent data and can't be rollback. Weak XA transaction implementation doesn't need extra efforts, so Sha [...]
+Comparing to 2PC, weak XA without prepare phase can benefit for reducing resource blocking and improving concurrency. The implementation only needs to iterate and call commit/callback on each datasource connection in a business thread. Performance of weak XA almost without reducing compares to local transaction. When has network failures, database crash and et., weak XA will lead inconsistent data and can't be rollback. Weak XA transaction implementation doesn't need extra efforts, so Sh [...]
<!-- **二阶段提交：2PC** -->
@@ -141,7 +141,7 @@ All local transactions will use default isolation level to lock resources, recor
<!-- 开启XA全局事务后，所有子事务会按照本地默认的隔离级别锁定资源，并记录undo和redo日志，然后由TM发起prepare投票，询问所有的子事务是否可以进行提交：当所有子事务反馈的结果为“yes”时，TM再发起commit；若其中任何一个子事务反馈的结果为“no”，TM则发起rollback；如果在prepare阶段的反馈结果为yes，而commit的过程中出现宕机等异常时，则在节点服务重启后，可根据XA recover再次进行commit补偿，以保证数据的一致性。 -->
-On 2PC model, the prepare stage needs to wait all involved RMs response and that may lead resource locked for a long time，so it's not suitable for high concurrency and time-consumed sub transaction scenario.
+On 2PC model, the prepare stage needs to wait all involved RMs response and that may lead resource locked for a long time, so it's not suitable for high concurrency and time-consumed sub transaction scenario.
<!-- 2PC模型中，在prepare阶段需要等待所有参与子事务的反馈，因此可能造成数据库资源锁定时间过长，不适合并发高以及子事务生命周长较长的业务场景。 -->
@@ -422,7 +422,7 @@ Both XA and BASE transaction are supported by Sharding-Sphere, and allows to sel
Sharding-Sphere TM integrated XA and BASE transaction model:
-- For XA transaction, using SPI makes weak XA、Atomikos、Narayana are mutually exclusive.
+- For XA transaction, using SPI makes weak XA, Atomikos, Narayana are mutually exclusive.
<!-- 下面将Sharding-Sphere内部如何用事件驱动方式，将事务从分片主流程中解耦进行详细说明： -->
The following section will explain how to decouple transaction from main process by event-driven:
diff --git a/docs/blog/content/material/solution.en.md b/docs/blog/content/material/solution.en.md
index 0de90eb723b..e1c7c6a8044 100644
--- a/docs/blog/content/material/solution.en.md
+++ b/docs/blog/content/material/solution.en.md
@@ -6,14 +6,14 @@ chapter = true
### Author
-Liang Zhang，Leader of Data R&D of JD.com, initiator & PPMC of Apache ShardingSphere.
+Liang Zhang, Leader of Data R&D of JD.com, initiator & PPMC of Apache ShardingSphere.
Love open source, currently leading open source project ShardingSphere (formerly known as Sharding-JDBC) and Elastic-Job. Good at using Java as the popular distributed architecture and Kubernetes and Mesos as the popular cloud platform, admiring elegant codes, and having more research on how to write expressive codes.
At present, focus on improving ShardingSphere to be the industry's first-class financial data solution. ShardingSphere has entered the Apache Incubator, is the first open source project of the Jingdong Group to enter the Apache Software Foundation, and is also the first distributed database middleware of the Apache Software Foundation.
---
-Ning Jiang，Technical expert of Huawei Open Source Competency Center, project leader of Apache ServiceComb. Former chief software engineer of Red Hat Software. He has more than ten years of experience in enterprise-level open source middleware development, rich experience in Java development, and also is the enthusiast of functional programming. Since 2006, he has been engaged in the development of the Apache open source middleware projects, and has participated in the development of Apac [...]
+Ning Jiang, Technical expert of Huawei Open Source Competency Center, project leader of Apache ServiceComb. Former chief software engineer of Red Hat Software. He has more than ten years of experience in enterprise-level open source middleware development, rich experience in Java development, and also is the enthusiast of functional programming. Since 2006, he has been engaged in the development of the Apache open source middleware projects, and has participated in the development of Apa [...]
Blog site：https://willemjiang.github.io/
@@ -115,7 +115,7 @@ Provides APIs for users and SPIs for developers.
The parent module of two-phases commit transaction. Currently only the sharding-transaction-xa module provides XA protocol support. In the future, more types of transactions based on two-phase commit will be introduced, such as `percolator`, see:
-[https://storage.googleapis.com/pub-tools-public-publication-data/pdf/36726.pdf]。
+[https://storage.googleapis.com/pub-tools-public-publication-data/pdf/36726.pdf].
- sharding-transaction-base:
diff --git a/docs/community/content/contribute/code-conduct.en.md b/docs/community/content/contribute/code-conduct.en.md
index b727bb877aa..0cb7ffe064c 100644
--- a/docs/community/content/contribute/code-conduct.en.md
+++ b/docs/community/content/contribute/code-conduct.en.md
@@ -19,7 +19,7 @@ The following code of conduct is based on full compliance with [ASF CODE OF COND
- Make sure the test coverage rate is not lower than the master branch.
- Careful consideration for each `pull request`; Small and frequent `pull request` with complete unit function is welcomed.
- Conform to `Contributor Covenant Code of Conduct` below.
- - If using IDEA，you can import the recommended [Settings](https://shardingsphere.apache.org/community/data/shardingsphere-settings.jar).
+ - If using IDEA, you can import the recommended [Settings](https://shardingsphere.apache.org/community/data/shardingsphere-settings.jar).
## Contributor Covenant Code of Conduct
diff --git a/docs/community/content/contribute/contributor.en.md b/docs/community/content/contribute/contributor.en.md
index 62931792dd8..6ab831bc40d 100644
--- a/docs/community/content/contribute/contributor.en.md
+++ b/docs/community/content/contribute/contributor.en.md
@@ -13,7 +13,7 @@ You can report a bug, submit a new function enhancement suggestion, or submit a
- [Create](https://github.com/apache/shardingsphere/issues/new/choose) a new issue and choose the type of issue.
- Define the issue with a clear and descriptive title.
- Fill in necessary information according to the template.
- - Choose a label after issue created, for example: bug，enhancement，discussion.
+ - Choose a label after issue created, for example: bug, enhancement, discussion.
- Please pay attention for your issue, you may need provide more information during discussion.
## Developer Flow
diff --git a/docs/community/content/contribute/release.en.md b/docs/community/content/contribute/release.en.md
index aa180ff602d..73b39c9d8a9 100644
--- a/docs/community/content/contribute/release.en.md
+++ b/docs/community/content/contribute/release.en.md
@@ -8,7 +8,7 @@ chapter = true
**1. Confirm release notes**
-The release note should be provided in Chinese / English， confirm whether the Chinese description is clear and whether the English translation is accurate,
+The release note should be provided in Chinese / English, confirm whether the Chinese description is clear and whether the English translation is accurate,
and shall be classified according to the following labels:
1. New Feature
@@ -581,7 +581,7 @@ Remove the previous release from the [**Release Area**](https://dist.apache.org/
svn del -m "Archiving release ${PREVIOUS.RELEASE.VERSION}" https://dist.apache.org/repos/dist/release/shardingsphere/${PREVIOUS.RELEASE.VERSION}
```
-Previous releases will be archived automatically in [Archive repository](https://archive.apache.org/dist/shardingsphere/)。
+Previous releases will be archived automatically in [Archive repository](https://archive.apache.org/dist/shardingsphere/).
Incubating stage versions will be archived automatically in [Incubator Archive repository](https://archive.apache.org/dist/incubator/shardingsphere/)
diff --git a/docs/community/content/contribute/vote.en.md b/docs/community/content/contribute/vote.en.md
index c8e28bfca1a..3bcb70089b4 100644
--- a/docs/community/content/contribute/vote.en.md
+++ b/docs/community/content/contribute/vote.en.md
@@ -152,7 +152,7 @@ The Apache ShardingSphere project proposes to invite (nominee) to join the PMC.
The vote result is available here:
(vote link here)
-Thank you，
-（initiator)
+Thank you,
+(initiator)
```
diff --git a/docs/document/content/concepts/distsql/_index.en.md b/docs/document/content/concepts/distsql/_index.en.md
index fc10c951f46..e95a69e02dd 100644
--- a/docs/document/content/concepts/distsql/_index.en.md
+++ b/docs/document/content/concepts/distsql/_index.en.md
@@ -7,7 +7,7 @@ chapter = true
## Background
-DistSQL（Distributed SQL）is Apache ShardingSphere specific SQL, which provide added-on operation capability beside standard SQL.
+DistSQL (Distributed SQL) is Apache ShardingSphere specific SQL, which provide added-on operation capability beside standard SQL.
## Challenges
diff --git a/docs/document/content/features/observability/use-norms.en.md b/docs/document/content/features/observability/use-norms.en.md
index deb23e95929..2e97d87eaa1 100644
--- a/docs/document/content/features/observability/use-norms.en.md
+++ b/docs/document/content/features/observability/use-norms.en.md
@@ -88,15 +88,15 @@ plugins:
| Name | Description | Value range | Default value |
| :--------- | :-------- |:--------- | :-------- |
-| JVM_INFORMATION_COLLECTOR_ENABLED | Start JVM collector | true、false | true |
+| JVM_INFORMATION_COLLECTOR_ENABLED | Start JVM collector | true, false | true |
| SERVICE_NAME | Tracking service name | Custom | shardingsphere-agent |
-| JAEGER_SAMPLER_TYPE | Jaeger sample rate type | const、probabilistic、ratelimiting、remote | const |
-| JAEGER_SAMPLER_PARAM | Jaeger sample rate parameter |const:0、1, probabilistic:0.0 - 1.0, ratelimiting: > 0, Customize the number of acquisitions per second，remote：need to customize the remote service addres,JAEGER_SAMPLER_MANAGER_HOST_PORT | 1（const type）|
-| SAMPLER_TYPE | Zipkin sample rate type | const、counting、ratelimiting、boundary | const |
-| SAMPLER_PARAM | Zipkin sampling rate parameter |const:0、1, counting:0.01 - 1.0, ratelimiting: > 0, boundary:0.0001 - 1.0 | 1（const type）|
+| JAEGER_SAMPLER_TYPE | Jaeger sample rate type | const, probabilistic, ratelimiting, remote | const |
+| JAEGER_SAMPLER_PARAM | Jaeger sample rate parameter |const:0, 1, probabilistic:0.0 - 1.0, ratelimiting: > 0, Customize the number of acquisitions per second, remote：need to customize the remote service addres,JAEGER_SAMPLER_MANAGER_HOST_PORT | 1 (const type) |
+| SAMPLER_TYPE | Zipkin sample rate type | const, counting, ratelimiting, boundary | const |
+| SAMPLER_PARAM | Zipkin sampling rate parameter |const:0, 1, counting:0.01 - 1.0, ratelimiting: > 0, boundary:0.0001 - 1.0 | 1 (const type) |
| otel.resource.attributes | opentelemetry properties | String key value pair (, split) | service.name=shardingsphere-agent |
-| otel.traces.exporter | Tracing expoter | zipkin、jaeger | zipkin |
-| otel.traces.sampler | Opentelemetry sample rate type | always_on、always_off、traceidratio | always_on |
+| otel.traces.exporter | Tracing expoter | zipkin, jaeger | zipkin |
+| otel.traces.sampler | Opentelemetry sample rate type | always_on, always_off, traceidratio | always_on |
| otel.traces.sampler.arg | Opentelemetry sample rate parameter | traceidratio：0.0 - 1.0 | 1.0 |
diff --git a/docs/document/content/features/sharding/concept/table.en.md b/docs/document/content/features/sharding/concept/table.en.md
index dd840acae34..e63efa0a915 100644
--- a/docs/document/content/features/sharding/concept/table.en.md
+++ b/docs/document/content/features/sharding/concept/table.en.md
@@ -47,7 +47,7 @@ SELECT i.* FROM t_order_0 o JOIN t_order_item_0 i ON o.order_id=i.order_id WHERE
SELECT i.* FROM t_order_1 o JOIN t_order_item_1 i ON o.order_id=i.order_id WHERE o.order_id in (10, 11);
```
-In them, since table `t_order` specifies sharding conditions， it will be taken by ShardingSphere as the primary table of query.
+In them, since table `t_order` specifies sharding conditions, it will be taken by ShardingSphere as the primary table of query.
All the route computations will only use the sharding strategy of the primary table, so sharding computation of `t_order_item` table will use the conditions of `t_order`.
## Broadcast Table
diff --git a/docs/document/content/reference/api-change-history/shardingsphere-jdbc/java-api.en.md b/docs/document/content/reference/api-change-history/shardingsphere-jdbc/java-api.en.md
index 67204daa1e2..4a4adf2ab9b 100644
--- a/docs/document/content/reference/api-change-history/shardingsphere-jdbc/java-api.en.md
+++ b/docs/document/content/reference/api-change-history/shardingsphere-jdbc/java-api.en.md
@@ -436,7 +436,7 @@ Property configuration items, can be of the following properties.
| *Name* | *DataType* | *Explanation* |
| :-------------------- | :--------------------------- | :---------------------------------- |
-| instanceConfigurationMap | Map<String, CenterConfiguration> | config map of config-center®istry-center，the key is center’s name，the value is the config-center/registry-center |
+| instanceConfigurationMap | Map<String, CenterConfiguration> | config map of config-center®istry-center, the key is center’s name, the value is the config-center/registry-center |
#### CenterConfiguration
diff --git a/docs/document/content/reference/api-change-history/shardingsphere-jdbc/spring-boot-starter.en.md b/docs/document/content/reference/api-change-history/shardingsphere-jdbc/spring-boot-starter.en.md
index ce8a611e1c5..8c7c143460d 100644
--- a/docs/document/content/reference/api-change-history/shardingsphere-jdbc/spring-boot-starter.en.md
+++ b/docs/document/content/reference/api-change-history/shardingsphere-jdbc/spring-boot-starter.en.md
@@ -62,7 +62,7 @@ spring.shardingsphere.rules.sharding.key-generators.<key-generate-algorithm-name
spring.shardingsphere.rules.sharding.key-generators.<key-generate-algorithm-name>.props.xxx= # Key generate algorithm properties
```
-Please refer to [Built-in sharding Algorithm List](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding) and [Built-in keygen Algorithm List](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen)。
+Please refer to [Built-in sharding Algorithm List](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/sharding) and [Built-in keygen Algorithm List](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/keygen).
### Readwrite-splitting
@@ -298,11 +298,11 @@ spring.shardingsphere.props.check.table.metadata.enabled= #Whether to check meta
```properties
#Omit data source configurations; keep it consistent with data sharding
-spring.shardingsphere.encrypt.encryptors.<encryptor-name>.type= #Type of encryptor，use user-defined ones or built-in ones, e.g. MD5/AES
+spring.shardingsphere.encrypt.encryptors.<encryptor-name>.type= #Type of encryptor, use user-defined ones or built-in ones, e.g. MD5/AES
spring.shardingsphere.encrypt.encryptors.<encryptor-name>.props.<property-name>= #Properties, Notice: when use AES encryptor, `aes.key.value` for AES encryptor need to be set
spring.shardingsphere.encrypt.tables.<table-name>.columns.<logic-column-name>.plainColumn= #Plain column name
spring.shardingsphere.encrypt.tables.<table-name>.columns.<logic-column-name>.cipherColumn= #Cipher column name
-spring.shardingsphere.encrypt.tables.<table-name>.columns.<logic-column-name>.assistedQueryColumn= #AssistedColumns for query，when use ShardingQueryAssistedEncryptor, it can help query encrypted data
+spring.shardingsphere.encrypt.tables.<table-name>.columns.<logic-column-name>.assistedQueryColumn= #AssistedColumns for query, when use ShardingQueryAssistedEncryptor, it can help query encrypted data
spring.shardingsphere.encrypt.tables.<table-name>.columns.<logic-column-name>.encryptor= #Encryptor name
```
diff --git a/docs/document/content/reference/api-change-history/shardingsphere-jdbc/yaml-configuration.en.md b/docs/document/content/reference/api-change-history/shardingsphere-jdbc/yaml-configuration.en.md
index 9b02a8678df..3a9cc7e78f6 100644
--- a/docs/document/content/reference/api-change-history/shardingsphere-jdbc/yaml-configuration.en.md
+++ b/docs/document/content/reference/api-change-history/shardingsphere-jdbc/yaml-configuration.en.md
@@ -279,7 +279,7 @@ encryptRule:
<logic-column-name>:
plainColumn: # Plaintext column name
cipherColumn: # Ciphertext column name
- assistedQueryColumn: # AssistedColumns for query，when use ShardingQueryAssistedEncryptor, it can help query encrypted data
+ assistedQueryColumn: # AssistedColumns for query, when use ShardingQueryAssistedEncryptor, it can help query encrypted data
encryptor: # Encrypt name
```
diff --git a/docs/document/content/reference/api-change-history/shardingsphere-proxy/_index.en.md b/docs/document/content/reference/api-change-history/shardingsphere-proxy/_index.en.md
index 5063b5e2e50..4f558004dcc 100644
--- a/docs/document/content/reference/api-change-history/shardingsphere-proxy/_index.en.md
+++ b/docs/document/content/reference/api-change-history/shardingsphere-proxy/_index.en.md
@@ -180,7 +180,7 @@ encryptRule:
<logic-column-name>:
plainColumn: # plaintext column name.
cipherColumn: # ciphertext column name.
- assistedQueryColumn: # AssistedColumns for query，when use ShardingQueryAssistedEncryptor, it can help query encrypted data.
+ assistedQueryColumn: # AssistedColumns for query, when use ShardingQueryAssistedEncryptor, it can help query encrypted data.
encryptor: # encrypt name.
props:
query.with.cipher.column: true #Whether use cipherColumn to query or not
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 d6478aaf215..59402797ea1 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
@@ -86,7 +86,7 @@ ADD RESOURCE ds_2 (
### Reserved word
- ADD、RESOURCE、HOST、PORT、DB、USER、PASSWORD、PROPERTIES、URL
+ ADD, RESOURCE, HOST, PORT, DB, USER, PASSWORD, PROPERTIES, URL
### Related links
-- [Reserved word](/en/reference/distsql/syntax/reserved-word/)
\ No newline at end of file
+- [Reserved word](/en/reference/distsql/syntax/reserved-word/)
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 51f42fc8272..6dbd6654c3f 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
@@ -41,7 +41,7 @@ DROP RESOURCE IF EXISTS ds_2;
### Reserved word
- DROP、 RESOURCE、 IF、 EXISTS、 IGNORE、 SINGLE、 TABLES
+ DROP, RESOURCE, IF, EXISTS, IGNORE, SINGLE, TABLES
### Related links
-- [Reserved word](/en/reference/distsql/syntax/reserved-word/)
\ No newline at end of file
+- [Reserved word](/en/reference/distsql/syntax/reserved-word/)
diff --git a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/create-sharding-table-rule.en.md b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/create-sharding-table-rule.en.md
index 28a84b2a112..e78c78ff54e 100644
--- a/docs/document/content/reference/distsql/syntax/rdl/rule-definition/create-sharding-table-rule.en.md
+++ b/docs/document/content/reference/distsql/syntax/rdl/rule-definition/create-sharding-table-rule.en.md
@@ -136,7 +136,7 @@ CREATE SHARDING TABLE RULE t_order (
### Reserved word
- CREATE、SHARDING、TABLE、RULE、DATANODES、DATABASE_STRATEGY、TABLE_STRATEGY、KEY_GENERATE_STRATEGY、RESOURCES、SHARDING_COLUMN、TYPE、SHARDING_COLUMN、KEY_GENERATOR、SHARDING_ALGORITHM、COLUMN、NAME、PROPERTIES
+ CREATE, SHARDING, TABLE, RULE, DATANODES, DATABASE_STRATEGY, TABLE_STRATEGY, KEY_GENERATE_STRATEGY, RESOURCES, SHARDING_COLUMN, TYPE, SHARDING_COLUMN, KEY_GENERATOR, SHARDING_ALGORITHM, COLUMN, NAME, PROPERTIES
### Related links
- [Reserved word](/en/reference/distsql/syntax/reserved-word/)
diff --git a/docs/document/content/reference/faq/_index.en.md b/docs/document/content/reference/faq/_index.en.md
index ddf28add665..c823c7e19a9 100644
--- a/docs/document/content/reference/faq/_index.en.md
+++ b/docs/document/content/reference/faq/_index.en.md
@@ -67,8 +67,8 @@ Answer:
1. ShardingSphere-Proxy could be considered as a mysql sever, so we recommend using mysql command line tool to connect to and operate it.
2. If users would like use a third-party database tool, there may be some errors cause of the certain implementation/options.
3. The currently tested third-party database tools are as follows:
- - Navicat：11.1.13、15.0.20.
- - DataGrip：2020.1、2021.1 (turn on "introspect using jdbc metadata" in idea or datagrip).
+ - Navicat：11.1.13, 15.0.20.
+ - DataGrip：2020.1, 2021.1 (turn on "introspect using jdbc metadata" in idea or datagrip).
- WorkBench：8.0.25.
## [Proxy] When using a client such as Navicat to connect to ShardingSphere-Proxy, if ShardingSphere-Proxy does not create a Schema or does not add a Resource, the client connection will fail?
@@ -313,7 +313,7 @@ https://ourcodeworld.com/articles/read/109/how-to-solve-filename-too-long-error-
Answer:
-In Apache ShardingSphere, many functionality implementation are uploaded through [SPI](/en/concepts/pluggable/), such as Distributed Primary Key. These functions load SPI implementation by configuring the `type`，so the `type` must be specified in the configuration file.
+In Apache ShardingSphere, many functionality implementation are uploaded through [SPI](/en/concepts/pluggable/), such as Distributed Primary Key. These functions load SPI implementation by configuring the `type`, so the `type` must be specified in the configuration file.
## [Other] How to speed up the metadata loading when service starts up?
@@ -417,4 +417,4 @@ The ShardingSphere assembled the SQL using the following code:
return tables.isEmpty() ? String.format(TABLE_META_DATA_SQL, collation)
: String.format(TABLE_META_DATA_SQL_IN_TABLES, collation, tables.stream().map(each -> String.format("'%s'", each)).collect(Collectors.joining(",")));
}
-```
\ No newline at end of file
+```
diff --git a/docs/document/content/reference/management/_index.en.md b/docs/document/content/reference/management/_index.en.md
index c540a84481a..9565d6dcd5d 100644
--- a/docs/document/content/reference/management/_index.en.md
+++ b/docs/document/content/reference/management/_index.en.md
@@ -54,7 +54,7 @@ namespace
### /rules
-global rule configurations， including configure the username and password for ShardingSphere-Proxy.
+global rule configurations, including configure the username and password for ShardingSphere-Proxy.
```yaml
- !AUTHORITY
diff --git a/docs/document/content/reference/shadow/_index.en.md b/docs/document/content/reference/shadow/_index.en.md
index 538ba204758..b2b021acdac 100644
--- a/docs/document/content/reference/shadow/_index.en.md
+++ b/docs/document/content/reference/shadow/_index.en.md
@@ -46,7 +46,7 @@ Support two type shadow algorithms.
The shadow judgment first judges whether there is an intersection between SQL related tables and configured shadow tables.
-If there is an intersection, determine the shadow algorithm associated with the shadow table of the intersection in turn，and any one of them was successful. SQL statement executed shadow DB.
+If there is an intersection, determine the shadow algorithm associated with the shadow table of the intersection in turn, and any one of them was successful. SQL statement executed shadow DB.
If shadow tables have no intersection, or shadow algorithms are unsuccessful, SQL statement executed production DB.
@@ -72,7 +72,7 @@ Shadow algorithm details, please refer to [List of built-in shadow algorithms](/
Assume that the e-commerce website wants to perform pressure testing on the order business,
-the pressure testing related table `t_order` is a shadow table，the production data executed to the `ds` production DB, and the pressure testing data executed to the database `ds_shadow` shadow DB.
+the pressure testing related table `t_order` is a shadow table, the production data executed to the `ds` production DB, and the pressure testing data executed to the database `ds_shadow` shadow DB.
### Shadow DB configuration
diff --git a/docs/document/content/reference/sharding/parse.en.md b/docs/document/content/reference/sharding/parse.en.md
index 8145469417b..8d9255b0da7 100644
--- a/docs/document/content/reference/sharding/parse.en.md
+++ b/docs/document/content/reference/sharding/parse.en.md
@@ -122,4 +122,4 @@ example：
|CREATE TABLE IF NOT EXISTS <br>`runoob_tbl`(`runoob_id` INT UNSIGNED AUTO_INCREMENT,`runoob_title` VARCHAR(100) NOT NULL,<br>`runoob_author` VARCHAR(40) NOT NULL,`runoob_test` NATIONAL CHAR(40),<br>`submission_date` DATE,PRIMARY KEY (`runoob_id`))ENGINE=InnoDB DEFAULT CHARSET=utf8;|CREATE TABLE IF NOT EXISTS `runoob_tbl` (<br>    `runoob_id` INT UNSIGNED AUTO_INCREMENT,<br>    `runoob_title` VARCHAR(100) NOT NULL,<br>    `runoo [...]
|INSERT INTO t_order_item(order_id, user_id, status, creation_date) <br>values (1, 1, 'insert', '2017-08-08'), (2, 2, 'insert', '2017-08-08') ON DUPLICATE KEY UPDATE status = 'init';|INSERT INTO t_order_item (order_id , user_id , status , creation_date)<br>VALUES<br>    (1, 1, 'insert', '2017-08-08'),<br>    (2, 2, 'insert', '2017-08-08')<br>ON DUPLICATE KEY UPDATE status = 'init';|
|INSERT INTO t_order SET order_id = 1, user_id = 1, status = convert(to_base64(aes_encrypt(1, 'key')) USING utf8)<br> ON DUPLICATE KEY UPDATE status = VALUES(status);|INSERT INTO t_order SET order_id = 1,<br>    user_id = 1,<br>    status = CONVERT(to_base64(aes_encrypt(1 , 'key')) USING utf8)<br>ON DUPLICATE KEY UPDATE status = VALUES(status);|
-|INSERT INTO t_order (order_id, user_id, status) SELECT order_id, user_id, status FROM t_order WHERE order_id = 1；|INSERT INTO t_order (order_id , user_id , status) <br>SELECT order_id , user_id , status <br>FROM t_order<br>WHERE <br>    order_id = 1;|
+|INSERT INTO t_order (order_id, user_id, status) SELECT order_id, user_id, status FROM t_order WHERE order_id = 1;|INSERT INTO t_order (order_id , user_id , status) <br>SELECT order_id , user_id , status <br>FROM t_order<br>WHERE <br>    order_id = 1;|
diff --git a/docs/document/content/reference/test/module-test/parser-test.en.md b/docs/document/content/reference/test/module-test/parser-test.en.md
index df908f9a5f9..f53fdae2d5f 100644
--- a/docs/document/content/reference/test/module-test/parser-test.en.md
+++ b/docs/document/content/reference/test/module-test/parser-test.en.md
@@ -9,7 +9,7 @@ Not like Integration test, SQL parse test does not need a specific database envi
### SQL Data
-As mentioned `sql-case-id` in Integration test，test-case-id could be shared in different module to test, and the file is at `shardingsphere-sql-parser/shardingsphere-sql-parser-test/src/main/resources/sql/supported/${SQL-TYPE}/*.xml`
+As mentioned `sql-case-id` in Integration test, test-case-id could be shared in different module to test, and the file is at `shardingsphere-sql-parser/shardingsphere-sql-parser-test/src/main/resources/sql/supported/${SQL-TYPE}/*.xml`
### Assert Data
diff --git a/docs/document/content/reference/test/module-test/rewrite-test.en.md b/docs/document/content/reference/test/module-test/rewrite-test.en.md
index bc1cb25e9ad..b84dcad3185 100644
--- a/docs/document/content/reference/test/module-test/rewrite-test.en.md
+++ b/docs/document/content/reference/test/module-test/rewrite-test.en.md
@@ -17,7 +17,7 @@ The rewrite tests are in the test folder under `sharding-core/sharding-core-rewr
Test engine is the entrance of rewrite tests, just like other test engines, through Junit [Parameterized](https://github.com/junit-team/junit4/wiki/Parameterized-tests), read every and each data in the xml file under the target test type in `test\resources`, and then assert by the engine one by one
-Environment configuration is the yaml file under test type under `test\resources\yaml`. The configuration file contains dataSources，shardingRule，encryptRule and other info. for example:
+Environment configuration is the yaml file under test type under `test\resources\yaml`. The configuration file contains dataSources, shardingRule, encryptRule and other info. for example:
```yaml
dataSources:
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/builtin-algorithm/shadow.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/builtin-algorithm/shadow.en.md
index df7039b8e50..ff233c2d615 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/builtin-algorithm/shadow.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/builtin-algorithm/shadow.en.md
@@ -14,7 +14,7 @@ Attributes:
| *Name* | *DataType* | *Description* |
| -------------- | --------- | ------- |
| column | String | Shadow column |
-| operation | String | SQL operation type（INSERT, UPDATE, DELETE, SELECT） |
+| operation | String | SQL operation type (INSERT, UPDATE, DELETE, SELECT) |
| value | String | Shadow column matching value |
### Column Regex Match Shadow Algorithm
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/java-api/rules/ha.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/java-api/rules/ha.en.md
index 8336c808279..f0b8dacd931 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/java-api/rules/ha.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/java-api/rules/ha.en.md
@@ -46,5 +46,5 @@ Attributes：
| *Name* | *DataType* | *Description* | *Default Value* |
| -------------------------- | ---------------------- | ------------------------------------------------------------------------------- | ------------- |
-| type (+) | String | Database discovery type, such as: MGR、openGauss | - |
+| type (+) | String | Database discovery type, such as: MGR, openGauss | - |
| props (?) | Properties | Required parameters for high-availability types, such as MGR's group-name | - |
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/java-api/rules/readwrite-splitting.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/java-api/rules/readwrite-splitting.en.md
index b783fe73b52..1988dda82a3 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/java-api/rules/readwrite-splitting.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/java-api/rules/readwrite-splitting.en.md
@@ -23,8 +23,8 @@ Attributes:
| *Name* | *DataType* | *Description* | *Default Value* |
| -------------------------- | -------------------- | -------------------------------------------------- | ---------------------------------- |
| name | String | Readwrite-splitting data source name | - |
-| type | String | Readwrite-splitting type, such as: Static、Dynamic | - |
-| props | Properties | Readwrite-splitting required properties. Static: write-data-source-name、read-data-source-names, Dynamic: auto-aware-data-source-name| - |
+| type | String | Readwrite-splitting type, such as: Static, Dynamic | - |
+| props | Properties | Readwrite-splitting required properties. Static: write-data-source-name, read-data-source-names, Dynamic: auto-aware-data-source-name| - |
| loadBalancerName (?) | String | Load balance algorithm name of replica sources | Round robin load balance algorithm |
Please refer to [Built-in Load Balance Algorithm List](/en/user-manual/shardingsphere-jdbc/builtin-algorithm/load-balance) for more details about type of algorithm.
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/special-api/observability/agent.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/special-api/observability/agent.en.md
index 752626832c3..28731cd2144 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/special-api/observability/agent.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/special-api/observability/agent.en.md
@@ -12,7 +12,7 @@ weight = 1
> mvn clean install
```
-### Download（Not Released Yet）
+### Download (Not Released Yet)
```
> weget http://xxxxx/shardingsphere-agent.tar.gz
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/spring-boot-starter/rules/ha.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/spring-boot-starter/rules/ha.en.md
index 47045bbe228..86410d4861a 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/spring-boot-starter/rules/ha.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/spring-boot-starter/rules/ha.en.md
@@ -14,7 +14,7 @@ spring.shardingsphere.rules.database-discovery.data-sources.<database-discovery-
spring.shardingsphere.rules.database-discovery.discovery-heartbeats.<discovery-heartbeat-name>.props.keep-alive-cron= # This is cron expression, such as：'0/5 * * * * ?'
-spring.shardingsphere.rules.database-discovery.discovery-types.<discovery-type-name>.type= # Database discovery type, such as: MGR、openGauss
+spring.shardingsphere.rules.database-discovery.discovery-types.<discovery-type-name>.type= # Database discovery type, such as: MGR, openGauss
spring.shardingsphere.rules.database-discovery.discovery-types.<discovery-type-name>.props.group-name= # Required parameters for database discovery types, such as MGR's group-name
-```
\ No newline at end of file
+```
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/spring-boot-starter/rules/shadow.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/spring-boot-starter/rules/shadow.en.md
index d4be7890587..8529e0bd2da 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/spring-boot-starter/rules/shadow.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/spring-boot-starter/rules/shadow.en.md
@@ -14,7 +14,7 @@ spring.shardingsphere.rules.shadow.data-sources.shadow-data-source.shadow-data-s
spring.shardingsphere.rules.shadow.tables.<table-name>.data-source-names= # Shadow table location shadow data source names (multiple values are separated by ",")
spring.shardingsphere.rules.shadow.tables.<table-name>.shadow-algorithm-names= # Shadow table location shadow algorithm names (multiple values are separated by ",")
-spring.shardingsphere.rules.shadow.defaultShadowAlgorithmName= # Default shadow algorithm name，optional item.
+spring.shardingsphere.rules.shadow.defaultShadowAlgorithmName= # Default shadow algorithm name, optional item.
spring.shardingsphere.rules.shadow.shadow-algorithms.<shadow-algorithm-name>.type= # Shadow algorithm type
spring.shardingsphere.rules.shadow.shadow-algorithms.<shadow-algorithm-name>.props.xxx= # Shadow algorithm property configuration
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/spring-namespace/rules/ha.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/spring-namespace/rules/ha.en.md
index af2a755ef9c..1a20f211c9d 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/spring-namespace/rules/ha.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/spring-namespace/rules/ha.en.md
@@ -36,5 +36,5 @@ Namespace：[http://shardingsphere.apache.org/schema/shardingsphere/database-dis
| *Name* | *Type* | *Description* |
| --------- | ---------- | ---------------------------------------------------------------- |
| id | Attribute | Database discovery type Id |
-| type | Attribute | Database discovery type, such as: MGR、openGauss |
+| type | Attribute | Database discovery type, such as: MGR, openGauss |
| props (?) | tag | Required parameters for database discovery types, such as MGR's group-name |
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/spring-namespace/rules/readwrite-splitting.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/spring-namespace/rules/readwrite-splitting.en.md
index aae830da12e..026879bb396 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/spring-namespace/rules/readwrite-splitting.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/spring-namespace/rules/readwrite-splitting.en.md
@@ -19,8 +19,8 @@ Namespace: [http://shardingsphere.apache.org/schema/shardingsphere/readwrite-spl
| *Name* | *Type* | *Description* |
| -------------------------- | ---------- | ----------------------------------------------------------------------- |
| id | Attribute | Readwrite-splitting data source rule name |
-| type | Attribute | Readwrite-splitting type, such as: Static、Dynamic |
-| props | Tag | Readwrite-splitting required properties. Static: write-data-source-name、read-data-source-names, Dynamic: auto-aware-data-source-name |
+| type | Attribute | Readwrite-splitting type, such as: Static, Dynamic |
+| props | Tag | Readwrite-splitting required properties. Static: write-data-source-name, read-data-source-names, Dynamic: auto-aware-data-source-name |
| load-balance-algorithm-ref | Attribute | Load balance algorithm name |
\<readwrite-splitting:load-balance-algorithm />
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/ha.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/ha.en.md
index a81b4b891f6..61dd3248cfa 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/ha.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/ha.en.md
@@ -23,7 +23,7 @@ rules:
# Database Discovery Configuration
discoveryTypes:
<discovery-type-name> (+): # Database discovery type name
- type: # Database discovery type, such as: MGR、openGauss
+ type: # Database discovery type, such as: MGR, openGauss
props (?):
group-name: 92504d5b-6dec-11e8-91ea-246e9612aaf1 # Required parameters for database discovery types, such as MGR's group-name
```
diff --git a/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/ral/_index.en.md b/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/ral/_index.en.md
index fbc3e6dae6c..5a03cbe9153 100644
--- a/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/ral/_index.en.md
+++ b/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/ral/_index.en.md
@@ -51,7 +51,7 @@ RAL (Resource & Rule Administration Language) responsible for the added-on featu
| SHOW AUTHORITY RULE | Query authority rule configuration | SHOW AUTHORITY RULE [...]
| SHOW TRANSACTION RULE | Query transaction rule configuration | SHOW TRANSACTION RULE [...]
| SHOW SQL_PARSER RULE | Query SQL parser rule configuration | SHOW SQL_PARSER RULE [...]
-| ALTER TRANSACTION RULE(DEFAULT=xx,TYPE(NAME=xxx, PROPERTIES("key1"="value1","key2"="value2"...))) | Alter transaction rule configuration，`DEFAULT`: default transaction type，support LOCAL、XA、BASE; `NAME`: name of transaction manager, support Atomikos, Narayana and Bitronix | ALTER TRANSACTION RULE(DEFAULT=XA,TYPE(NAME=Narayana, PROPERTIES [...]
+| ALTER TRANSACTION RULE(DEFAULT=xx,TYPE(NAME=xxx, PROPERTIES("key1"="value1","key2"="value2"...))) | Alter transaction rule configuration, `DEFAULT`: default transaction type, support LOCAL, XA, BASE; `NAME`: name of transaction manager, support Atomikos, Narayana and Bitronix | ALTER TRANSACTION RULE(DEFAULT=XA,TYPE(NAME=Narayana, PROPER [...]
| ALTER SQL_PARSER RULE SQL_COMMENT_PARSE_ENABLE=xx, PARSE_TREE_CACHE(INITIAL_CAPACITY=xx, MAXIMUM_SIZE=xx, CONCURRENCY_LEVEL=xx), SQL_STATEMENT_CACHE(INITIAL_CAPACITY=xxx, MAXIMUM_SIZE=xxx, CONCURRENCY_LEVEL=xxx) | Alter SQL parser rule configuration, `SQL_COMMENT_PARSE_ENABLE`: whether to parse the SQL comment, `PARSE_TREE_CACHE`: local cache configuration of syntax tree, `SQL_STATEMENT_CACHE`: local cache of SQL statement | ALTER SQL_PARSER RULE SQL_COMMENT_PARSE_ENABLE=false, PARSE_T [...]
## Other
diff --git a/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/rdl/rule-definition/sharding.en.md b/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/rdl/rule-definition/sharding.en.md
index e7e586b0e1d..aa5dcc63a30 100644
--- a/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/rdl/rule-definition/sharding.en.md
+++ b/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/rdl/rule-definition/sharding.en.md
@@ -110,7 +110,7 @@ keyGeneratorDefinition:
- Duplicate `tableName` will not be created
- `shardingAlgorithm` can be reused by different `Sharding Table Rule`, so when executing `DROP SHARDING TABLE RULE`, the corresponding `shardingAlgorithm` will not be removed
- To remove `shardingAlgorithm`, please execute `DROP SHARDING ALGORITHM`
-- `strategyType` specifies the sharding strategy，please refer to[Sharding Strategy](/en/features/sharding/concept/sharding/#sharding-strategy)
+- `strategyType` specifies the sharding strategy, please refer to[Sharding Strategy](/en/features/sharding/concept/sharding/#sharding-strategy)
- `Sharding Table Rule` supports both `Auto Table` and `Table` at the same time. The two types are different in syntax. For the corresponding configuration file, please refer to [Sharding](/en/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/)
- When using the `autoCreativeAlgorithm` way to specify `shardingStrategy`, a new sharding algorithm will be created automatically. The algorithm naming rule is `tableName_strategyType_shardingAlgorithmType`, such as `t_order_database_inline`
diff --git a/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/rql/rule-query/readwrite-splitting.en.md b/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/rql/rule-query/readwrite-splitting.en.md
index 5767fb4ed63..19233f45c14 100644
--- a/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/rql/rule-query/readwrite-splitting.en.md
+++ b/docs/document/content/user-manual/shardingsphere-proxy/distsql/syntax/rql/rule-query/readwrite-splitting.en.md
@@ -14,7 +14,7 @@ SHOW READWRITE_SPLITTING RULES [FROM schemaName]
| Column | Description |
| --------------------------- | ------------------------------------ |
| name | Rule name |
-| auto_aware_data_source_name | Auto-Aware discovery data source name（Display configuration dynamic readwrite splitting rules）|
+| auto_aware_data_source_name | Auto-Aware discovery data source name (Display configuration dynamic readwrite splitting rules) |
| write_data_source_name | Write data source name |
| read_data_source_names | Read data source name list |
| load_balancer_type | Load balance algorithm type |
diff --git a/docs/document/content/user-manual/shardingsphere-scaling/usage.en.md b/docs/document/content/user-manual/shardingsphere-scaling/usage.en.md
index 5a409468e8d..5b125e09487 100644
--- a/docs/document/content/user-manual/shardingsphere-scaling/usage.en.md
+++ b/docs/document/content/user-manual/shardingsphere-scaling/usage.en.md
@@ -7,7 +7,7 @@ weight = 2
### Environment
-JAVA，JDK 1.8+.
+JAVA, JDK 1.8+.
The migration scene we support: