doc: polish release doc

CONTRIBUTING.md

@@ -96,6 +96,31 @@ Some components may require specific setup steps. Please refer to their respecti
 - [Node.js Binding](bindings/nodejs/CONTRIBUTING.md)
 - [Python Binding](bindings/python/CONTRIBUTING.md)
 
+## Build from source
+
+OpenDAL uses [Cargo](https://doc.rust-lang.org/cargo/) as its build system. 
+To build OpenDAL, run the following command under OpenDAL's root directory:
+
+Only build the core component:
+
+```shell
+cargo build
+```
+
+With full features enabled:
+
+```shell
+cargo build --all-features
+```
+
+Build all components:
+
+```shell
+cargo build --all
+```
+
+For building every component, you can refer to each component's `CONTRIBUTING` documentation for more details.
+
 ## Code of Conduct
 
 We expect all community members to follow our [Code of Conduct](https://www.apache.org/foundation/policies/conduct.html).

website/docs/contributing/reference/generate_release_note.md

@@ -2,7 +2,7 @@
 title: Generate Release Note
 ---
 
-This document describes how to generate release notes using Github:
+This document describes how to generate release notes using GitHub:
 
 1. Go to https://github.com/apache/incubator-opendal/releases/new to start a new release.
 2. Fill the tag with `draft`.

website/docs/contributing/reference/setup_gpg.md

@@ -4,15 +4,15 @@ title: Setup GPG Key
 
 > This section is a brief from the [Cryptography with OpenPGP](https://infra.apache.org/openpgp.html) guideline.
 
-## Install gpg
+## Install GPG
 
 For more details, please refer to [GPG official website](https://www.gnupg.org/download/index.html). Here shows one approach to install GPG with `apt`:
 
 ```shell
 sudo apt install gnupg2
 ```
 
-## Generate gpg Key
+## Generate GPG Key
 
 Attentions:
 
@@ -73,7 +73,7 @@ generator a better chance to gain enough entropy.
 │                                                      │
 │       <OK>                              <Cancel>     │
 └──────────────────────────────────────────────────────┘
-# key generatio[n will be done after your inputting the key with the following output
+# key generation will be done after your inputting the key with the following output
 gpg: key E49B00F626B marked as ultimately trusted
 gpg: revocation certificate stored as '/Users/hulk/.gnupg/openpgp-revocs.d/F77B887A4F25A9468C513E9AA3008E49B00F626B.rev'
 public and secret key created and signed.
@@ -84,7 +84,7 @@ uid           [ultimate] hulk <[email protected]>
 sub   rsa4096 2022-07-12 [E]
 ```
 
-## Upload your key to public gpg keyserver
+## Upload your key to public GPG keyserver
 
 Firstly, list your key:
 
@@ -112,15 +112,15 @@ Among them, `keys.openpgp.org` is a randomly selected keyserver, you can use `ke
 
 ## Check whether the key is created successfully
 
-Uploading takes about one minute, after that, you can check by your email at the corresponding keyserver.
+Uploading takes about one minute; after that, you can check by your email at the corresponding keyserver.
 
 Uploading keys to the keyserver is mainly for joining a [Web of Trust](https://infra.apache.org/release-signing.html#web-of-trust).
 
-## Add your gpg public key to the KEYS document
+## Add your GPG public key to the KEYS document
 
 :::info
 
-SVN is required for this step.
+`SVN` is required for this step.
 
 :::
 
@@ -139,5 +139,5 @@ svn ci -m "add gpg key for YOUR_NAME" # Later on, if you are asked to enter a us
 
 ## Upload the GPG public key to your GitHub account
 
-- Enter https://github.com/settings/keys to add GPG KEYS.
+- Enter https://github.com/settings/keys to add your GPG key.
 - Please remember to bind the email address used in the GPG key to your GitHub account (https://github.com/settings/emails) if you find "unverified" after adding it.

website/docs/contributing/release.md

@@ -3,13 +3,16 @@ title: Release
 sidebar_position: 1
 ---
 
-This document mainly introduces how the Release Manager releases a new version in accordance with the Apache requirements.
+This document mainly introduces
+how the release manager releases a new version in accordance with the Apache requirements.
 
 ## Introduction
 
-Source Release is the key point which Apache values, also, is necessary for a release. And OpenDAL will only have source release.
+`Source Release` is the key point which Apache values, also, is necessary for a release. And OpenDAL will only have source release.
 
-Please remember that publishing software has legal consequences. This guide complements the foundation-wide policies and guides:
+Please remember that publishing software has legal consequences. 
+
+This guide complements the foundation-wide policies and guides:
 
 - [Release Policy](https://www.apache.org/legal/release-policy.html)
 - [Release Distribution Policy](https://infra.apache.org/release-distribution)
@@ -19,47 +22,49 @@ Please remember that publishing software has legal consequences. This guide comp
 
 :::caution
 
-This section is the requirements for release manager who is the first time to be a release manager
+This section is the requirements for the release manager who is the first time to be a release manager
 
 :::
 
-Refer to [Setup GPG Key](reference/setup_gpg.md) to make sure GPG key has been setup.
+Refer to [Setup GPG Key](reference/setup_gpg.md) to make sure the GPG key has been set up.
 
-## Github Release
+## GitHub Release
 
 ### Bump Version
 
-OpenDAL will release all package in the same version.
+OpenDAL will release all packages in the same version.
 
-- Bump version in `Cargo.toml`
-- For nodejs binding, bump version in `bindings/nodejs/npm/*/package.json`
-- For java binding, bump version in `bindings/java/pom.xml`
+- Bump version in `Cargo.toml`.
+- For the nodejs binding, bump version in `bindings/nodejs/package.json`, then use the command `napi version` in `bindings/nodejs` to bump all sub-packages' version.
+- For th java binding, bump version in `bindings/java/pom.xml`.
 - Update `CHANGELOG.md`, refer to [Generate Release Note](reference/generate_release_note.md) for more information.
-- If there are breaking changes in `core`, please also update `core/src/docs/upgrade.md`
-- After all those changes, submit a PR with name `Bump to version x.y.z`
+- If there are breaking changes in `core`, please also update `core/src/docs/upgrade.md`.
+- After all those changes, submit a PR with name `Bump to version x.y.z`.
 
-Take [Bump to version 0.36.1](https://github.com/apache/incubator-opendal/pull/2401) as an example.
+Take [Bump to version 0.36.0](https://github.com/apache/incubator-opendal/pull/2366) as an example.
 
-### Create Github Release
+### Create a GitHub Release
 
-After bump version PR get merged, we can create a github release:
+After bump version PR gets merged, we can create a GitHub release:
 
-- Create a tag at `main` branch on the `Bump Version` commit: `git tag -s "v0.36.1"`
-- Push tags to Github: `git push --tags`.
+- Create a tag at `main` branch on the `Bump Version` commit: `git tag -s "v0.36.0"`
+- Push tags to GitHub: `git push --tags`.
 - Create Release on the newly created tag
   - If there are breaking changes, please add the content from `upgrade.md` before.
 
 ## ASF Release
 
-If any step in the ASF Release process fails and requires code changes, we will abandon that version and prepare for the next one. Our release page will only display ASF releases instead of Github Releases.
+If any step in the ASF Release process fails and requires code changes,
+we will abandon that version and prepare for the next one.
+Our release page will only display ASF releases instead of GitHub Releases.
 
-### Create ASF Release
+### Create an ASF Release
 
-After Github Release has been created, we can start to create ASF Release.
+After GitHub Release has been created, we can start to create ASF Release.
 
 - Checkout to released tag.
-- Use release script to create a new release: `OPENDAL_VERSION=<version> OPENDAL_VERSION_RC=<rc_version> ./scripts/release.sh`
-- Push the newly created branch to github
+- Use the release script to create a new release: `OPENDAL_VERSION=<version> OPENDAL_VERSION_RC=<rc_version> ./scripts/release.sh`
+- Push the newly created branch to GitHub
 
 This script will create a new release under `dist`.
 
@@ -73,7 +78,7 @@ dist
 └── apache-opendal-incubating-0.36.0-src.tar.gz.sha512
 ```
 
-### Upload artifacts to SVN dist repo
+### Upload artifacts to the SVN dist repo
 
 :::info
 
@@ -110,7 +115,7 @@ svn status
 svn commit -m "Prepare for ${release_version}"
 ```
 
-Visit <https://dist.apache.org/repos/dist/dev/incubator/opendal/> to make sure the artifacts is uploaded correctly.
+Visit <https://dist.apache.org/repos/dist/dev/incubator/opendal/> to make sure the artifacts are uploaded correctly.
 
 ## Voting
 
@@ -279,7 +284,7 @@ More detailed checklist please refer to:
 https://github.com/apache/incubator-opendal/tree/main/scripts
 
 To compile from source, please refer to:
-https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
+https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md#build-from-source
 
 Thanks