docs: revert unnecessary wording changes

Author: chenjiahan

website/README.md

@@ -2,26 +2,24 @@
 
 This website is built with [Rspress](https://rspress.rs/) through Rstack CLI.
 
-The documentation source lives in `docs` and is written in Markdown or MDX.
+Documentation can be written with Markdown or MDX.
 
 ## Development
 
-Start the development server from the repository root:
+Run the development server from the repository root:
 
 ```bash
 pnpm doc
 ```
 
-Alternatively, run the website scripts from this directory:
+Build or preview the website from this directory:
 
 ```bash
-pnpm dev
 pnpm build
 pnpm preview
 ```
 
 ## Contributing
 
-Keep corresponding English and Chinese pages aligned in structure, meaning,
-links, and examples. When a translated heading would generate a different
-anchor, add an explicit anchor that matches the English heading.
+The website provides English and Chinese documentation. Keep both versions in
+sync when possible.

website/docs/en/guide/api-reference.mdx

@@ -1,6 +1,6 @@
 # API reference
 
-Rstack exposes a unified configuration API and dedicated entry points for the public APIs of Rsbuild, Rslib, Rstest, and Rslint. Prefer these entry points over direct imports from each tool's core package so that import paths and tool versions stay aligned with Rstack.
+Rstack provides a unified configuration API and re-exports the public APIs of Rsbuild, Rslib, Rstest, and Rslint through dedicated subpaths. Prefer these subpaths to direct imports from each tool's core package so that dependency entry points and tool versions remain aligned with Rstack.
 
 ## Import paths
 
@@ -19,11 +19,11 @@ Rstack exposes a unified configuration API and dedicated entry points for the pu
 
 ### `define`
 
-Import `define` from `rstack` to register tool configurations in `rstack.config.ts`. For details, see [Configuration APIs](./configuration#configuration-apis).
+Import `define` from `rstack` to register tool configurations in `rstack.config.ts`; see [Configuration APIs](./configuration#configuration-apis) for details.
 
 ## Re-exports
 
-Each tool-specific subpath re-exports the public APIs of its corresponding core package.
+The tool-specific subpaths below re-export the public APIs from their corresponding core packages. Using these Rstack entry points keeps dependency entry points and tool versions aligned with the toolchain integrated by Rstack.
 
 ### `rstack/app`
 
@@ -53,7 +53,7 @@ For details, see the [Rslib core APIs](https://rslib.rs/api/javascript-api/core)
 import { describe, expect, test } from 'rstack/test';
 ```
 
-For test APIs, see the [Rstest runtime API](https://rstest.rs/api/runtime-api/). For configuration helpers, see the [Rstest core APIs](https://rstest.rs/api/javascript-api/rstest-core).
+See the [Rstest runtime API](https://rstest.rs/api/runtime-api/) for test APIs and the [Rstest core APIs](https://rstest.rs/api/javascript-api/rstest-core) for configuration helpers.
 
 > For more guidance on testing, see [Testing](./testing).
 
@@ -69,7 +69,7 @@ For details about the available presets and plugins, see [Rslint rules and prese
 
 ## TypeScript types
 
-The following type-only entry points add ambient declarations to a TypeScript project. Add only the entries your project needs to [`compilerOptions.types`](https://www.typescriptlang.org/tsconfig/#types) in `tsconfig.json`.
+These type-only entry points add ambient declarations to a TypeScript project. Add only the entries your project needs to [`compilerOptions.types`](https://www.typescriptlang.org/tsconfig/#types) in `tsconfig.json`.
 
 ### `rstack/types`
 

website/docs/en/guide/cli/build.mdx

@@ -20,7 +20,7 @@ Examples:
 # Write output files to the output directory
 rs build --dist-path output
 
-# Generate source maps for output files
+# Generate source maps for the output files
 rs build --source-map
 
 # Rebuild when files change

website/docs/en/guide/cli/dev.mdx

@@ -20,7 +20,7 @@ Examples:
 # Start the server and open the page in the browser
 rs dev --open
 
-# Use port 8080 and exit if it is already in use
+# Use port 8080 and fail if it is already in use
 rs dev --port 8080 --strict-port
 
 # Make the server available on the local network

website/docs/en/guide/cli/doc.mdx

@@ -2,9 +2,9 @@
 
 import { PackageManagerTabs } from '@rspress/core/theme';
 
-The `rs doc` command uses [Rspress](https://rspress.rs/guide/start/introduction) to develop, build, and locally preview a documentation site.
+The `rs doc` command uses [Rspress](https://rspress.rs/guide/start/introduction) to develop, build, and preview a documentation site.
 
-[`@rspress/core`](https://www.npmjs.com/package/@rspress/core) is an optional dependency. Install it before using `rs doc`:
+Install [`@rspress/core`](https://www.npmjs.com/package/@rspress/core) before using the command:
 
 <PackageManagerTabs command="install -D @rspress/core" />
 

website/docs/en/guide/cli/lint.mdx

@@ -1,6 +1,6 @@
 # lint
 
-The `rs lint` command uses [Rslint](https://rslint.rs/guide/) to lint source files.
+The `rs lint` command uses [Rslint](https://rslint.rs/guide/) to lint source code.
 
 ## Usage
 

website/docs/en/guide/cli/preview.mdx

@@ -1,14 +1,14 @@
 # preview
 
-The `rs preview` command uses [Rsbuild](https://rsbuild.rs/guide/basic/cli#rsbuild-preview) to preview an application's production output locally.
+The `rs preview` command uses [Rsbuild](https://rsbuild.rs/guide/basic/cli#rsbuild-preview) to preview an application's production build locally.
 
 ## Usage
 
 ```bash
 rs preview [options]
 ```
 
-The command loads the application configuration registered with [`define.app()`](../configuration#define-app). Before starting the preview server, run [`rs build`](./build) to generate the production output:
+The command loads the application configuration registered with [`define.app()`](../configuration#define-app). Run [`rs build`](./build) before starting the preview server to generate the production output:
 
 ```bash
 rs build
@@ -27,7 +27,7 @@ Examples:
 # Start the preview server and open the page in the browser
 rs preview --open
 
-# Use port 8080 and exit if it is already in use
+# Use port 8080 and fail if it is already in use
 rs preview --port 8080 --strict-port
 
 # Make the preview server available on the local network

website/docs/en/guide/cli/staged.mdx

@@ -1,8 +1,8 @@
 # staged
 
-The `rs staged` command uses [lint-staged](https://github.com/lint-staged/lint-staged) to run tasks against files staged for commit.
+The `rs staged` command uses [lint-staged](https://github.com/lint-staged/lint-staged) to run tasks against files staged in Git.
 
-It is typically used in a Git hook to lint, format, or otherwise check files before a commit.
+A common use case is to run linters, formatters, or other checks on staged files before committing code.
 
 ## Usage
 
@@ -16,7 +16,7 @@ The command loads the staged-file tasks registered with [`define.staged()`](../c
 
 ### `--allow-empty`
 
-`--allow-empty` allows the commit to proceed if tasks revert all staged changes.
+`--allow-empty` allows an empty commit when tasks revert all staged changes.
 
 ```bash
 rs staged --allow-empty

website/docs/en/guide/cli/test.mdx

@@ -2,7 +2,7 @@
 
 The `rs test` command uses [Rstest](https://rstest.rs/guide/basic/cli) to run tests.
 
-> For more guidance on testing, see [Testing](../testing).
+For more guidance on testing, see [Testing](../testing).
 
 ## Usage
 

website/docs/en/guide/configuration.mdx

@@ -1,6 +1,6 @@
 # Configuration
 
-Rstack centralizes your project's tool configurations in one file. Register only the configurations your project needs with the `define.*()` APIs.
+Rstack centralizes the configuration for your project's tools in a single file. Define only the configurations your project needs with the `define.*()` APIs.
 
 ## Configuration file
 
@@ -24,7 +24,7 @@ define.lint({
 
 The configuration file does not require a default export. Each `define.*()` API can be called at most once; defining the same configuration type more than once throws an error.
 
-By default, Rstack looks for any of the following files in the project root:
+By default, Rstack looks for a file with one of the following names:
 
 - `rstack.config.ts`
 - `rstack.config.js`
@@ -39,9 +39,9 @@ rs build --config ./configs/rstack.config.ts
 
 ## Loading dependencies on demand
 
-Before running a tool, Rstack loads and executes the configuration file. It then resolves only the configuration functions required by that command.
+Every `rs` command loads and executes the Rstack configuration file, then resolves only the configuration functions needed by that command.
 
-When a configuration uses a tool-specific plugin or dependency, define it as an async function and load that dependency with dynamic `import()` inside the function. This defers loading until the configuration is needed.
+When a configuration needs to import plugins or other tool-specific dependencies, use an async configuration function and load those dependencies with dynamic `import()` inside it. This ensures that they are loaded only when the configuration is resolved.
 
 ```ts title="rstack.config.ts"
 import { define } from 'rstack';
@@ -57,7 +57,7 @@ define.app(async () => {
 
 ## Configuration APIs
 
-Each API accepts the configuration format of its underlying tool. When using APIs and helpers re-exported by Rstack, import them from the `rstack/app`, `rstack/lib`, `rstack/test`, and `rstack/lint` entry points.
+Configuration options follow the formats of the underlying tools. When using APIs and helpers that Rstack re-exports, prefer the `rstack/app`, `rstack/lib`, `rstack/test`, and `rstack/lint` entry points.
 
 | API                                 | Tool                                                                    | Commands                                                                        |
 | ----------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
@@ -70,7 +70,7 @@ Each API accepts the configuration format of its underlying tool. When using API
 
 ### `define.app()` \{#define-app}
 
-Defines the [Rsbuild configuration](https://rsbuild.rs/config/) for an application. It accepts a configuration object or a configuration function. The function receives the same configuration parameters as Rsbuild.
+Defines the [Rsbuild configuration](https://rsbuild.rs/config/) for an application. It accepts a configuration object or a configuration function. The function receives the standard Rsbuild configuration parameters.
 
 ```ts title="rstack.config.ts"
 import { define } from 'rstack';
@@ -89,7 +89,7 @@ define.app({
 
 ### `define.lib()` \{#define-lib}
 
-Defines the [Rslib configuration](https://rslib.rs/config/) for a library. It accepts a configuration object or a configuration function. The function receives the same configuration parameters as Rslib.
+Defines the [Rslib configuration](https://rslib.rs/config/) for a library. It accepts a configuration object or a configuration function. The function receives the standard Rslib configuration parameters.
 
 ```ts title="rstack.config.ts"
 import { define } from 'rstack';
@@ -106,7 +106,7 @@ define.lib({
 
 ### `define.doc()` \{#define-doc}
 
-Defines the [Rspress configuration](https://rspress.rs/api/config/config-basic) for a documentation site. It accepts either a configuration object or an async configuration function.
+Defines the [Rspress configuration](https://rspress.rs/api/config/config-basic) for a documentation site. It accepts a configuration object or an async configuration function.
 
 ```ts title="rstack.config.ts"
 import { define } from 'rstack';
@@ -117,15 +117,15 @@ define.doc({
 });
 ```
 
-`@rspress/core` is an optional peer dependency of Rstack. Install it in each project that runs `rs doc`:
+`@rspress/core` is an optional dependency of Rstack. Install it in every project that uses the `rs doc` command:
 
 ```bash
 pnpm add -D @rspress/core
 ```
 
 ### `define.test()` \{#define-test}
 
-Defines the [Rstest configuration](https://rstest.rs/config/). It accepts either a configuration object or a configuration function.
+Defines the [Rstest configuration](https://rstest.rs/config/). It accepts a configuration object or a configuration function.
 
 ```ts title="rstack.config.ts"
 import { define } from 'rstack';
@@ -140,15 +140,15 @@ define.test({
 });
 ```
 
-When `extends` is omitted, Rstack uses the Rsbuild adapter to inherit the configuration from `define.app()`. If no application configuration is registered, it uses the Rslib adapter to inherit `define.lib()` instead. `define.app()` takes precedence when both are registered. Set `extends` explicitly to opt out of automatic inheritance.
+When `extends` is omitted, Rstack automatically connects the test configuration to `define.app()` through the Rsbuild adapter. If no application configuration is defined, it falls back to `define.lib()` through the Rslib adapter. The application configuration takes precedence when both are defined. Set `extends` explicitly to opt out of this automatic inheritance.
 
-If the root test configuration contains `projects` and does not define `extends`, each inline project without its own `extends` inherits the same application or library configuration. A function-based configuration is resolved once and shared by those projects. String entries are passed to Rstest unchanged, so their external configurations load independently and do not inherit the current application or library configuration.
+If the root test configuration does not define `extends` and contains `projects`, Rstack applies automatic inheritance to each inline project that omits its own `extends`. A function-based application or library configuration is resolved once and shared by those projects. String project entries are passed to Rstest unchanged; they load their external configurations independently and do not inherit the current application or library configuration.
 
 > For more guidance on testing, see [Testing](./testing).
 
 ### `define.lint()` \{#define-lint}
 
-Defines the [Rslint configuration](https://rslint.rs/config/). Pass a configuration directly, or use an async function to load presets and plugins from `rstack/lint` on demand.
+Defines the [Rslint configuration](https://rslint.rs/config/). Pass the configuration directly, or use an async function to load presets and plugins from `rstack/lint` on demand.
 
 ```ts title="rstack.config.ts"
 import { define } from 'rstack';
@@ -162,7 +162,7 @@ define.lint(async () => {
 
 ### `define.staged()` \{#define-staged}
 
-Defines the [lint-staged configuration](https://github.com/lint-staged/lint-staged#configuration) for files staged in Git. It accepts either an object that maps glob patterns to tasks or a task-generator function. Tasks can be commands, command arrays, or functions supported by lint-staged.
+Defines the [lint-staged configuration](https://github.com/lint-staged/lint-staged#configuration) used to run tasks on staged Git files. It accepts either an object that maps glob patterns to tasks or a task-generator function. Tasks can be commands, command arrays, or functions supported by lint-staged.
 
 ```ts title="rstack.config.ts"
 import { define } from 'rstack';
@@ -172,4 +172,4 @@ define.staged({
 });
 ```
 
-Unlike the other tool commands, `rs staged` requires a `define.staged()` configuration and exits with an error when it is missing.
+Unlike the other commands, `rs staged` requires a `define.staged()` configuration and reports an error when it is missing.