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 f98cd4c9b3b Update README.md (#22163)
f98cd4c9b3b is described below

commit f98cd4c9b3b54b5af999f6b5475a3418362a21de
Author: Yacine Si Tayeb <[email protected]>
AuthorDate: Mon Nov 14 20:26:08 2022 +0800

    Update README.md (#22163)
---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index fd2c4a85224..793f10d59f6 100644
--- a/README.md
+++ b/README.md
@@ -174,11 +174,11 @@ Through the mixed use of ShardingSphere-JDBC & 
ShardingSphere-Proxy together wit
 
 | *Solutions/Features* |  *Distributed Database* | *Data Security*      | 
*Database Gateway*                | *Stress Testing* |
 | -------------------- | ----------------------- | ---------------------| 
--------------------------------- | ---------------- |
-|                      | Data Sharding           | Data Encrypt         | 
Heterogeneous Databases Supported | Shadow Database  |
-|                      | Readwrite-splitting     | Row Authority (TODO) | SQL 
Dialect Translate (TODO)      | Observability    |
+|                      | Data Sharding           | Data Encryption         | 
Heterogeneous Databases Supported | Shadow Database  |
+|                      | Read/write Splitting     | Row Authority (TODO) | SQL 
Dialect Translate (TODO)      | Observability    |
 |                      | Distributed Transaction | SQL Audit (TODO)     |      
                             |                  |
 |                      | Elastic Scale-out       | SQL Firewall (TODO)  |      
                             |                  |
-|                      | Highly Available        |                      |      
                             |                  |
+|                      | High Availability       |                      |      
                             |                  |
 
 ##
 

Reply via email to