update readme

Author: Eikykun

README.md

@@ -5,25 +5,21 @@
 
 # Controller Mesh
 
-KusionStack Controller Mesh is a solution that helps developers manage their controllers/operators better.
+KusionStack Controller Mesh is a solution that helps developers managing their controllers/operators better.
 
 The design architecture of this project is based on [openkruise/controllermesh](https://github.com/openkruise/controllermesh).
 
 ## Key Features
 
 1. **Sharding**: Through relevant configurations, Kubernetes single-point deployed operator applications can be flexibly shard deployed.
-2. **Canary upgrade**: Depends on sharding, the controllers can be updated in canary progress instead of one time replace.
+2. **Canary upgrade**: Depends on sharding, the controller instances can be updated in canary progress instead of updated in one time.
 3. **Circuit breaker and rate limiter**: Not only Kubernetes operation requests, but also other external operation requests.
-4. **Multicluster routing and sharding**: This feature is supported by [kusionstack/kaera(karbour)]()
+4. **Multicluster routing and sharding**
+5. **And more**: Fault injection and Observability. (Todo)
 
 <p align="center"><img width="800" src="./docs/img/mesh-arch-2.png"/></p>
 
-## Quick Start
-Visit [Quick Start](docs/getting-started.md).
-
-
-## Installation
-Visit [Installation](docs/installation.md).
+Visit [Quick Start](docs/getting-started.md) or [Installation](docs/installation.md).
 ## Principles
 
 Generally, a `ctrlmesh-proxy` container will be injected into each operator Pod that has configured in ShardingConfigs.

docs/intro.md

@@ -2,15 +2,16 @@
 
 # Controller Mesh
 
-KusionStack Controller Mesh is a solution that helps developers manage their controllers/operators better.
+KusionStack Controller Mesh is a solution that helps developers managing their controllers/operators better.
 
 The design architecture of this project is based on [openkruise/controllermesh](https://github.com/openkruise/controllermesh).
 
 ## Key Features
 
 1. **Sharding**: Through relevant configurations, Kubernetes single-point deployed operator applications can be flexibly shard deployed.
-2. **Canary upgrade**: Depends on sharding, the controllers can be updated in canary progress instead of one time replace.
+2. **Canary upgrade**: Depends on sharding, the controller instances can be updated in canary progress instead of updated in one time.
 3. **Circuit breaker and rate limiter**: Not only Kubernetes operation requests, but also other external operation requests.
-4. **Multicluster routing and sharding**.
+4. **Multicluster routing and sharding**
+5. **And more**: Fault injection and Observability. (Todo)
 
 <p align="center"><img width="800" src="../docs/img/mesh-arch-2.png"/></p>