docs: improve documentation authenticity and readability (#5972)

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: chenjiahan <[email protected]>
Co-authored-by: neverland <[email protected]>

Author: Copilot

website/docs/en/api/start/index.mdx

@@ -1,6 +1,6 @@
 # JavaScript API
 
-Rsbuild provides a complete set of JavaScript APIs for developers to build higher level tools or frameworks on top of Rsbuild.
+Rsbuild provides a comprehensive JavaScript API for developers to build higher-level tools or frameworks on top of Rsbuild.
 
 Rsbuild's JavaScript API can be used in Node.js, Deno, or Bun.
 
@@ -30,30 +30,30 @@ The `createRsbuild` method provides some options, which you can learn more about
 
 ### 3. Call Rsbuild instance method
 
-The Rsbuild instance provides some methods, which you can use according to the usage scenarios.
+The Rsbuild instance provides several methods that you can use according to your scenario.
 
-To start local development, it is recommended to use the [rsbuild.startDevServer](/api/javascript-api/instance#rsbuildstartdevserver) method, which will start a local dev server.
+For local development, we recommend using the [rsbuild.startDevServer](/api/javascript-api/instance#rsbuildstartdevserver) method, which starts a local dev server.
 
 ```ts
 await rsbuild.startDevServer();
 ```
 
-After successfully starting dev server, you can see the following logs:
+After successfully starting the dev server, you will see the following logs:
 
 ```
   ➜ Local:    http://localhost:3000
   ➜ Network:  http://192.168.0.1:3000
 ```
 
-To deploy the App to production environment, it is recommended to use the [rsbuild.build](/api/javascript-api/instance#rsbuildbuild) method, which will build the production outputs.
+For production deployment, we recommend using the [rsbuild.build](/api/javascript-api/instance#rsbuildbuild) method, which builds the production outputs.
 
 ```ts
 await rsbuild.build();
 ```
 
 > For more introduction of Rsbuild instance methods, please read the [Rsbuild Instance](/api/javascript-api/instance) chapter.
 
-After completing the above three steps, you have learned the basic usage of Rsbuild. Next, you can customize the build process through Rsbuild plugins and configurations.
+After completing these three steps, you have learned the basic usage of Rsbuild. Next, you can customize the build process through Rsbuild plugins and configurations.
 
 ## Exports format
 
@@ -67,4 +67,4 @@ import { createRsbuild } from '@rsbuild/core';
 const { createRsbuild } = require('@rsbuild/core');
 ```
 
-> It is recommended to use ES modules format, which is more in line with the community standards.
+> We recommend using the ES modules format, which better aligns with community standards.

website/docs/en/config/environments.mdx

@@ -133,7 +133,7 @@ const nodeConfig = {
 
 ## Environment name
 
-Since environment names are used for directory names and object property names, it is recommended to only include letters, numbers, `-`, `_`, and `$`. When using other characters, Rsbuild will output a warning to prompt you.
+Since environment names are used for directory names and object property names, we recommend using only letters, numbers, `-`, `_`, and `$`. When using other characters, Rsbuild will display a warning.
 
 ```ts
 export default {

website/docs/en/config/output/asset-prefix.mdx

@@ -5,9 +5,9 @@
 
 In [production mode](/config/mode), use this option to set the URL prefix for static assets, such as setting it to a CDN URL.
 
-`assetPrefix` will affect the URLs of most of the static assets, including JavaScript files, CSS files, images, videos, etc. If an incorrect value is specified, you'll receive 404 errors while loading these resources.
+`assetPrefix` affects the URLs of most static assets, including JavaScript files, CSS files, images, videos, etc. If an incorrect value is specified, you'll receive 404 errors while loading these resources.
 
-This config is only used in `production` mode or `none` mode. In `development` mode, use the [dev.assetPrefix](/config/dev/asset-prefix) to set the URL prefix.
+This configuration is only used in `production` mode or `none` mode. In `development` mode, use the [dev.assetPrefix](/config/dev/asset-prefix) to set the URL prefix.
 
 ## Example
 

website/docs/en/config/output/clean-dist-path.mdx

@@ -8,14 +8,14 @@ type CleanDistPath = boolean | 'auto' | CleanDistPathObject;
 
 - **Default:** `'auto'`
 
-Whether to clean up all files in the output directory before the build starts. The output directory is the [output.distPath.root](/config/output/dist-path) directory.
+Configure whether to clean up all files in the output directory before the build starts. The output directory is the [output.distPath.root](/config/output/dist-path) directory.
 
 ## Default behavior
 
 The default value of `output.cleanDistPath` is `'auto'`:
 
 - In development mode, if [dev.writeToDisk](/config/dev/write-to-disk) is `false`, Rsbuild will not perform cleanup.
-- In any mode, if [output.distPath.root](/config/output/dist-path) is an external directory or equals to the project root directory, Rsbuild will not perform cleanup to avoid accidentally deleting files from other directories.
+- In any mode, if [output.distPath.root](/config/output/dist-path) is an external directory or equals the project root directory, Rsbuild will not perform cleanup to avoid accidentally deleting files from other directories.
 
 ```js
 export default {

website/docs/en/config/output/css-modules.mdx

@@ -2,13 +2,13 @@
 
 - **Type:** `CSSModules`
 
-For custom CSS Modules configuration.
+Configure custom CSS Modules settings.
 
-The CSS Modules feature of Rsbuild is based on the `modules` option of css-loader. You can refer to [css-loader - modules](https://github.com/webpack-contrib/css-loader?tab=readme-ov-file#modules) to learn more.
+The CSS Modules feature in Rsbuild is based on the `modules` option of css-loader. You can refer to [css-loader - modules](https://github.com/webpack-contrib/css-loader?tab=readme-ov-file#modules) to learn more.
 
 ## cssModules.auto
 
-The `auto` configuration option allows CSS Modules to be automatically enabled based on their filenames.
+The `auto` configuration option allows CSS Modules to be automatically enabled based on filenames.
 
 - **Type:**
 
@@ -27,7 +27,7 @@ type Auto =
 
 Type description:
 
-- `true`: enable CSS Modules for all files matching `/\.module\.\w+$/i.test(filename)` regexp.
+- `true`: enable CSS Modules for all files matching the `/\.module\.\w+$/i.test(filename)` regexp.
 - `false`: disable CSS Modules.
 - `RegExp`: enable CSS Modules for all files matching `/RegExp/i.test(filename)` regexp.
 - `function`: enable CSS Modules for files based on the filename satisfying your filter function check.

website/docs/en/config/output/dist-path.mdx

@@ -40,23 +40,23 @@ const defaultDistPath = {
 };
 ```
 
-Set the directory of the output files. Rsbuild will emit files to the specified subdirectory according to the file type.
+Configure the directory for output files. Rsbuild will emit files to the specified subdirectory according to the file type.
 
 > See [Output files](/guide/basic/output-files) for more information.
 
 ## File types
 
-`output.distPath` can be set differently for different file types.
+`output.distPath` can be configured differently for different file types.
 
 Here are the details of each `output.distPath` option:
 
 - `root`: The root directory of all output files.
 - `html`: The output directory of HTML files.
 - `favicon`: The output directory of favicon files.
 - `js`: The output directory of JavaScript files.
-- `jsAsync`: The output directory of async JavaScript files, which by default will be output to the `async` subdirectory of `distPath.js`.
+- `jsAsync`: The output directory of async JavaScript files, which by default are output to the `async` subdirectory of `distPath.js`.
 - `css`: The output directory of CSS style files.
-- `cssAsync`: The output directory of async CSS files, which by default will be output to the `async` subdirectory of `distPath.css`.
+- `cssAsync`: The output directory of async CSS files, which by default are output to the `async` subdirectory of `distPath.css`.
 - `svg`: The output directory of SVG images.
 - `font`: The output directory of font files.
 - `wasm`: The output directory of WebAssembly files.
@@ -66,7 +66,7 @@ Here are the details of each `output.distPath` option:
 
 ## Root directory
 
-The `root` is the root directory of the build artifacts and can be specified as a relative or absolute path. If `root` is a relative path, it will be appended to the project's root directory to form an absolute path.
+The `root` is the root directory of the build artifacts and can be specified as a relative or absolute path. If `root` is a relative path, it is appended to the project's root directory to form an absolute path.
 
 Other directories can only be specified as relative paths and will be output relative to the `root` directory.
 

website/docs/en/config/output/filename-hash.mdx

@@ -3,18 +3,18 @@
 - **Type:** `boolean | string`
 - **Default:** `true`
 
-Whether to add a hash value to the filename after the production build.
+Configure whether to add a hash value to the filename after the production build.
 
 ### Disable hash
 
-By default, the filename of the output files will include a hash value:
+By default, output file names include a hash value:
 
 ```bash
 dist/static/css/index.7879e19d.css
 dist/static/js/index.18a568e5.js
 ```
 
-You can set `output.filenameHash` to false to disable this behavior:
+You can set `output.filenameHash` to `false` to disable this behavior:
 
 ```js
 export default {
@@ -24,7 +24,7 @@ export default {
 };
 ```
 
-After rebuilding, the output filenames becomes:
+After rebuilding, the output filenames become:
 
 ```bash
 dist/static/css/index.css

website/docs/en/config/output/legal-comments.mdx

@@ -3,11 +3,11 @@
 - **Type:** `'linked' | 'inline' | 'none'`
 - **Default:** `'linked'`
 
-Configure how to handle the legal comments.
+Configure how to handle legal comments.
 
 ## What are legal comments?
 
-A "legal comment" is considered to be any statement-level comment in JS or rule-level comment in CSS that contains @license or @preserve or that starts with //! or /\*!. These comments are preserved in output files by default since that follows the intent of the original authors of the code.
+A "legal comment" is any statement-level comment in JS or rule-level comment in CSS that contains @license or @preserve, or that starts with //! or /\*!. These comments are preserved in output files by default since that follows the intent of the original authors of the code.
 
 For example, the `LICENSE` comment in React:
 

website/docs/en/config/output/manifest.mdx

@@ -10,7 +10,7 @@ Configure how to generate the manifest file.
 - `string`: Generate a manifest file with the specified filename or path.
 - `object`: Generate a manifest file with the specified options.
 
-The manifest file contains the information of all assets, and the mapping relationship between [entry module](/config/source/entry) and assets.
+The manifest file contains information about all assets and the mapping between [entry modules](/config/source/entry) and assets.
 
 ## Basic example
 
@@ -49,7 +49,7 @@ After building, Rsbuild will generate a `dist/manifest.json` file:
 
 ## Manifest structure
 
-By default, the manifest file will be output in the following structure:
+The manifest file will be output with the following structure by default:
 
 ```ts
 type FilePath = string;
@@ -255,7 +255,7 @@ export default {
 
 ## Multiple environments
 
-When using [environments](/config/environments) and configuring multiple environments, please specify a unique `manifest.filename` value for each environment to prevent manifest files from different environments from overwriting each other.
+When using [environments](/config/environments) with multiple environments, please specify a unique `manifest.filename` value for each environment to prevent manifest files from different environments from overwriting each other.
 
 For example, use the default `manifest.json` for the `web` environment and use `manifest-node.json` for the `node` environment:
 
@@ -279,7 +279,7 @@ export default {
 };
 ```
 
-You can also choose to generate the manifest file for a specific environment:
+You can also choose to generate the manifest file only for specific environments:
 
 ```ts title="rsbuild.config.ts"
 export default {

website/docs/en/config/output/minify.mdx

@@ -15,9 +15,9 @@ type Minify =
 
 - **Default:** `true`
 
-Configure whether to enable code minification in production mode, and to configure minimizer options.
+Configure whether to enable code minification in production mode and configure minimizer options.
 
-By default, JS and CSS code will be automatically minimized in production mode to improve page performance. If you do not want to minify the code, you can set `minify` to `false` to disable minification for all code. Alternatively, you can control the behavior of code minification through detailed configuration of the `minify` option. Below are detailed explanations for each configuration option:
+By default, JS and CSS code are automatically minified in production mode to improve page performance. If you don't want to minify the code, you can set `minify` to `false` to disable minification for all code. Alternatively, you can control code minification behavior through detailed configuration of the `minify` option. Below are detailed explanations for each configuration option:
 
 :::tip
 Rsbuild uses [SWC](/guide/configuration/swc) to minify JS code and [Lightning CSS](/guide/styling/css-usage#lightning-css) to minify CSS code by default.