diff --git a/website/blog/2024-01-22-apache-opendal-graduated/index.md b/website/blog/2024-01-22-apache-opendal-graduated/index.md index 1c78cfc87ed..57d4df193a0 100644 --- a/website/blog/2024-01-22-apache-opendal-graduated/index.md +++ b/website/blog/2024-01-22-apache-opendal-graduated/index.md @@ -115,7 +115,7 @@ We plan to: ### More Useful Documents -OpenDAL have good docs for it's rust core, but not for other language bindings. +OpenDAL have good docs for its rust core, but not for other language bindings. The lack of comprehensive documentation makes OpenDAL challenging for users to operate in Java or Python. Without user feedback, the community is unable to enhance this documentation, leading to a detrimental cycle that must be broken. @@ -126,7 +126,7 @@ We plan to: - Introduce code generation to automatically create documentation for the service builder due to its numerous configurations. - Add more API Docs and examples for other language bindings. -OpenDAL have good docs for it's public API, but not for its internal design. +OpenDAL have good docs for its public API, but not for its internal design. OpenDAL is proud of its elegant design, but it is not well documented. This makes it difficult for new contributors to understand the codebase and make contributions. diff --git a/website/community/committers/release.md b/website/community/committers/release.md index 591b6e9a28e..494ae41ed67 100644 --- a/website/community/committers/release.md +++ b/website/community/committers/release.md @@ -466,7 +466,7 @@ For non-Java bindings, if we can not find the latest version of artifacts in the Send the release announcement to `dev@opendal.apache.org` and CC `announce@apache.org`. -> Tips: Please following the [Committer Email](https://infra.apache.org/committer-email.html) guide to make sure you have already set up the email SMTP. Otherwise, your email cannot be sent to the announce mailing list. +> Tips: Please following the [Committer Email](https://infra.apache.org/committer-email.html) guide to make sure you have already set up the email SMTP. Otherwise, your email cannot be sent to the announcement mailing list. Instead of adding breaking changes, let's include the new features as "notable changes" in the announcement. diff --git a/website/community/pmc_members/podling-report.md b/website/community/pmc_members/podling-report.md index f06624973e5..8a37974da6a 100644 --- a/website/community/pmc_members/podling-report.md +++ b/website/community/pmc_members/podling-report.md @@ -37,7 +37,7 @@ Note that IPMC update the template from time to time, so be sure to use the one Each Podling Status Report must be signed off by a mentor. **Without a mentor's sign-off, the IPMC will not accept the report**, and the podling will need to submit a new report the following month. -After submitting the report, you can send a email to dev@opendal.apache.org to remind our mentors and the community to review the report and provide feedback. +After submitting the report, you can email dev@opendal.apache.org to remind our mentors and the community to review the report and provide feedback. ``` [ANNOUNCE] OpenDAL's Podling Report of diff --git a/website/docs/overview.md b/website/docs/overview.md index fe999b85d4c..76e271020fa 100644 --- a/website/docs/overview.md +++ b/website/docs/overview.md @@ -61,7 +61,7 @@ For example, we DO OpenDAL needs to implement features in a zero cost way which means: -- Users need not to pay cost for unused features. +- Users don't need to pay costs for unused features. - Users cannot write better implementation for used features. For example, we DO