diff --git a/website/docs/vision.md b/website/docs/vision.md
index 17704015b33b..28666bb3bdc8 100644
--- a/website/docs/vision.md
+++ b/website/docs/vision.md
@@ -15,13 +15,14 @@ OpenDAL must enable users to access various storage services ranging from `s3` t
 
 ### Examples
 
-- Add support for [Google Drive](https://www.google.com/drive/): Good, it allows users to access and manage their data on the [Google Drive](https://www.google.com/drive/).
-- Add support for [Object Storage Service (OSS)](https://www.alibabacloud.com/product/object-storage-service) via native API: Good, users can utilize Aliyun's RAM support.
-- Add support for [supabase storage](https://supabase.com/docs/guides/storage): Good, users can visit `supabase storage` now!
+We
+- Add support for [Google Drive](https://www.google.com/drive/): It allows users to access and manage their data on the [Google Drive](https://www.google.com/drive/).
+- Add support for [Object Storage Service (OSS)](https://www.alibabacloud.com/product/object-storage-service) via native API: Users can utilize Aliyun's RAM support.
+- Add support for [supabase storage](https://supabase.com/docs/guides/storage): Users can visit `supabase storage` now!
 
-
-- Add support for [Google Cloud Storage(GCS)](https://cloud.google.com/storage) via [XML API](https://cloud.google.com/storage/docs/xml-api/overview): Bad, [GCS](https://cloud.google.com/storage) has native [JSON API](https://cloud.google.com/storage/docs/json_api) which more powerful
-- Add support for `MySQL/PostgreSQL`: Bad, relational DBMS provides data types such as BLOB, but they are often not used as a storage service.
+We don't
+- Add support for [Google Cloud Storage(GCS)](https://cloud.google.com/storage) via [XML API](https://cloud.google.com/storage/docs/xml-api/overview): [GCS](https://cloud.google.com/storage) has native [JSON API](https://cloud.google.com/storage/docs/json_api) which more powerful
+- Add support for `MySQL/PostgreSQL`: Relational DBMS provides data types such as BLOB, but they are often not used as a storage service.
 
 ## 2. Free from implementations
 
@@ -29,12 +30,13 @@ OpenDAL needs to separate the various implementation details of services and ena
 
 ### Examples
 
-- Add a new capability to indicate whether `presign` is supported: Good, users can now write logic based on the `can_presign` option.
-- Add a `default_storage_class` configuration for the S3 service: Good, configuration is specific to the S3 service.
-- Add an option for `content_type` in the `write` operation: Good, it aligns with HTTP standards.
-
+We
+- Add a new capability to indicate whether `presign` is supported: Users can now write logic based on the `can_presign` option.
+- Add a `default_storage_class` configuration for the S3 service: Configuration is specific to the S3 service.
+- Add an option for `content_type` in the `write` operation: It aligns with HTTP standards.
 
-- Add a new option in read for `storage_class`: Bad, as different services could have varying values for this parameter.
+We don't
+- Add a new option in read for `storage_class`: As different services could have varying values for this parameter.
 
 ## 3. Free to integrate
 
@@ -42,8 +44,9 @@ OpenDAL needs to be integrated with different systems.
 
 ### Examples
 
-- Add python binding: Good, users from `python` can use OpenDAL.
-- Add object_store integration: Good, users of `object_store` can adopt OpenDAL.
+We
+- Add python binding: users from `python` can use OpenDAL.
+- Add object_store integration: users of `object_store` can adopt OpenDAL.
 
 ## 4. Free to zero cost
 
@@ -54,8 +57,9 @@ OpenDAL needs to implement features in zero cost way which means:
 
 ### Examples
 
-- Add `layer` support: Good, users can add logging/metrics/tracing in zero cost way.
-- Implement `seek` for Reader: Good, users can't write better `seek` support, they all need to pay the same cost.
-
+We
+- Add `layer` support: Users can add logging/metrics/tracing in zero cost way.
+- Implement `seek` for Reader: Users can't write better `seek` support, they all need to pay the same cost.
 
-- Add `Arc` for metadata: Bad, users may only need to use metadata once and never clone it. For those who do want this feature, they can add `Arc` themselves.
+We don't
+- Add `Arc` for metadata: Users may only need to use metadata once and never clone it. For those who do want this feature, they can add `Arc` themselves.