apache · tisonkun · Jan 16, 2024 · Jan 16, 2024
@@ -1,9 +1,9 @@
 ---
-title: "Apache OpenDAL(Incubating): Access Data Freely"
+title: "Apache OpenDAL™: Access Data Freely"
 date: 2023-07-07
 slug: opendal-access-data-freely
 tags: [announcement]
-description: "If you're committed to building cloud-native, cross-cloud-first applications and services, or you want to support configurable storage backends to meet complex data access needs, or if you're tired of juggling various SDKs and hoping for a unified abstraction and development experience, Apache OpenDAL (Incubating) will be your perfect partner."
+description: "If you're committed to building cloud-native, cross-cloud-first applications and services, or you want to support configurable storage backends to meet complex data access needs, or if you're tired of juggling various SDKs and hoping for a unified abstraction and development experience, Apache OpenDAL™ will be your perfect partner."
 authors:
   - name: PsiACE
     url: https://github.com/PsiACE
@@ -13,7 +13,7 @@ authors:
     image_url: https://github.com/Xuanwo.png
 ---
 
-If you're committed to building cloud-native, cross-cloud-first applications and services, or you want to support configurable storage backends to meet complex data access needs, or if you're tired of juggling various SDKs and hoping for a unified abstraction and development experience, Apache OpenDAL (Incubating) will be your perfect partner.
+If you're committed to building cloud-native, cross-cloud-first applications and services, or you want to support configurable storage backends to meet complex data access needs, or if you're tired of juggling various SDKs and hoping for a unified abstraction and development experience, Apache OpenDAL™ will be your perfect partner.
 
 ![OpenDAL Arch](opendal-arch.png)
 

@@ -1,5 +1,5 @@
 ---
-title: "OpenDAL Internal: Data Reading"
+title: "Apache OpenDAL™ Internal: Data Reading"
 date: 2023-08-15
 slug: how-opendal-read-data
 tags: [internal]
@@ -10,7 +10,7 @@ authors:
     image_url: https://github.com/Xuanwo.png
 ---
 
-As the OpenDAL community continues to grow, new abstractions are constantly being added, which has brought some burdens to new contributors participating in development. Many maintainers hope to have a deeper understanding of OpenDAL's internal implementation. At the same time, OpenDAL's core design has not changed significantly for a long time, making it possible to write a series on internal implementation. I believe now is the time to write a series of articles on OpenDAL's internal implementation, to explain from the maintainer's perspective how OpenDAL is designed, implemented, and how it can be expanded. With the impending release of OpenDAL v0.40, I hope this series of articles will better help the community understand the past, master the present, and shape the future.
+As the Apache OpenDAL™ community continues to grow, new abstractions are constantly being added, which has brought some burdens to new contributors participating in development. Many maintainers hope to have a deeper understanding of OpenDAL's internal implementation. At the same time, OpenDAL's core design has not changed significantly for a long time, making it possible to write a series on internal implementation. I believe now is the time to write a series of articles on OpenDAL's internal implementation, to explain from the maintainer's perspective how OpenDAL is designed, implemented, and how it can be expanded. With the impending release of OpenDAL v0.40, I hope this series of articles will better help the community understand the past, master the present, and shape the future.
 
 The first article will discuss OpenDAL's most commonly used data reading function. I will start from the outermost interface and then gradually unfold according to the calling sequence of OpenDAL. Let's get started!
 

@@ -9,7 +9,7 @@ authors:
     image_url: https://github.com/Xuanwo.png
 ---
 
-> OwO (Outcome, Working, Outlook) is our blog series where we share our current work status and future plans.
+> OwO (Outcome, Working, Outlook) is an Apache OpenDAL™ release blog series, where we share the current work status and future plans.
 
 Hello! It's been a while since our last update. We've been hard at work determining the optimal way to implement new features and improvements. We're thrilled to announce that we'll soon be releasing v0.40.
 
@@ -87,7 +87,7 @@ Other improvements in the core library can be found in our [CHANGELOG](https://g
 
 ### Bindings
 
-#### Cpp
+#### C++
 
 [`opendal-cpp`](https://github.com/apache/incubator-opendal/tree/main/bindings/cpp) is ready for its first release! Welcome to check it out and give us some feedback.
 

@@ -1,8 +1,10 @@
 ---
-title: Welcome to Apache OpenDAL™
+sidebar_label: About
 sidebar_position: 1
 ---
 
+# Welcome to Apache OpenDAL™
+
 OpenDAL represents **Open** **D**ata **A**ccess **L**ayer. Our vision is to **access data freely**.
 
 ## What does OpenDAL do?
@@ -29,7 +31,7 @@ For example, we DO
 
 while we DO NOT
 
-- 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 is more powerful
+- 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 is more powerful
 - Add support for structural data in `MySQL/PostgreSQL`: We can treat a database as a simple key-value store, but we can't support unified access of structural data.
 
 ### 2. Free from implementations