You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by yy...@apache.org on 2022/12/02 09:26:27 UTC

[shardingsphere] branch yy2so-patch-2 created (now 3ee8f5d538a)

This is an automated email from the ASF dual-hosted git repository.

yy2so pushed a change to branch yy2so-patch-2
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git


      at 3ee8f5d538a Update usage.en.md

This branch includes the following new commits:

     new 3ee8f5d538a Update usage.en.md

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



[shardingsphere] 01/01: Update usage.en.md

Posted by yy...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

yy2so pushed a commit to branch yy2so-patch-2
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git

commit 3ee8f5d538a03bd5d293394570ad6192c6a05a5d
Author: Yacine Si Tayeb <86...@users.noreply.github.com>
AuthorDate: Fri Dec 2 17:26:20 2022 +0800

    Update usage.en.md
---
 .../user-manual/shardingsphere-proxy/migration/usage.en.md   | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/document/content/user-manual/shardingsphere-proxy/migration/usage.en.md b/docs/document/content/user-manual/shardingsphere-proxy/migration/usage.en.md
index 31e1bbdd63d..43c3988e043 100644
--- a/docs/document/content/user-manual/shardingsphere-proxy/migration/usage.en.md
+++ b/docs/document/content/user-manual/shardingsphere-proxy/migration/usage.en.md
@@ -43,7 +43,7 @@ If the following information is displayed, binlog is enabled.
 
 2. Grant Replication-related permissions for MySQL account.
 
-Run the following command and see whether the user has migration permission.
+Run the following command to check whether the user has migration permission.
 ```
 SHOW GRANTS FOR 'migration_user';
 ```
@@ -70,7 +70,7 @@ Please refer to [MySQL GRANT](https://dev.mysql.com/doc/refman/8.0/en/grant.html
 
 ### Complete procedure example
 
-#### Prerequisite
+#### Requirements
 
 1. Prepare the source database, table, and data in MySQL.
 
@@ -281,7 +281,7 @@ If you are using a non-super admin account for migration, you need to GRANT CREA
 GRANT CREATE, CONNECT ON DATABASE migration_ds_0 TO migration_user;
 ```
 
-The account also need to have access to the migrated tables and schema, take the t_order table under test schema as an example. 
+The account also needs to have access to the migrated tables and schema. Take the t_order table under test schema as an example. 
 
 ```sql
 \c migration_ds_0
@@ -296,7 +296,7 @@ Please refer to [PostgreSQL GRANT](https://www.postgresql.org/docs/current/sql-g
 
 ### Complete procedure example
 
-#### Prerequisite
+#### Requirements
 
 1. Prepare the source database, table, and data in PostgreSQL.
 
@@ -492,7 +492,7 @@ If you are using a non-super admin account for migration, you need to GRANT CREA
 GRANT CREATE, CONNECT ON DATABASE migration_ds_0 TO migration_user;
 ```
 
-The account also need to have access to the migrated tables and schema, take the t_order table under test schema as an example. 
+The account also needs to have access to the migrated tables and schema. Take the t_order table under test schema as an example. 
 
 ```sql
 \c migration_ds_0
@@ -513,7 +513,7 @@ GRANT ALL PRIVILEGES TO migration_user;
 
 ### Complete procedure example
 
-#### Prerequisite
+#### Requirements
 
 1. Prepare the source database, table, and data in openGauss.