diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index 80145794eb..df814a23d1 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -1,6 +1,6 @@
-# Contributor Covenant Code of Conduct
+# Contributor covenant code of conduct
 
-## Our Pledge
+## Our pledge
 
 We as members, contributors, and leaders pledge to make participation in our
 community a harassment-free experience for everyone, regardless of age, body
@@ -12,7 +12,7 @@ and orientation.
 We pledge to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.
 
-## Our Standards
+## Our standards
 
 Examples of behavior that contributes to a positive environment for our
 community include:
@@ -36,7 +36,7 @@ Examples of unacceptable behavior include:
 - Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
-## Enforcement Responsibilities
+## Enforcement responsibilities
 
 Community leaders are responsible for clarifying and enforcing our standards of
 acceptable behavior and will take appropriate and fair corrective action in
@@ -65,7 +65,7 @@ All complaints will be reviewed and investigated promptly and fairly.
 All community leaders are obligated to respect the privacy and security of the
 reporter of any incident.
 
-## Enforcement Guidelines
+## Enforcement guidelines
 
 Community leaders will follow these Community Impact Guidelines in determining
 the consequences for any action they deem in violation of this Code of Conduct:
@@ -91,7 +91,7 @@ includes avoiding interactions in community spaces as well as external channels
 like social media. Violating these terms may lead to a temporary or
 permanent ban.
 
-### 3. Temporary Ban
+### 3. Temporary ban
 
 **Community Impact**: A serious violation of community standards, including
 sustained inappropriate behavior.
@@ -102,7 +102,7 @@ private interaction with the people involved, including unsolicited interaction
 with those enforcing the Code of Conduct, is allowed during this period.
 Violating these terms may lead to a permanent ban.
 
-### 4. Permanent Ban
+### 4. Permanent ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
 standards, including sustained inappropriate behavior, harassment of an
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 69a051d92f..26eb2e020d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,12 +1,12 @@
-# Rsbuild Contribution Guide
+# Rsbuild contribution guide
 
 Thank you for your interest in contributing to Rsbuild! Before you start your contribution, please take a moment to read the following guidelines.
 
 ---
 
-## Setup the Environment
+## Setup the environment
 
-### Fork the Repo
+### Fork the repo
 
 [Fork](https://help.github.com/articles/fork-a-repo/) this repository to your
 own GitHub account and then [clone](https://help.github.com/articles/cloning-a-repository/) it to your local.
@@ -39,7 +39,7 @@ nvm alias default 20
 nvm use 20
 ```
 
-### Install Dependencies
+### Install dependencies
 
 Enable [pnpm](https://pnpm.io/) with corepack:
 
@@ -59,7 +59,7 @@ What this will do:
 - Create symlinks between packages in the monorepo
 - Run the `prepare` script to build all packages, powered by [nx](https://nx.dev/).
 
-### Set Git Email
+### Set git email
 
 Please make sure you have your email set up in `<https://github.com/settings/emails>`. This will be needed later when you want to submit a pull request.
 
@@ -83,11 +83,11 @@ git config user.email "SOME_EMAIL@example.com"
 
 ---
 
-## Making Changes and Building
+## Making changes and building
 
 Once you have set up the local development environment in your forked repo, we can start development.
 
-### Checkout A New Branch
+### Checkout a new branch
 
 It is recommended to develop on a new branch, as it will make things easier later when you submit a pull request:
 
@@ -95,7 +95,7 @@ It is recommended to develop on a new branch, as it will make things easier late
 git checkout -b MY_BRANCH_NAME
 ```
 
-### Build the Package
+### Build the package
 
 Use [nx build](https://nx.dev/nx-api/nx/documents/run) to build the package you want to change:
 
@@ -113,13 +113,13 @@ pnpm run build
 
 ## Testing
 
-### Add New Tests
+### Add new tests
 
 If you've fixed a bug or added code that should be tested, then add some tests.
 
 You can add unit test cases in the `<PACKAGE_DIR>/tests` folder. The test runner is based on [Vitest](https://vitest.dev/).
 
-### Run Unit Tests
+### Run unit tests
 
 Before submitting a pull request, it's important to make sure that the changes haven't introduced any regressions or bugs. You can run the unit tests for the project by executing the following command:
 
@@ -133,7 +133,7 @@ You can also run the unit tests of single package:
 pnpm run ut packages/core
 ```
 
-### Run E2E Tests
+### Run E2E tests
 
 Rsbuild uses [playwright](https://github.com/microsoft/playwright) to run end-to-end tests.
 
@@ -174,9 +174,9 @@ You can find the Rsbuild documentation in the [website](./website) folder.
 
 ---
 
-## Submitting Changes
+## Submitting changes
 
-### Committing your Changes
+### Committing your changes
 
 Commit your changes to your forked repo, and [create a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
diff --git a/README.md b/README.md
index ece94e0057..0120a66cee 100644
--- a/README.md
+++ b/README.md
@@ -68,7 +68,7 @@ The following diagram illustrates the relationship between Rsbuild and other too
 
 ![Rspack stack layers](https://assets.rspack.dev/rsbuild/assets/rspack-stack-layers.png)
 
-## 📚 Getting Started
+## 📚 Getting started
 
 To get started with Rsbuild, see the [Quick Start](https://rsbuild.dev/guide/start/quick-start).
 
@@ -138,7 +138,7 @@ Please read the [Contributing Guide](https://github.com/web-infra-dev/rsbuild/bl
   </table>
 </a>
 
-### Code of Conduct
+### Code of conduct
 
 This repo has adopted the ByteDance Open Source Code of Conduct. Please check [Code of Conduct](./CODE_OF_CONDUCT.md) for more details.
 
diff --git a/README.pt-BR.md b/README.pt-BR.md
index b692cfd9d8..82fc2c1c48 100644
--- a/README.pt-BR.md
+++ b/README.pt-BR.md
@@ -138,7 +138,7 @@ Por favor leia o [Guia de Contribuição](https://github.com/web-infra-dev/rsbui
   </table>
 </a>
 
-### Código de Conduta
+### Código de conduta
 
 Este repositório adotou o código de conduta de código aberto da ByteDance. Por favor, verifique [Código de Conduta](./CODE_OF_CONDUCT.md) para mais detalhes.
 
diff --git a/e2e/README.md b/e2e/README.md
index b77c87a97e..e4dab66916 100644
--- a/e2e/README.md
+++ b/e2e/README.md
@@ -2,7 +2,7 @@
 
 This folder contains the e2e test cases of Rsbuild.
 
-## Tech Stack
+## Tech stack
 
 - [playwright](https://github.com/microsoft/playwright): The e2e test framework.
 
@@ -11,13 +11,13 @@ This folder contains the e2e test cases of Rsbuild.
 Most of the E2E tests in Rsbuild are run by both Rspack and Webpack at the same time. This is to check that the functionality of Rspack is correctly aligned with Webpack.
 
 ```bash
-# Run all test cases, including Rspack and Webpack
+# Run all test cases, including Rspack and webpack
 pnpm test
 
 # Run test cases for Rspack
 pnpm test:rspack
 
-# Run test cases for Webpack
+# Run test cases for webpack
 pnpm test:webpack
 
 # Run specific test case, such as "css"
@@ -25,7 +25,7 @@ pnpm test:webpack css
 pnpm test:rspack css
 ```
 
-## Add Test Cases
+## Add test cases
 
 Test cases added using the `test` method will run in both Rspack and Webpack.
 
diff --git a/examples/README.md b/examples/README.md
index ba50851280..675bbce8c7 100644
--- a/examples/README.md
+++ b/examples/README.md
@@ -1,11 +1,11 @@
-# Rsbuild Examples
+# Rsbuild examples
 
 This folder contains some basic examples for Rsbuild, you can use these examples for debugging.
 
-## More Cases
+## More cases
 
 More use cases can be found in [e2e/cases](../e2e/cases/).
 
-## Add Examples
+## Add examples
 
 It is recommended to add more examples to [rspack-examples](https://github.com/rspack-contrib/rspack-examples).
diff --git a/packages/compat/README.md b/packages/compat/README.md
index 6b194095e1..fe9b7fab48 100644
--- a/packages/compat/README.md
+++ b/packages/compat/README.md
@@ -1,4 +1,4 @@
-# Compat Packages
+# Compat packages
 
 The compat folder contains some packages that are used to test the compatibility of Rspack with webpack.
 
diff --git a/packages/create-rsbuild/template-common/README.md b/packages/create-rsbuild/template-common/README.md
index 37b1dd3328..5fc0306f5b 100644
--- a/packages/create-rsbuild/template-common/README.md
+++ b/packages/create-rsbuild/template-common/README.md
@@ -1,4 +1,4 @@
-# Rsbuild Project
+# Rsbuild project
 
 ## Setup
 
@@ -8,7 +8,7 @@ Install the dependencies:
 pnpm install
 ```
 
-## Get Started
+## Get started
 
 Start the dev server:
 
diff --git a/website/README.md b/website/README.md
index db55263eac..b46aa210a5 100644
--- a/website/README.md
+++ b/website/README.md
@@ -1,4 +1,4 @@
-# Rsbuild Website
+# Rsbuild website
 
 This website is built with [Rspress](https://github.com/web-infra-dev/rspress), the document content can be written using markdown or mdx syntax. You can refer to the [Rspress Website](https://rspress.dev/) for detailed usage.
 
@@ -6,7 +6,11 @@ This website is built with [Rspress](https://github.com/web-infra-dev/rspress),
 
 Currently Rsbuild provides documentation in English and Chinese. If you can use Chinese, please update both documents at the same time. Otherwise, just update the English documentation.
 
-### Image Assets
+## Writing style guide
+
+The same as Rspack: [Writing style guide](https://github.com/web-infra-dev/rspack/tree/main/website#writing-style-guide).
+
+### Image assets
 
 For images you use in the document, it's better to upload them to the [rspack-contrib/rstack-design-resources](https://github.com/rspack-contrib/rstack-design-resources) repository, so the size of the current repository doesn't get too big.
 
diff --git a/website/docs/en/api/javascript-api/core.mdx b/website/docs/en/api/javascript-api/core.mdx
index 221a7dd434..720c0b848b 100644
--- a/website/docs/en/api/javascript-api/core.mdx
+++ b/website/docs/en/api/javascript-api/core.mdx
@@ -1,4 +1,4 @@
-# Rsbuild Core
+# Rsbuild core
 
 This section describes some of the core methods provided by Rsbuild.
 
@@ -212,7 +212,7 @@ The `mergeRsbuildConfig` function takes multiple configuration objects as parame
 function mergeRsbuildConfig(...configs: RsbuildConfig[]): RsbuildConfig;
 ```
 
-### Basic Example
+### Basic example
 
 ```ts
 import { mergeRsbuildConfig } from '@rsbuild/core';
@@ -235,7 +235,7 @@ console.log(mergedConfig); // { dev: { https: true } }
 
 > This method will not modify the config object in the input parameter.
 
-### Merge Rules
+### Merge rules
 
 In addition to deep merging, the `mergeRsbuildConfig` function also handles some options in a special way.
 
@@ -337,7 +337,7 @@ logger.debug('This is a debug message');
 logger.log('This is a log message');
 ```
 
-### Custom Logger
+### Custom logger
 
 You can use the `logger.override` method to override partial or all methods of the default logger:
 
diff --git a/website/docs/en/api/javascript-api/environment-api.mdx b/website/docs/en/api/javascript-api/environment-api.mdx
index 4757378438..a4c11c251a 100644
--- a/website/docs/en/api/javascript-api/environment-api.mdx
+++ b/website/docs/en/api/javascript-api/environment-api.mdx
@@ -4,7 +4,7 @@ Here you can find all the environment related APIs.
 
 > See [Multi-Environment Builds](/guide/advanced/environments) for more details.
 
-## Environment Context
+## Environment context
 
 Environment context is a read-only object that provides some context information about the current environment.
 
diff --git a/website/docs/en/api/javascript-api/instance.mdx b/website/docs/en/api/javascript-api/instance.mdx
index f38b2acc62..51c3bc0f0e 100644
--- a/website/docs/en/api/javascript-api/instance.mdx
+++ b/website/docs/en/api/javascript-api/instance.mdx
@@ -1,4 +1,4 @@
-# Rsbuild Instance
+# Rsbuild instance
 
 This section describes all the properties and methods on the Rsbuild instance object.
 
@@ -152,7 +152,7 @@ const result = await rsbuild.build({
 await result.close();
 ```
 
-### Stats Object
+### Stats object
 
 In non-watch mode, the `rsbuild.build() returns an Rspack [stats](https://rspack.dev/api/javascript-api/stats) object:
 
@@ -162,7 +162,7 @@ const result = await rsbuild.build();
 console.log(result.stats);
 ```
 
-### Custom Compiler
+### Custom compiler
 
 In some cases, you may want to use a custom compiler:
 
@@ -249,7 +249,7 @@ console.log(port); // 3000
 await server.close();
 ```
 
-### Custom Compiler
+### Custom compiler
 
 In some cases, you may want to use a custom compiler:
 
@@ -264,7 +264,7 @@ await rsbuild.startDevServer({
 });
 ```
 
-### Get Port Silently
+### Get port silently
 
 In some cases, the default startup port number is already occupied. In this situation, Rsbuild will automatically increment the port number until it finds an available one. This process will output a prompt log. If you do not want this log, you can set `getPortSilently` to `true`.
 
@@ -677,7 +677,7 @@ await rsbuild.inspectConfig({
 });
 ```
 
-### Output Path
+### Output path
 
 You can set the output path using `outputPath`. The default value is [output.distPath.root](/config/output/dist-path).
 
diff --git a/website/docs/en/api/javascript-api/types.mdx b/website/docs/en/api/javascript-api/types.mdx
index 176ab62f65..b305d4bbdf 100644
--- a/website/docs/en/api/javascript-api/types.mdx
+++ b/website/docs/en/api/javascript-api/types.mdx
@@ -1,4 +1,4 @@
-# Rsbuild Types
+# Rsbuild types
 
 This section describes some of the type definitions provided by the Rsbuild.
 
diff --git a/website/docs/en/api/start/index.mdx b/website/docs/en/api/start/index.mdx
index 77c7f75618..971527e59f 100644
--- a/website/docs/en/api/start/index.mdx
+++ b/website/docs/en/api/start/index.mdx
@@ -4,7 +4,7 @@ Rsbuild provides a complete set of JavaScript APIs for developers to build highe
 
 Rsbuild's JavaScript API can be used in Node.js, Deno, or Bun.
 
-## Access Example
+## Access example
 
 Here is a basic example of how to access the Rsbuild JavaScript API.
 
@@ -16,7 +16,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/core -D" />
 
-### 2. Create an Rsbuild Instance
+### 2. Create an Rsbuild instance
 
 You can call the [createRsbuild](/api/javascript-api/core#creatersbuild) method to create an Rsbuild instance:
 
@@ -28,7 +28,7 @@ const rsbuild = await createRsbuild();
 
 The `createRsbuild` method provides some options, which you can learn more about in the [API - createRsbuild](/api/javascript-api/core#creatersbuild).
 
-### 3. Call Rsbuild Instance Method
+### 3. Call Rsbuild instance method
 
 The Rsbuild instance provides some methods, which you can use it according to the usage scenarios.
 
@@ -55,7 +55,7 @@ await rsbuild.build();
 
 After completing the above three steps, you have learned the basic usage of Rsbuild. Next, you can customize the build process through the Rsbuild plugin and Rsbuild configs.
 
-## Exports Format
+## Exports format
 
 Rsbuild provides exports in both ES Modules and CommonJS formats:
 
diff --git a/website/docs/en/community/releases/index.mdx b/website/docs/en/community/releases/index.mdx
index 738e36900e..1639bcade6 100644
--- a/website/docs/en/community/releases/index.mdx
+++ b/website/docs/en/community/releases/index.mdx
@@ -4,7 +4,7 @@
 
 Please visit [GitHub - release](https://github.com/web-infra-dev/rsbuild/releases) to view the changes for each version of Rsbuild.
 
-## Semantic Version
+## Semantic version
 
 Rsbuild follows the [Semantic Versioning](https://semver.org/) specification.
 
diff --git a/website/docs/en/community/releases/v0-1.mdx b/website/docs/en/community/releases/v0-1.mdx
index e6ef646c89..863d9545bd 100644
--- a/website/docs/en/community/releases/v0-1.mdx
+++ b/website/docs/en/community/releases/v0-1.mdx
@@ -38,7 +38,7 @@ Rsbuild has the following features:
 
 - **Framework Agnostic**: Rsbuild is not coupled with any front-end UI framework. It supports frameworks like React, Vue, Svelte, Solid and Preact through plugins, and plans to support more UI frameworks from the community in the future.
 
-### 💡 Next Step
+### 💡 Next step
 
 Currently, Rsbuild is still evolving rapidly and plans to introduce many more powerful new features.
 
diff --git a/website/docs/en/community/releases/v0-2.mdx b/website/docs/en/community/releases/v0-2.mdx
index fc6f292369..afc17824dd 100644
--- a/website/docs/en/community/releases/v0-2.mdx
+++ b/website/docs/en/community/releases/v0-2.mdx
@@ -63,7 +63,7 @@ export default {
 };
 ```
 
-## Write to Disk
+## Write to disk
 
 `dev.writeToDisk` defaults to `false`.
 
@@ -83,7 +83,7 @@ export default {
 };
 ```
 
-## Babel Plugin
+## Babel plugin
 
 `@rsbuild/plugin-babel` will move all babel-loader options to `babelLoaderOptions`:
 
@@ -109,7 +109,7 @@ pluginBabel([
 
 This change allows us to add more options for `pluginBabel`, such as `include` and `exclude`.
 
-## Source Map
+## Source map
 
 `output.disableSourceMap` has been renamed to `output.sourceMap`.
 
@@ -144,7 +144,7 @@ The default value of source map has also been updated to improve build performan
 - before: generate JS / CSS source map in development, generate JS source map in production.
 - after: generate JS source map in development, no source map are generated in production.
 
-## Inject Styles
+## Inject styles
 
 Rename `output.disableCssExtract` to `output.injectStyles` to be clearer:
 
diff --git a/website/docs/en/community/releases/v0-3.mdx b/website/docs/en/community/releases/v0-3.mdx
index 7f64a0d8e0..911d7669ec 100644
--- a/website/docs/en/community/releases/v0-3.mdx
+++ b/website/docs/en/community/releases/v0-3.mdx
@@ -19,7 +19,7 @@ Notable changes:
 - [Module Federation added to Rspack](https://rspack.dev/blog/module-federation-added-to-rspack)
 - [Remove deprecated builtins options](https://rspack.dev/blog/announcing-0-5#make-swchelpers-and-react-refresh-as-peerdependencies)
 
-## TOML / YAML Plugin
+## TOML / YAML plugin
 
 The need to import TOML and YAML in JS is not common, so Rsbuild core will no longer support import TOML and YAML by default in v0.3.0.
 
@@ -54,7 +54,7 @@ Some JavaScript APIs have changed:
 - The `printURLs` option of `rsbuild.startDevServer` is deprecated, use [server.printUrls](/config/server/print-urls) instead.
 - The `logger` option of `rsbuild.startDevServer` is deprecated, use [logger.override()](/api/javascript-api/core#logger) instead.
 
-## Node Target
+## Node target
 
 - Adjust default browserslist for node target, from `node >= 14` to `node >= 16`.
 - The default value of `output.distPath.server` is changed from `'bundles'` to `'server'`
diff --git a/website/docs/en/community/releases/v0-4.mdx b/website/docs/en/community/releases/v0-4.mdx
index 334be73f24..50cfa27482 100644
--- a/website/docs/en/community/releases/v0-4.mdx
+++ b/website/docs/en/community/releases/v0-4.mdx
@@ -10,7 +10,7 @@ published_at: 2024-02-06 08:00:00
 
 Rsbuild 0.4 provides built-in support for module federation. It also contains some incompatible API updates. Please refer to the current document for upgrading.
 
-### Module Federation Config
+### Module Federation config
 
 Rsbuild now provides a builtin [moduleFederation](/config/module-federation/options) option, which will make configuring Module Federation in Rsbuild much easier.
 
@@ -30,7 +30,7 @@ When you use this option, Rsbuild will automatically set the default `publicPath
 
 > See [RFC - Provide first-class support for Module Federation](https://github.com/web-infra-dev/rsbuild/discussions/1461) for details.
 
-### Plugin Hook Order
+### Plugin hook order
 
 In Rsbuild plugin, you can now declare the order of hooks using the `order` field:
 
@@ -93,7 +93,7 @@ module.exports = {
 };
 ```
 
-## Pure React Plugin
+## Pure React plugin
 
 The React plugin has removed default [source.transformImport](/config/source/transform-import) config for [antd](https://www.npmjs.com/package/antd) v4 and [@arco-design/web-react](https://www.npmjs.com/package/@arco-design/web-react).
 
diff --git a/website/docs/en/community/releases/v0-5.mdx b/website/docs/en/community/releases/v0-5.mdx
index 7687979602..5664c8f525 100644
--- a/website/docs/en/community/releases/v0-5.mdx
+++ b/website/docs/en/community/releases/v0-5.mdx
@@ -38,7 +38,7 @@ In a real large-scale web application, we have integrated the Rsbuild Lightning
 - CSS compilation time was reduced from 8.4s to 0.12s, a 70x improvement.
 - The overall build time was reduced from 33.1s to 25.4s, a 30% increase.
 
-## 🌟 Support for Custom Server
+## 🌟 Support for custom server
 
 Rsbuild now supports replacing the dev server with a custom server that reuses Rsbuild's page preview, routing, and module hot update features. This makes it easier to integrate Rsbuild with other Node.js frameworks.
 
@@ -60,7 +60,7 @@ async function startCustomServer() {
 
 For more details, please refer to [Rsbuild - createDevServer](/api/javascript-api/instance#rsbuildcreatedevserver).
 
-## 🍭 Refactoring SVGR Plugin
+## 🍭 Refactoring SVGR plugin
 
 In versions prior to 0.5.0, the default usage of the SVGR plugin was the same as create-react-app, allowing SVGs to be used via mixed import:
 
@@ -94,7 +94,7 @@ pluginSvgr({
 });
 ```
 
-## 📍 Custom Minify Options
+## 📍 Custom minify options
 
 The `output.disableMinimize` option has been renamed to [output.minify](/config/output/minify), and it allows customizing JS and HTML minification options.
 
diff --git a/website/docs/en/community/releases/v0-7.mdx b/website/docs/en/community/releases/v0-7.mdx
index b72f2ae45a..8a55057fd6 100644
--- a/website/docs/en/community/releases/v0-7.mdx
+++ b/website/docs/en/community/releases/v0-7.mdx
@@ -48,7 +48,7 @@ export default config;
 
 > For more usage, please refer to [storybook-rsbuild repository](https://github.com/rspack-contrib/storybook-rsbuild).
 
-## Faster Sass Compilation
+## Faster Sass compilation
 
 In Rsbuild 0.7, **Sass compilation is 3~10 times faster**. The performance improvements are particularly noticeable on large projects.
 
@@ -60,7 +60,7 @@ This improvement is due to Rsbuild's default use of [sass-embedded](https://www.
 
 Rsbuild has also enabled the latest sass-loader's [modern-compiler](https://github.com/webpack-contrib/sass-loader/releases/tag/v14.2.0) API. This can enable Sass's shared resources feature, which allows the same compiler process to be reused when compiling multiple files, improving build performance.
 
-## Better CSS Supports
+## Better CSS supports
 
 Rsbuild now uses [CssExtractRspackPlugin](https://www.rspack.dev/plugins/rspack/css-extract-rspack-plugin) to extract CSS into separate files, rather than using the [experimental.css](https://www.rspack.dev/config/experiments#experimentscss) config to do so.
 
@@ -151,7 +151,7 @@ const { createRsbuild } = require('@rsbuild/core');
 
 ESM/CJS interop is a tricky issue, so we will provide both formats for a long time to make it easier for more users to use.
 
-## Breaking Changes
+## Breaking changes
 
 ### Upgrade Rspack to 0.7
 
@@ -161,7 +161,7 @@ In the new version, Rspack supports lazy compilation, which can significantly im
 
 In Rsbuild, you can use [dev.lazyCompilation](/config/dev/lazy-compilation) to enable lazy compilation.
 
-### Sass and Less Plugins
+### Sass and Less plugins
 
 Rsbuild's Sass and Less plugins are now two separate npm packages instead of being built into `@rsbuild/core` as before. This change allows users to enable Sass and Less compilation as needed.
 
@@ -187,7 +187,7 @@ export default {
 };
 ```
 
-### dataUriLimit Defaults
+### dataUriLimit defaults
 
 The default value for [output.dataUriLimit](/config/output/data-uri-limit) has been changed from `10000 (10kB)` to `4096 (4KiB)`.
 
diff --git a/website/docs/en/config/dev/asset-prefix.mdx b/website/docs/en/config/dev/asset-prefix.mdx
index aa09f8fafd..dc63e72a8d 100644
--- a/website/docs/en/config/dev/asset-prefix.mdx
+++ b/website/docs/en/config/dev/asset-prefix.mdx
@@ -9,7 +9,7 @@ Set the URL prefix of static assets in [development mode](/config/mode).
 
 This config is only used in development mode. In the production mode, please use the [output.assetPrefix](/config/output/asset-prefix) to set the URL prefix.
 
-## Default Value
+## Default value
 
 The default value of `dev.assetPrefix` is the same as [server.base](/config/server/base).
 
@@ -28,7 +28,7 @@ export default {
 };
 ```
 
-## Boolean Type
+## Boolean type
 
 If `assetPrefix` is set to `true`, the URL prefix will be `http://localhost:<port>/`:
 
@@ -101,7 +101,7 @@ export default {
 };
 ```
 
-## Path Types
+## Path types
 
 assetPrefix can be set to the following types of paths:
 
diff --git a/website/docs/en/config/dev/cli-shortcuts.mdx b/website/docs/en/config/dev/cli-shortcuts.mdx
index a0f6b3b635..f4043118f7 100644
--- a/website/docs/en/config/dev/cli-shortcuts.mdx
+++ b/website/docs/en/config/dev/cli-shortcuts.mdx
@@ -16,7 +16,7 @@ type CliShortcuts =
 
 Whether to enable CLI shortcuts.
 
-## All Shortcuts
+## All shortcuts
 
 Press `h + Enter` to show all shortcuts:
 
@@ -51,7 +51,7 @@ export default {
 };
 ```
 
-## Custom Shortcuts
+## Custom shortcuts
 
 `custom` option can be used to custom shortcuts, the value is a function that receives the default shortcuts array and returns a new shortcuts array.
 
@@ -92,7 +92,7 @@ export default {
 };
 ```
 
-## Print Help
+## Print help
 
 `help` option can be used to control whether to print the help hint when the server is started:
 
diff --git a/website/docs/en/config/dev/client.mdx b/website/docs/en/config/dev/client.mdx
index 73d9d43add..6deebe14c0 100644
--- a/website/docs/en/config/dev/client.mdx
+++ b/website/docs/en/config/dev/client.mdx
@@ -83,7 +83,7 @@ During the HMR process, the page will make GET requests to get hot-update files,
 
 Hot-update files are considered to be static assets. If you need to configure the URL for hot-update files, please use the [dev.assetPrefix](/config/dev/asset-prefix) option.
 
-## Error Overlay
+## Error overlay
 
 The `dev.client.overlay` option allows you to choose whether or not to enable the error overlay feature.
 
diff --git a/website/docs/en/config/dev/lazy-compilation.mdx b/website/docs/en/config/dev/lazy-compilation.mdx
index 960ffa05fc..ec43fffe5c 100644
--- a/website/docs/en/config/dev/lazy-compilation.mdx
+++ b/website/docs/en/config/dev/lazy-compilation.mdx
@@ -41,7 +41,7 @@ With lazy compilation enabled, Rspack will only compile the entrypoints and dyna
 
 ## Example
 
-### Enable Lazy Compilation
+### Enable lazy compilation
 
 ```ts
 export default {
@@ -64,7 +64,7 @@ export default {
 };
 ```
 
-### Entry Modules
+### Entry modules
 
 Use `lazyCompilation.entries` to control whether to lazily compile entry modules:
 
@@ -85,7 +85,7 @@ When lazily compiling entry modules, please note:
 - It only applies to multi-page applications (MPA) and does not optimize single-page applications (SPA).
 - When you visit a page, you need to wait for the page to finish compiling before you can see its content.
 
-### Async Modules
+### Async modules
 
 Use `lazyCompilation.imports` to control whether to lazily compile [dynamic imported](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import) modules.
 
diff --git a/website/docs/en/config/dev/live-reload.mdx b/website/docs/en/config/dev/live-reload.mdx
index 857bc7a389..76d4f1a00e 100644
--- a/website/docs/en/config/dev/live-reload.mdx
+++ b/website/docs/en/config/dev/live-reload.mdx
@@ -11,7 +11,7 @@ Please refer to [Hot Module Replacement](/guide/advanced/hmr) for more informati
 
 ## Disabling liveReload
 
-If you need to disable liveReload, you can set both `dev.hmr` and `dev.liveReload` to `false`. Then, no Web Socket requests will be made to the dev server on the page, and the page will not automatically refresh when file change.
+If you need to disable liveReload, you can set both `dev.hmr` and `dev.liveReload` to `false`. Then, no WebSocket requests will be made to the dev server on the page, and the page will not automatically refresh when file change.
 
 ```js
 export default {
diff --git a/website/docs/en/config/dev/setup-middlewares.mdx b/website/docs/en/config/dev/setup-middlewares.mdx
index 17b3fd5645..13157972da 100644
--- a/website/docs/en/config/dev/setup-middlewares.mdx
+++ b/website/docs/en/config/dev/setup-middlewares.mdx
@@ -26,7 +26,7 @@ type SetupMiddlewares = Array<
 
 Provides the ability to execute a custom function and apply custom middlewares.
 
-## Execution Order
+## Execution order
 
 The order among several different types of middleware is: `unshift` => internal middlewares => `push`.
 
diff --git a/website/docs/en/config/dev/write-to-disk.mdx b/website/docs/en/config/dev/write-to-disk.mdx
index c69666c5e2..c7588323f6 100644
--- a/website/docs/en/config/dev/write-to-disk.mdx
+++ b/website/docs/en/config/dev/write-to-disk.mdx
@@ -9,7 +9,7 @@ Controls whether the build output from development mode is written to disk.
 In development mode, Rsbuild stores the build outputs in memory on the dev server by default, rather than writing then to disk. This can reduce the overhead of fs operations. You can refer to [View Static Assets](/guide/basic/server#view-static-assets) to view all static assets generated in the current build.
 :::
 
-## Writing to Disk
+## Writing to disk
 
 You can choose to write the build output to disk, which is usually used for inspecting the content of the build output or configuring proxy rules for static assets.
 
@@ -27,7 +27,7 @@ export default {
 Setting `writeToDisk: true` is used for viewing the build output from development mode. It does not change the behavior of the dev server. When accessing files through a browser, the dev server will still read the file content from memory.
 :::
 
-## Matching Specific Files
+## Matching specific files
 
 You can also set `dev.writeToDisk` to a function to match only certain files. When the function returns `false`, the file will not be written; when it returns `true`, the file will be written to disk.
 
diff --git a/website/docs/en/config/html/crossorigin.mdx b/website/docs/en/config/html/crossorigin.mdx
index 7b3798713e..c583f077df 100644
--- a/website/docs/en/config/html/crossorigin.mdx
+++ b/website/docs/en/config/html/crossorigin.mdx
@@ -45,7 +45,7 @@ The `<style>` tag becomes:
 If the domain of static assets is the same as the current page, Rsbuild will not add the crossorigin="anonymous" attribute, as this attribute is not required for non-cross-domain scenario.
 :::
 
-## Optional Values
+## Optional values
 
 `crossorigin` can the set to the following values:
 
diff --git a/website/docs/en/config/html/favicon.mdx b/website/docs/en/config/html/favicon.mdx
index c05ae0fa45..f586bd3e68 100644
--- a/website/docs/en/config/html/favicon.mdx
+++ b/website/docs/en/config/html/favicon.mdx
@@ -57,7 +57,7 @@ After recompiling, the following tags are automatically generated in the HTML:
 <link rel="icon" href="/favicon.ico" />
 ```
 
-## Function Usage
+## Function usage
 
 - **Type:**
 
diff --git a/website/docs/en/config/html/inject.mdx b/website/docs/en/config/html/inject.mdx
index d173ee325a..6a61ceac5a 100644
--- a/website/docs/en/config/html/inject.mdx
+++ b/website/docs/en/config/html/inject.mdx
@@ -58,7 +58,7 @@ You will see that the script tag is generated at the end of the body tag:
 </html>
 ```
 
-## Function Usage
+## Function usage
 
 - **Type:**
 
@@ -83,7 +83,7 @@ export default {
 };
 ```
 
-## Manual Injection
+## Manual injection
 
 When `html.inject` is set to `false`, Rsbuild will not inject tags into the HTML, and the tags defined in [html.tags](/config/html/tags) will not take effect.
 
diff --git a/website/docs/en/config/html/meta.mdx b/website/docs/en/config/html/meta.mdx
index 919b2dd157..02d36486b2 100644
--- a/website/docs/en/config/html/meta.mdx
+++ b/website/docs/en/config/html/meta.mdx
@@ -20,7 +20,7 @@ Configure the `<meta>` tag of the HTML.
 If the HTML template used in the current project already contains the charset or viewport meta tags, then the tags in the HTML template take precedence.
 :::
 
-## String Type
+## String type
 
 - **Type:**
 
@@ -50,7 +50,7 @@ The generated `meta` tag in HTML is:
 <meta name="description" content="a description of the page" />
 ```
 
-## Object Type
+## Object type
 
 - **Type:**
 
@@ -89,7 +89,7 @@ The `meta` tag in HTML is:
 <meta charset="UTF-8" />
 ```
 
-## Function Usage
+## Function usage
 
 - **Type:**
 
@@ -145,7 +145,7 @@ export default {
 };
 ```
 
-## Remove Default Value
+## Remove default value
 
 Setting the `value` of the `meta` object to `false` and the meta tag will not be generated.
 
diff --git a/website/docs/en/config/html/mount-id.mdx b/website/docs/en/config/html/mount-id.mdx
index bc73eae834..74ad5d62ff 100644
--- a/website/docs/en/config/html/mount-id.mdx
+++ b/website/docs/en/config/html/mount-id.mdx
@@ -33,7 +33,7 @@ After compilation:
 
 ## Notes
 
-### Update Relevant Code
+### Update relevant code
 
 After modifying `mountId`, if there is logic in your code to obtain the `root` root node, please update the corresponding value:
 
@@ -44,6 +44,6 @@ After modifying `mountId`, if there is logic in your code to obtain the `root` r
 ReactDOM.createRoot(domNode).render(<App />);
 ```
 
-### Custom Templates
+### Custom templates
 
 If you customized the HTML template, please make sure that the template contains `<div id="<%= mountId %>"></div>`, otherwise the `mountId` config will not take effect.
diff --git a/website/docs/en/config/html/tags.mdx b/website/docs/en/config/html/tags.mdx
index f1a1c22cb6..46f7c9042a 100644
--- a/website/docs/en/config/html/tags.mdx
+++ b/website/docs/en/config/html/tags.mdx
@@ -10,7 +10,7 @@ type TagsConfig = HtmlTag | HtmlTagHandler | Array<HtmlTag | HtmlTagHandler>;
 
 Modifies the tags that are injected into the HTML page.
 
-## Tag Object
+## Tag object
 
 ```ts
 type HtmlTag = {
@@ -102,7 +102,7 @@ The final insertion position on the page is as follows:
 </html>
 ```
 
-## Tags Handler
+## Tags handler
 
 ```ts
 type HtmlTagContext = {
diff --git a/website/docs/en/config/html/template-parameters.mdx b/website/docs/en/config/html/template-parameters.mdx
index 2505e659f4..85f40b2d6f 100644
--- a/website/docs/en/config/html/template-parameters.mdx
+++ b/website/docs/en/config/html/template-parameters.mdx
@@ -28,7 +28,7 @@ type DefaultParameters = {
 
 Define the parameters in the HTML template, see [HTML Template - Template Parameters](/guide/basic/html-template#template-parameters) for detailed usage.
 
-## Object Usage
+## Object usage
 
 If the value of `templateParameters` is an object, it will be merged with the default parameters using `Object.assign`.
 
@@ -60,7 +60,7 @@ The compiled HTML code will be:
 </script>
 ```
 
-## Function Usage
+## Function usage
 
 - **Type:**
 
diff --git a/website/docs/en/config/html/template.mdx b/website/docs/en/config/html/template.mdx
index 5d9c79fc97..72799af3db 100644
--- a/website/docs/en/config/html/template.mdx
+++ b/website/docs/en/config/html/template.mdx
@@ -16,7 +16,7 @@ If `template` is not specified, the built-in HTML template of Rsbuild will be us
 </html>
 ```
 
-## String Usage
+## String usage
 
 For example, to replace the default HTML template with the `static/index.html` file, you can add the following configuration:
 
@@ -28,7 +28,7 @@ export default {
 };
 ```
 
-## Function Usage
+## Function usage
 
 - **Type:**
 
diff --git a/website/docs/en/config/html/title.mdx b/website/docs/en/config/html/title.mdx
index 8dab839b95..ce7b4c4dec 100644
--- a/website/docs/en/config/html/title.mdx
+++ b/website/docs/en/config/html/title.mdx
@@ -9,7 +9,7 @@ Set the title tag of the HTML page.
 If the HTML template used in the current project already includes the `<title>` tag, the `html.title` will not take effect.
 :::
 
-## String Usage
+## String usage
 
 `html.title` can be directly set as a string:
 
@@ -27,7 +27,7 @@ The `title` tag generated in HTML will be:
 <title>Example</title>
 ```
 
-## Function Usage
+## Function usage
 
 - **Type:**
 
@@ -56,7 +56,7 @@ export default {
 };
 ```
 
-## Unset `<title>` Tag
+## Unset `<title>` tag
 
 When `html.title` is set to an empty string, Rsbuild will not inject the `<title>` tag:
 
diff --git a/website/docs/en/config/index.mdx b/website/docs/en/config/index.mdx
index f50107e839..28a113caea 100644
--- a/website/docs/en/config/index.mdx
+++ b/website/docs/en/config/index.mdx
@@ -1,4 +1,4 @@
-# Config Overview
+# Config overview
 
 This page lists all the configurations for Rsbuild. See ["Configure Rsbuild"](/guide/basic/configure-rsbuild) for detail.
 
diff --git a/website/docs/en/config/mode.mdx b/website/docs/en/config/mode.mdx
index 50945b49de..10c065501b 100644
--- a/website/docs/en/config/mode.mdx
+++ b/website/docs/en/config/mode.mdx
@@ -13,7 +13,7 @@ The value of `mode` does not affect the loading results of the `.env` file, as t
 Rsbuild CLI supports using the `--env-mode` option to specify the env mode. See ["Env mode"](/guide/advanced/env-vars#env-mode) for more details.
 :::
 
-## Default Values
+## Default values
 
 The default value of `mode` depends on the `process.env.NODE_ENV` environment variable:
 
@@ -29,7 +29,7 @@ export default {
 };
 ```
 
-### Command Line
+### Command line
 
 When using Rsbuild's command line:
 
@@ -43,7 +43,7 @@ When using Rsbuild's JavaScript API:
 - [rsbuild.startDevServer](/api/javascript-api/instance#rsbuildstartdevserver) and [rsbuild.createDevServer](/api/javascript-api/instance#rsbuildcreatedevserver) will set the default values of `NODE_ENV` and `mode` to `development`.
 - [rsbuild.build](/api/javascript-api/instance#rsbuildbuild) and [rsbuild.preview](/api/javascript-api/instance#rsbuildpreview) will set the default values of `NODE_ENV` and `mode` to `production`.
 
-## Development Mode
+## Development mode
 
 If the value of `mode` is `development`:
 
@@ -54,7 +54,7 @@ If the value of `mode` is `development`:
 - The `import.meta.env.DEV` in the source code will be replaced with `true`.
 - The `import.meta.env.PROD` in the source code will be replaced with `false`.
 
-## Production Mode
+## Production mode
 
 If the value of `mode` is `production`:
 
@@ -68,7 +68,7 @@ If the value of `mode` is `production`:
 - The `import.meta.env.DEV` in the source code will be replaced with `false`.
 - The `import.meta.env.PROD` in the source code will be replaced with `true`.
 
-## None Mode
+## None mode
 
 If the value of `mode` is `none`:
 
diff --git a/website/docs/en/config/output/asset-prefix.mdx b/website/docs/en/config/output/asset-prefix.mdx
index 34604fca60..fda48c1fb8 100644
--- a/website/docs/en/config/output/asset-prefix.mdx
+++ b/website/docs/en/config/output/asset-prefix.mdx
@@ -48,7 +48,7 @@ After the build, the URL of the JS file will be:
 <script defer src="./static/js/index.ebc4ff4f.js"></script>
 ```
 
-## Default Value
+## Default value
 
 The default value of `output.assetPrefix` is the same as [server.base](/config/server/base).
 
@@ -67,7 +67,7 @@ export default {
 };
 ```
 
-## Path Types
+## Path types
 
 assetPrefix can be set to the following types of paths:
 
diff --git a/website/docs/en/config/output/clean-dist-path.mdx b/website/docs/en/config/output/clean-dist-path.mdx
index 822358a3d4..6b29a96aed 100644
--- a/website/docs/en/config/output/clean-dist-path.mdx
+++ b/website/docs/en/config/output/clean-dist-path.mdx
@@ -5,7 +5,7 @@
 
 Whether to clean up all files under the output directory before the build starts (the output directory defaults to `dist`).
 
-## Default Behavior
+## Default behavior
 
 The default value of `output.cleanDistPath` is `'auto'`. If the output directory is a subdir of the project root path, Rsbuild will automatically clean all files under the build directory.
 
@@ -21,7 +21,7 @@ export default {
 };
 ```
 
-## Forced Switch
+## Forced switch
 
 You can set `cleanDistPath` to `true` to force it to be enabled, or set it to `false` to force it to be disabled.
 
diff --git a/website/docs/en/config/output/css-modules.mdx b/website/docs/en/config/output/css-modules.mdx
index b0c2eacc4c..f5107d099f 100644
--- a/website/docs/en/config/output/css-modules.mdx
+++ b/website/docs/en/config/output/css-modules.mdx
@@ -135,7 +135,7 @@ const localIdentName = isProd
 
 Sets the format of the class names generated by CSS Modules after compilation.
 
-### Default Value
+### Default value
 
 `localIdentName` has different default values in development and production.
 
@@ -149,7 +149,7 @@ import styles from './index.module.scss';
 console.log(styles.header);
 ```
 
-### Template String
+### Template string
 
 You can use the following template strings in `localIdentName`:
 
diff --git a/website/docs/en/config/output/dist-path.mdx b/website/docs/en/config/output/dist-path.mdx
index 8ee854ec5b..2aba63514e 100644
--- a/website/docs/en/config/output/dist-path.mdx
+++ b/website/docs/en/config/output/dist-path.mdx
@@ -55,7 +55,7 @@ Detail:
 - `media`: The output directory of media assets, such as videos.
 - `assets`: The output directory of other static assets. Such as the assets defined in [Extend Asset Types](/guide/basic/static-assets#extend-asset-types).
 
-### Root Directory
+### Root directory
 
 The `root` is the root directory of the build artifacts and can be specified as a relative or absolute path. If the value of `root` is a relative path, it will be appended to the project's root directory to form an absolute path.
 
diff --git a/website/docs/en/config/output/filename-hash.mdx b/website/docs/en/config/output/filename-hash.mdx
index 23c1ecbe4b..b5bb69c9de 100644
--- a/website/docs/en/config/output/filename-hash.mdx
+++ b/website/docs/en/config/output/filename-hash.mdx
@@ -31,7 +31,7 @@ dist/static/css/index.css
 dist/static/js/index.js
 ```
 
-### Hash Format
+### Hash format
 
 The default hash format is `contenthash:8`, which generates an 8-bit hash based on the content of the file.
 
diff --git a/website/docs/en/config/output/filename.mdx b/website/docs/en/config/output/filename.mdx
index 567af84949..cf3140d567 100644
--- a/website/docs/en/config/output/filename.mdx
+++ b/website/docs/en/config/output/filename.mdx
@@ -93,7 +93,7 @@ Usually, Rsbuild only set the filename hash in the production mode (i.e., when `
 If you set the filename hash in the development mode, it may cause HMR to fail (especially for CSS files). This is because every time the file content changes, the hash value changes, preventing bundler from reading the latest file content.
 :::
 
-## Template Strings
+## Template strings
 
 In the value of `output.filename`, you can use template strings to dynamically generate file names.
 
@@ -113,7 +113,7 @@ Common template strings include:
 
 :::
 
-## Filename of Async Modules
+## Filename of async modules
 
 When you import a module via dynamic import, the module will be bundled into a single file, and its default naming rules are as follows:
 
@@ -134,7 +134,7 @@ const { add } = await import(
 
 After specifying the module name as above, the generated file will be `dist/static/js/async/my-chunk-name.js`.
 
-## Using Function
+## Using function
 
 You can pass a function to `output.filename.js` or `output.filename.css`, allowing you to dynamically generate filenames based on file information:
 
@@ -169,7 +169,7 @@ export default {
 Except for `output.filename.js` and `output.filename.css`, other types of files currently do not support using functions.
 :::
 
-## Query Hash
+## Query hash
 
 If you need to generate hash values on the URL query of assets, you can refer to:
 
diff --git a/website/docs/en/config/output/inject-styles.mdx b/website/docs/en/config/output/inject-styles.mdx
index f43416e5c0..eb9c9574da 100644
--- a/website/docs/en/config/output/inject-styles.mdx
+++ b/website/docs/en/config/output/inject-styles.mdx
@@ -21,7 +21,7 @@ export default {
 
 When `output.injectStyles` is enabled, you can modify the options of `style-loader` through [tools.styleLoader](/config/tools/style-loader).
 
-### Usage Scenario
+### Usage scenario
 
 It is recommended to only enable the `injectStyles` option in development mode.
 
diff --git a/website/docs/en/config/output/inline-scripts.mdx b/website/docs/en/config/output/inline-scripts.mdx
index e3cc2027d2..6253bfbae1 100644
--- a/website/docs/en/config/output/inline-scripts.mdx
+++ b/website/docs/en/config/output/inline-scripts.mdx
@@ -65,7 +65,7 @@ And `dist/static/js/main.js` will be inlined in `index.html`:
 Setting `inlineScripts: true` is equivalent to setting [inlineScripts.enable](#enable) to `'auto'`. This indicates that inline scripts will only be enabled in production mode.
 :::
 
-### Script Tag Position
+### Script tag position
 
 When `output.inlineScripts` is used, it is recommended to set [html.inject](/config/html/inject) to `'body'`.
 
@@ -100,7 +100,7 @@ export default {
 The production filename includes a hash value by default, such as `static/js/main.18a568e5.js`. Therefore, in regular expressions, `\w+` is used to match the hash.
 :::
 
-### Using Function
+### Using function
 
 You can also set `output.inlineScripts` to a function that accepts the following parameters:
 
@@ -119,7 +119,7 @@ export default {
 };
 ```
 
-### Async Chunks
+### Async chunks
 
 When you use [dynamic import](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import) in JavaScript, Rspack will generate an async chunk. By default, `output.inlineScripts` will not inline async chunks into the HTML.
 
diff --git a/website/docs/en/config/output/inline-styles.mdx b/website/docs/en/config/output/inline-styles.mdx
index 11be39abb4..e810b88d10 100644
--- a/website/docs/en/config/output/inline-styles.mdx
+++ b/website/docs/en/config/output/inline-styles.mdx
@@ -84,7 +84,7 @@ export default {
 The production filename includes a hash value by default, such as `static/css/main.18a568e5.css`. Therefore, in regular expressions, `\w+` is used to match the hash.
 :::
 
-### Using Function
+### Using function
 
 You can also set `output.inlineStyles` to a function that accepts the following parameters:
 
diff --git a/website/docs/en/config/output/manifest.mdx b/website/docs/en/config/output/manifest.mdx
index edde16c85a..096b1f50ba 100644
--- a/website/docs/en/config/output/manifest.mdx
+++ b/website/docs/en/config/output/manifest.mdx
@@ -12,7 +12,7 @@ Configure how to generate the manifest file.
 
 The manifest file contains the information of all assets, and the mapping relationship between [entry module](/config/source/entry) and assets.
 
-## Basic Example
+## Basic example
 
 Enable the asset manifest:
 
@@ -47,7 +47,7 @@ After building, Rsbuild will generate a `dist/manifest.json` file:
 }
 ```
 
-## Manifest Structure
+## Manifest structure
 
 By default, the manifest file will be output in the following structure:
 
diff --git a/website/docs/en/config/output/override-browserslist.mdx b/website/docs/en/config/output/override-browserslist.mdx
index 205105ed7c..24d519cef3 100644
--- a/website/docs/en/config/output/override-browserslist.mdx
+++ b/website/docs/en/config/output/override-browserslist.mdx
@@ -15,7 +15,7 @@ In most cases, it is recommended to use the `.browserslistrc` file rather than t
 
 > For more details, see [Browserslist](/guide/advanced/browserslist).
 
-## Default Value
+## Default value
 
 If there is no `browserslist` configs defined in the project, nor `overrideBrowserslist` defined, then Rsbuild will set the default browserslist to:
 
diff --git a/website/docs/en/config/output/polyfill.mdx b/website/docs/en/config/output/polyfill.mdx
index 2c5aaed547..5d74d806c5 100644
--- a/website/docs/en/config/output/polyfill.mdx
+++ b/website/docs/en/config/output/polyfill.mdx
@@ -7,7 +7,7 @@ Control the injection mode of the polyfills.
 
 > Please refer to the [Polyfill Mode](/guide/advanced/browser-compatibility#polyfill-mode) for more details.
 
-## Optional Value
+## Optional value
 
 ### usage
 
diff --git a/website/docs/en/config/output/source-map.mdx b/website/docs/en/config/output/source-map.mdx
index 5cda033550..d28bbefe46 100644
--- a/website/docs/en/config/output/source-map.mdx
+++ b/website/docs/en/config/output/source-map.mdx
@@ -26,7 +26,7 @@ Used to set whether to generate source map files, and which format of source map
 Source map is an information file that saves the source code mapping relationship. It records each location of the compiled code and the corresponding pre-compilation location. With source map, you can directly view the source code when debugging the compiled code.
 :::
 
-## Default Behavior
+## Default behavior
 
 By default, the source map generation rules for Rsbuild are as follows:
 
@@ -61,7 +61,7 @@ export default {
 };
 ```
 
-## JS Source Map
+## JS source map
 
 The source map for JS files is controlled by `sourceMap.js` and can be configured by passing in all the source map formats supported by Rspack's [devtool](https://rspack.dev/config/devtool) option. Setting it to `false` will disable the source map.
 
@@ -94,7 +94,7 @@ export default {
 };
 ```
 
-## CSS Source Map
+## CSS source map
 
 The source map for CSS files is controlled by `sourceMap.css`. Setting it to `true` will enable the source map, while setting it to `false` will disable it.
 
diff --git a/website/docs/en/config/output/target.mdx b/website/docs/en/config/output/target.mdx
index a707d9fa5c..40368a3889 100644
--- a/website/docs/en/config/output/target.mdx
+++ b/website/docs/en/config/output/target.mdx
@@ -13,13 +13,13 @@ Setting the build target of Rsbuild.
 
 Rsbuild supports multiple build targets for running in different environments. After setting the target type, the default configuration of Rsbuild will change accordingly.
 
-## Default Target
+## Default target
 
 By default, the target is set to 'web' and will build outputs for running in the browser.
 
 Rsbuild will read the [Browserslist config](https://github.com/browserslist/browserslist) in the project to determine the range of browsers.
 
-## Optional Targets
+## Optional targets
 
 In addition to `'web'`, `target` can also be set to the following values:
 
@@ -36,7 +36,7 @@ export default {
 };
 ```
 
-## Parallel Builds
+## Parallel builds
 
 You can use [environments](/config/environments) to build multiple targets in parallel.
 
@@ -59,7 +59,7 @@ export default {
 };
 ```
 
-## Node Target
+## Node target
 
 Refers to the build target running in the Node.js environment, usually used in scenarios such as SSR.
 
@@ -72,7 +72,7 @@ When `target` is set to `'node'`, Rsbuild will:
 - Set the default value of Browserslist to `['node >= 16']`.
 - Set the default value of [output.emitCss](/config/output/emit-css) to `false`. This means that CSS code will not be extracted to separate files, but the id information of CSS Modules will be included in the bundle.
 
-### Node Addons
+### Node addons
 
 When `target` is set to `'node'`, Rsbuild allows you to import Node.js [Addons](https://nodejs.org/api/addons.html) in JavaScript files.
 
@@ -91,7 +91,7 @@ dist/index.js
 dist/addon.node
 ```
 
-## Web Worker Target
+## Web Workers target
 
 Refers to the build target running in the [Web Worker](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API) environment.
 
diff --git a/website/docs/en/config/performance/bundle-analyze.mdx b/website/docs/en/config/performance/bundle-analyze.mdx
index 95adb95b87..c87a302d2b 100644
--- a/website/docs/en/config/performance/bundle-analyze.mdx
+++ b/website/docs/en/config/performance/bundle-analyze.mdx
@@ -15,11 +15,11 @@ const defaultConfig = {
 };
 ```
 
-## Enable Bundle Analyze
+## Enable bundle analyze
 
 You have two ways to enable `webpack-bundle-analyzer` to analyze the size of the output files.
 
-### Via Environment Variable
+### Via environment variable
 
 Add the environment variable `BUNDLE_ANALYZE=true`, for example:
 
@@ -44,7 +44,7 @@ Since the Windows system does not support the above usage, you can also use [cro
 }
 ```
 
-### Via Configuration
+### Via configuration
 
 Configure `performance.bundleAnalyze` to enable it permanently:
 
@@ -56,7 +56,7 @@ export default {
 };
 ```
 
-### Analysis Result
+### Analysis result
 
 After enabling it, Rsbuild will generate an HTML file that analyzes the size of the output files, and print the following log in the Terminal:
 
@@ -68,7 +68,7 @@ You can manually open the file in the browser and view the detail of the bundle
 
 ![](https://assets.rspack.dev/rsbuild/assets/bundle-analyzer-example.png)
 
-## Override Default Configuration
+## Override default configuration
 
 You can override the default configuration through `performance.bundleAnalyze`, such as enabling the server mode:
 
@@ -85,7 +85,7 @@ export default {
 };
 ```
 
-## Size Types
+## Size types
 
 In the `webpack-bundle-analyzer` panel, you can control size types in the upper left corner (default is `Parsed`):
 
diff --git a/website/docs/en/config/performance/chunk-split.mdx b/website/docs/en/config/performance/chunk-split.mdx
index 89e233ce90..bb05f50684 100644
--- a/website/docs/en/config/performance/chunk-split.mdx
+++ b/website/docs/en/config/performance/chunk-split.mdx
@@ -20,7 +20,7 @@ Rsbuild supports the following chunk splitting strategies:
 - `single-vendor`: bundle all NPM packages into a single chunk.
 - `custom`: custom chunk splitting strategy.
 
-## Type Definition
+## Type definition
 
 The type of `performance.chunkSplit` is as follows:
 
@@ -51,7 +51,7 @@ interface SplitCustom extends BaseSplitRules {
 type ChunkSplit = BaseChunkSplit | SplitBySize | SplitCustom;
 ```
 
-### Default Strategy
+### Default strategy
 
 By default, Rsbuild uses the `split-by-experience` strategy. If you want to use other chunk splitting strategies, you can specify them through the `strategy` option, for example:
 
diff --git a/website/docs/en/config/performance/prefetch.mdx b/website/docs/en/config/performance/prefetch.mdx
index c18f2bc56a..6197a77e9f 100644
--- a/website/docs/en/config/performance/prefetch.mdx
+++ b/website/docs/en/config/performance/prefetch.mdx
@@ -53,7 +53,7 @@ The tags injected in HTML are as follows:
 </html>
 ```
 
-## Inject Manually
+## Inject manually
 
 The `performance.prefetch` can only inject the prefetch tags for static resources generated by Rsbuild. If you need to prefetch other resources, you can manually add tags through [html.tags](/config/html/tags) :
 
diff --git a/website/docs/en/config/performance/preload.mdx b/website/docs/en/config/performance/preload.mdx
index 3182722f28..fb737e4f1a 100644
--- a/website/docs/en/config/performance/preload.mdx
+++ b/website/docs/en/config/performance/preload.mdx
@@ -55,7 +55,7 @@ The tags injected in HTML are as follows:
 </html>
 ```
 
-## Inject Manually
+## Inject manually
 
 The `performance.preload` can only inject the preload tags for static resources generated by Rsbuild. If you need to preload other resources, you can manually add tags through [html.tags](/config/html/tags) :
 
diff --git a/website/docs/en/config/performance/print-file-size.mdx b/website/docs/en/config/performance/print-file-size.mdx
index 1229cbd8a7..21c97a39b9 100644
--- a/website/docs/en/config/performance/print-file-size.mdx
+++ b/website/docs/en/config/performance/print-file-size.mdx
@@ -17,7 +17,7 @@ type PrintFileSizeOptions =
 
 Whether to print the file sizes after production build.
 
-## Default Outputs
+## Default outputs
 
 The default output log is as follows:
 
@@ -31,7 +31,7 @@ The default output log is as follows:
   Total: 143.0 kB (gzip: 46.3 kB)
 ```
 
-## Disable Outputs
+## Disable outputs
 
 If you don't want to print any information, you can disable it by setting `printFileSize` to `false`:
 
diff --git a/website/docs/en/config/performance/remove-console.mdx b/website/docs/en/config/performance/remove-console.mdx
index 7bd4e98635..78db503be8 100644
--- a/website/docs/en/config/performance/remove-console.mdx
+++ b/website/docs/en/config/performance/remove-console.mdx
@@ -17,7 +17,7 @@ export default {
 };
 ```
 
-## Specific Type
+## Specific type
 
 You can also specify to remove only certain types of `console.[methodName]`, such as `console.log` and `console.warn`:
 
diff --git a/website/docs/en/config/plugins.mdx b/website/docs/en/config/plugins.mdx
index f4db0d9f89..87a7305a41 100644
--- a/website/docs/en/config/plugins.mdx
+++ b/website/docs/en/config/plugins.mdx
@@ -42,13 +42,13 @@ export default defineConfig({
 });
 ```
 
-## Execution Order
+## Execution order
 
 By default, plugins are executed in the order they appear in the `plugins` array. Built-in Rsbuild plugins are executed before user-registered plugins.
 
 When a plugin internally uses fields that control the order, such as `pre` and `post`, the execution order is adjusted based on them. See [Pre Plugins](/plugins/dev/core#pre-pluginss) for more details.
 
-## Nested Plugins
+## Nested plugins
 
 Rsbuild also supports adding nested plugins. You can pass in an array containing multiple plugins, similar to a plugin preset collection. This is particularly useful for implementing complex functionalities that require a combination of multiple plugins (such as framework integration).
 
@@ -62,7 +62,7 @@ export default {
 };
 ```
 
-## Local Plugins
+## Local plugins
 
 If your local code repository contains Rsbuild plugins, you can import them using relative paths.
 
@@ -75,7 +75,7 @@ export default defineConfig({
 });
 ```
 
-## Plugin Options
+## Plugin options
 
 If a plugin provides custom options, you can pass the configurations through the plugin function's parameters.
 
@@ -122,7 +122,7 @@ export default {
 };
 ```
 
-## Rspack Plugins
+## Rspack plugins
 
 The `plugins` option is used to register Rsbuild plugins. If you need to register Rspack or Webpack plugins, please use [tools.rspack](/config/tools/rspack).
 
diff --git a/website/docs/en/config/resolve/alias.mdx b/website/docs/en/config/resolve/alias.mdx
index 5437ab01c9..8005111636 100644
--- a/website/docs/en/config/resolve/alias.mdx
+++ b/website/docs/en/config/resolve/alias.mdx
@@ -24,7 +24,7 @@ For TypeScript projects, you only need to configure [compilerOptions.paths](http
 In versions prior to Rsbuild 1.1.7, you can use the `source.alias` to set alias, but it will be removed in the next major version.
 :::
 
-## Object Type
+## Object type
 
 The `alias` can be an Object, and the relative path will be automatically converted to absolute path.
 
@@ -40,7 +40,7 @@ export default {
 
 With above configuration, if `@common/Foo.tsx` is import in the code, it will be mapped to the `<project>/src/common/Foo.tsx` path.
 
-## Function Type
+## Function type
 
 The `alias` can be a function, it will accept the previous alias object, and you can modify it.
 
@@ -113,7 +113,7 @@ export default {
 };
 ```
 
-## Exact Matching
+## Exact matching
 
 By default, `resolve.alias` will automatically match sub-paths, for example, with the following configuration:
 
@@ -179,7 +179,7 @@ When using alias to handle npm packages, please be aware of whether different ma
 
 For example, if a module or npm dependency in your project uses the React 19 API, and you alias React to version 17, the module will not be able to reference the React 19 API, resulting in code exceptions.
 
-## Handling Loader
+## Handling loader
 
 `resolve.alias` does not support creating aliases for loaders.
 
diff --git a/website/docs/en/config/resolve/extensions.mdx b/website/docs/en/config/resolve/extensions.mdx
index 370a90c6bc..0517da7185 100644
--- a/website/docs/en/config/resolve/extensions.mdx
+++ b/website/docs/en/config/resolve/extensions.mdx
@@ -31,7 +31,7 @@ export default {
 };
 ```
 
-## Rspack Config
+## Rspack config
 
 `resolve.extensions` is provided by Rspack, see [Rspack - resolve.extensions](https://rspack.dev/config/resolve#resolveextensions).
 
diff --git a/website/docs/en/config/security/nonce.mdx b/website/docs/en/config/security/nonce.mdx
index 6b901e1193..1b52cacb32 100644
--- a/website/docs/en/config/security/nonce.mdx
+++ b/website/docs/en/config/security/nonce.mdx
@@ -35,7 +35,7 @@ export default {
 
 Typically, we can define a fixed value in the project, and replace it with a random value on downstream servers such as Nginx, Web Server, gateway, etc.
 
-## Scope of Effect
+## Scope of effect
 
 The `security.nonce` config adds the nonce attribute to the following tags:
 
diff --git a/website/docs/en/config/server/https.mdx b/website/docs/en/config/server/https.mdx
index f020c28cb6..35f75f1cf0 100644
--- a/website/docs/en/config/server/https.mdx
+++ b/website/docs/en/config/server/https.mdx
@@ -31,7 +31,7 @@ HTTPS:
 Rsbuild enables HTTP/2 server by default. However, when you use [server.proxy](/config/server/proxy), the server will downgrade to HTTP/1, because the underlying `http-proxy` does not support HTTP/2.
 :::
 
-## Set Certificate
+## Set certificate
 
 You can manually pass in the certificate and the private key required in the `server.https` option. This parameter will be directly passed to the `createServer` method of the https module in Node.js.
 
diff --git a/website/docs/en/config/server/print-urls.mdx b/website/docs/en/config/server/print-urls.mdx
index 4148616d0c..7c1a30982c 100644
--- a/website/docs/en/config/server/print-urls.mdx
+++ b/website/docs/en/config/server/print-urls.mdx
@@ -29,7 +29,7 @@ By default, when you start the dev server or preview server, Rsbuild will print
   ➜ Network:  http://192.168.0.1:3000
 ```
 
-## Custom Logging
+## Custom logging
 
 `server.printUrls` can be set to a function, with parameters including `port`, `protocol`, `urls` and `routes`.
 
@@ -54,7 +54,7 @@ Output:
   ➜ Network:  http://192.168.0.1:3000/base/
 ```
 
-### Fully Customizable
+### Fully customizable
 
 If the `printUrls` function does not return a value, Rsbuild will not print the server's URL addresses. You can customize the log content based on the parameters and output it to the terminal yourself.
 
@@ -70,7 +70,7 @@ export default {
 };
 ```
 
-### MPA Output
+### MPA output
 
 If the current project contains multiple pages, you can generate a separate URL for each page based on the `routes` parameter.
 
@@ -92,7 +92,7 @@ export default {
 };
 ```
 
-## Disable Output
+## Disable output
 
 Setting `server.printUrls` to `false` will prevent Rsbuild from printing the server URLs.
 
@@ -104,7 +104,7 @@ export default {
 };
 ```
 
-### HTML Disabled
+### HTML disabled
 
 If [tools.htmlPlugin](/config/tools/html-plugin) is set to `false`, Rsbuild will not generate HTML files or output the server URL.
 
diff --git a/website/docs/en/config/server/proxy.mdx b/website/docs/en/config/server/proxy.mdx
index e13629c2e6..75201598ba 100644
--- a/website/docs/en/config/server/proxy.mdx
+++ b/website/docs/en/config/server/proxy.mdx
@@ -7,7 +7,7 @@ Configure proxy rules for the dev server or preview server to proxy requests to
 
 ## Example
 
-### Basic Usage
+### Basic usage
 
 ```js
 export default {
@@ -37,7 +37,7 @@ export default {
 };
 ```
 
-### Path Rewrite
+### Path rewrite
 
 If you don't want `/api` to be passed along, we need to rewrite the path:
 
diff --git a/website/docs/en/config/server/public-dir.mdx b/website/docs/en/config/server/public-dir.mdx
index 2aa3795596..400775fc97 100644
--- a/website/docs/en/config/server/public-dir.mdx
+++ b/website/docs/en/config/server/public-dir.mdx
@@ -91,7 +91,7 @@ export default {
 
 Note that setting the value of `copyOnBuild` to false means that when you run `rsbuild preview` for a production preview, you will not be able to access the corresponding static resources.
 
-#### Node Target
+#### Node target
 
 By default, when [output.target](/config/output/target) is `'node'`, Rsbuild will not copy files from the public directory.
 
@@ -138,7 +138,7 @@ export default {
 
 Note that the `watch` option is only valid in development mode. If [dev.hmr](/config/dev/hmr) and [dev.liveReload](/config/dev/live-reload) are both set to false, `watch` will be ignored.
 
-## Multiple Directories
+## Multiple directories
 
 The `server.publicDir` can be configured as an array, allowing you to serve multiple directories as static assets folders:
 
diff --git a/website/docs/en/config/source/entry.mdx b/website/docs/en/config/source/entry.mdx
index 33dab10ad6..3cb49a27a0 100644
--- a/website/docs/en/config/source/entry.mdx
+++ b/website/docs/en/config/source/entry.mdx
@@ -52,7 +52,7 @@ The generated directory structure is as follows:
 
 If you do not need to generate HTML files, you can set [tools.htmlPlugin](/config/tools/html-plugin) to `false` to disable this behavior.
 
-## Description Object
+## Description object
 
 `source.entry` also supports Rspack's entry description object. For example:
 
diff --git a/website/docs/en/config/source/exclude.mdx b/website/docs/en/config/source/exclude.mdx
index c5d23ab557..309d66c211 100644
--- a/website/docs/en/config/source/exclude.mdx
+++ b/website/docs/en/config/source/exclude.mdx
@@ -19,7 +19,7 @@ export default {
 
 > Refer to [source.include](/config/source/include) to learn more.
 
-### Not compiled vs Not bundled
+### Not compiled vs not bundled
 
 `source.exclude` is used to specify JavaScript/TypeScript files that do not need to be compiled. This means that these files will not be translated by SWC or Babel, but they will still be bundled into the outputs (if referenced).
 
diff --git a/website/docs/en/config/source/include.mdx b/website/docs/en/config/source/include.mdx
index ac9ab5a253..00a3f6e079 100644
--- a/website/docs/en/config/source/include.mdx
+++ b/website/docs/en/config/source/include.mdx
@@ -30,7 +30,7 @@ export default {
 };
 ```
 
-## Compile npm Packages
+## Compile npm packages
 
 A typical usage scenario is to compile npm packages under node_modules, because some third-party dependencies have ESNext syntax, which may cause them to fail to run on low-version browsers. You can solve the problem by using this config to specify the dependencies that need to be compiled.
 
@@ -65,7 +65,7 @@ The above two methods match the absolute paths of files using "path prefixes" an
 In the regular expression example above, we use `[\\/]` to match the path separator because different operating systems use different path separators. Using `[\\/]` ensures that the paths can be matched in macOS, Linux and Windows.
 :::
 
-## Compile Sub Dependencies
+## Compile sub dependencies
 
 When you compile an npm package via `source.include`, Rsbuild will only compile the matching module by default, not the **Sub Dependencies** of the module.
 
@@ -82,7 +82,7 @@ export default {
 };
 ```
 
-## Compile Libraries in Monorepo
+## Compile libraries in monorepo
 
 When developing in Monorepo, if you need to refer to the source code of other libraries in Monorepo, you can add the corresponding library to `source.include`:
 
@@ -104,7 +104,7 @@ export default {
 };
 ```
 
-## Matching Symlink
+## Matching symlink
 
 If you match a module that is symlinked to the current project, then you need to match the **real path** of the module, not the symlinked path.
 
diff --git a/website/docs/en/config/source/pre-entry.mdx b/website/docs/en/config/source/pre-entry.mdx
index d3c9218540..429b3f0076 100644
--- a/website/docs/en/config/source/pre-entry.mdx
+++ b/website/docs/en/config/source/pre-entry.mdx
@@ -5,7 +5,7 @@
 
 Add a script before the entry file of each page. This script will be executed before the page code. It can be used to execute global logics, such as injecting polyfills, setting global styles, etc.
 
-## Add a Single Script
+## Add a single script
 
 First create a `src/polyfill.ts` file:
 
@@ -25,7 +25,7 @@ export default {
 
 Re-run the compilation and visit any page, you can see that the code in `src/polyfill.ts` has been executed, and the `I am a polyfill` is logged in the console.
 
-## Add Global Style
+## Add global style
 
 You can also configure the global style through `source.preEntry`, this CSS code will be loaded earlier than the page code, such as introducing a `normalize.css` file:
 
@@ -37,7 +37,7 @@ export default {
 };
 ```
 
-## Add Multiple Scripts
+## Add multiple scripts
 
 You can add multiple scripts by setting `preEntry` to an array, and they will be executed in array order:
 
diff --git a/website/docs/en/config/source/transform-import.mdx b/website/docs/en/config/source/transform-import.mdx
index 2b567ef4c6..97c0f565c2 100644
--- a/website/docs/en/config/source/transform-import.mdx
+++ b/website/docs/en/config/source/transform-import.mdx
@@ -254,7 +254,7 @@ The following formats are supported:
 
 Customize the transformed style path, the usage is consistent with `customName`.
 
-## Function Type
+## Function type
 
 The `transformImport` can be a function, it will accept the previous value, and you can modify it.
 
diff --git a/website/docs/en/config/tools/css-loader.mdx b/website/docs/en/config/tools/css-loader.mdx
index 801228a8a6..75125515d5 100644
--- a/website/docs/en/config/tools/css-loader.mdx
+++ b/website/docs/en/config/tools/css-loader.mdx
@@ -15,7 +15,7 @@ Rsbuild uses [css-loader](https://github.com/webpack-contrib/css-loader) by defa
 If you need to modify the options related to CSS Modules, it is recommended to use the [output.cssModules](/config/output/css-modules) config first.
 :::
 
-### Object Type
+### Object type
 
 When this value is an Object, it is merged with the default config via deep merge. For example:
 
@@ -31,7 +31,7 @@ export default {
 };
 ```
 
-### Function Type
+### Function type
 
 When the value is a Function, the default config is passed in as the first parameter. You can modify the config object directly, or return an object as the final config. For example:
 
diff --git a/website/docs/en/config/tools/html-plugin.mdx b/website/docs/en/config/tools/html-plugin.mdx
index e5d9301c4e..da7b06c44b 100644
--- a/website/docs/en/config/tools/html-plugin.mdx
+++ b/website/docs/en/config/tools/html-plugin.mdx
@@ -26,7 +26,7 @@ If you need to modify options such as `title`, `template`, `templateParameters`,
 This is because Rsbuild provides some internal optimization processing for these HTML configurations. For example, if the HTML template used by the current project already contains the `<title>` tag, then `html.title` will not take effect.
 :::
 
-## Object Type
+## Object type
 
 When `tools.htmlPlugin` is `Object` type, the value will be merged with the default config via `Object.assign`.
 
@@ -40,7 +40,7 @@ export default {
 };
 ```
 
-## Function Type
+## Function type
 
 When `tools.htmlPlugin` is a Function:
 
@@ -74,7 +74,7 @@ export default {
 
 ## Example
 
-### Modify HTML File Name
+### Modify HTML file name
 
 The `filename` option can be used to modify the file name of the HTML output.
 
@@ -92,6 +92,6 @@ export default {
 };
 ```
 
-## HTML Minification
+## HTML minification
 
 Rsbuild currently does not minify HTML files. If you need to minify HTML files, you can use the [rsbuild-plugin-html-minifier-terser plugin](https://github.com/rspack-contrib/rsbuild-plugin-html-minifier-terser).
diff --git a/website/docs/en/config/tools/lightningcss-loader.mdx b/website/docs/en/config/tools/lightningcss-loader.mdx
index 2434fa51e8..0ae289f653 100644
--- a/website/docs/en/config/tools/lightningcss-loader.mdx
+++ b/website/docs/en/config/tools/lightningcss-loader.mdx
@@ -16,7 +16,7 @@ const defaultOptions = {
 
 You can set the options for [builtin:lightningcss-loader](https://rspack.dev/guide/features/builtin-lightningcss-loader) through `tools.lightningcssLoader`.
 
-## Object Type
+## Object type
 
 When `tools.lightningcssLoader` is an object, it will be merged with the default configuration using `Object.assign`.
 
@@ -34,7 +34,7 @@ export default {
 };
 ```
 
-## Function Type
+## Function type
 
 When `tools.lightningcssLoader` is a function, the default options will be passed in as the first parameter. You can directly modify this object or return a new object as the final options to be used. For example:
 
diff --git a/website/docs/en/config/tools/postcss.mdx b/website/docs/en/config/tools/postcss.mdx
index fd1cc51573..a15e8dc15f 100644
--- a/website/docs/en/config/tools/postcss.mdx
+++ b/website/docs/en/config/tools/postcss.mdx
@@ -14,7 +14,7 @@ const defaultOptions = {
 
 Rsbuild integrates PostCSS by default, you can configure [postcss-loader](https://github.com/webpack-contrib/postcss-loader) through `tools.postcss`.
 
-## Function Type
+## Function type
 
 When `tools.postcss` is a function, the default options will be passed in as the first parameter. You can directly modify this object or return a new object as the final options to be used. For example:
 
@@ -73,7 +73,7 @@ export default {
 };
 ```
 
-## Object Type
+## Object type
 
 When `tools.postcss` is an object, it will be merged with the default configuration using `Object.assign`. Note that `Object.assign` is a shallow copy and will completely overwrite the built-in `presets` or `plugins` array, please use it with caution.
 
@@ -113,7 +113,7 @@ export default {
 
 ## Practice
 
-### Multiple PostCSS Options
+### Multiple PostCSS options
 
 `tools.postcss.postcssOptions` can be set to a function, which receives the Rspack's `loaderContext` as a parameter. This allows you to use different PostCSS options for different file paths.
 
@@ -144,11 +144,11 @@ If the project contains a `postcss.config.*` config file, its content will be me
 
 ## Notes
 
-### PostCSS Version
+### PostCSS version
 
 Rsbuild uses the PostCSS v8. When you use third-party PostCSS plugins, please pay attention to whether the PostCSS version is compatible. Some legacy plugins may not work in PostCSS v8.
 
-### PostCSS Config Loading
+### PostCSS config loading
 
 Rsbuild uses [postcss-load-config](https://github.com/postcss/postcss-load-config) to load PostCSS config files and merge them with the default config.
 
diff --git a/website/docs/en/config/tools/rspack.mdx b/website/docs/en/config/tools/rspack.mdx
index 5dea709c2e..8c230be191 100644
--- a/website/docs/en/config/tools/rspack.mdx
+++ b/website/docs/en/config/tools/rspack.mdx
@@ -9,7 +9,7 @@
 The built-in Rspack config in Rsbuild may change with iterations, and these changes won't be reflected in semver. Therefore, your custom config may become invalid when you upgrade Rsbuild.
 :::
 
-## Object Type
+## Object type
 
 `tools.rspack` can be configured as an object to be deep merged with the built-in Rspack configuration through [webpack-merge](https://github.com/survivejs/webpack-merge).
 
@@ -46,7 +46,7 @@ export default {
 
 If you need to override a configuration rather than merge it with the default value, you can use the function type of `tools.rspack`.
 
-## Function Type
+## Function type
 
 `tools.rspack` can be configured as a function. The first parameter of this function is the built-in Rspack configuration object, you can modify this object, and then return it. For example:
 
diff --git a/website/docs/en/config/tools/style-loader.mdx b/website/docs/en/config/tools/style-loader.mdx
index 80c34e8779..feedcb003e 100644
--- a/website/docs/en/config/tools/style-loader.mdx
+++ b/website/docs/en/config/tools/style-loader.mdx
@@ -7,7 +7,7 @@ The config of [style-loader](https://github.com/webpack-contrib/style-loader) ca
 
 It is worth noting that Rsbuild does not enable `style-loader` by default. You can use [output.injectStyles](/config/output/inject-styles) config to enable it.
 
-## Object Type
+## Object type
 
 When `tools.styleLoader` is an object, it will be merged with the default configuration using `Object.assign`.
 
@@ -21,7 +21,7 @@ export default {
 };
 ```
 
-## Function Type
+## Function type
 
 When `tools.styleLoader` is a function, the default options will be passed in as the first parameter. You can directly modify this object or return a new object as the final options to be used. For example:
 
diff --git a/website/docs/en/config/tools/swc.mdx b/website/docs/en/config/tools/swc.mdx
index 7475a414bc..426f463db2 100644
--- a/website/docs/en/config/tools/swc.mdx
+++ b/website/docs/en/config/tools/swc.mdx
@@ -22,7 +22,7 @@ You can set the options of [builtin:swc-loader](https://rspack.dev/guide/feature
 
 > Refer to [Configure SWC](/guide/basic/configure-swc) for more details.
 
-## Object Type
+## Object type
 
 `tools.swc` can be configured as an object, this object will be deeply merged with the built-in `builtin:swc-loader` option.
 
@@ -38,7 +38,7 @@ export default {
 };
 ```
 
-## Function Type
+## Function type
 
 `tools.swc` can also be configured as a function, this function takes one argument, which is the built-in `builtin:swc-loader` option. You can modify this object then return a new config. For example:
 
diff --git a/website/docs/en/guide/advanced/alias.mdx b/website/docs/en/guide/advanced/alias.mdx
index 2db27daf3e..25618b9312 100644
--- a/website/docs/en/guide/advanced/alias.mdx
+++ b/website/docs/en/guide/advanced/alias.mdx
@@ -1,4 +1,4 @@
-# Path Aliases
+# Path aliases
 
 Path aliases allow developers to define aliases for modules, making it easier to reference them in code. This can be useful when you want to use a short, easy-to-remember name for a module instead of a long, complex path.
 
@@ -53,13 +53,13 @@ export default {
 
 Rsbuild provides the [resolve.alias](/config/resolve/alias) configuration option, which corresponds to the webpack/Rspack native [resolve.alias](https://rspack.dev/config/resolve#resolvealias) configuration. You can configure this option using an object or a function.
 
-### Use Cases
+### Use cases
 
 Since the `paths` configuration in `tsconfig.json` is written in a static JSON file, it lacks dynamism.
 
 The `resolve.alias` configuration can address this limitation by allowing you to dynamically set the `resolve.alias` using JavaScript code, such as based on environment variables.
 
-### Object Usage
+### Object usage
 
 You can configure `resolve.alias` using an object, where the relative paths will be automatically resolved to absolute paths.
 
@@ -77,7 +77,7 @@ export default {
 
 After configuring, if you reference `@common/Foo.tsx` in your code, it will be mapped to the `<project>/src/common/Foo.tsx` path.
 
-### Function Usage
+### Function usage
 
 You can also configure `resolve.alias` as a function, which receives the built-in `alias` object and allows you to modify it.
 
diff --git a/website/docs/en/guide/advanced/browser-compatibility.mdx b/website/docs/en/guide/advanced/browser-compatibility.mdx
index 50b21106fe..c8c9a25289 100644
--- a/website/docs/en/guide/advanced/browser-compatibility.mdx
+++ b/website/docs/en/guide/advanced/browser-compatibility.mdx
@@ -1,4 +1,4 @@
-# Browser Compatibility
+# Browser compatibility
 
 This chapter introduces how to use the capabilities provided by Rsbuild to deal with browser compatibility issues.
 
@@ -74,7 +74,7 @@ If the engine encounters an unrecognized syntax when converting to AST, it will
 
 If the code is successfully converted to AST, the engine will convert the AST into executable code and execute it normally inside the engine.
 
-### API Polyfill
+### API polyfill
 
 JavaScript is an interpreted scripting language, unlike compiled languages like Rust. Rust will check the calls in the code during the compilation phase, and JavaScript does not know whether the function called by this line of code exists before it actually runs to a certain line of code, so some errors will only appear at runtime.
 
@@ -187,7 +187,7 @@ Rsbuild compiles JavaScript code using SWC and supports injecting polyfills such
 
 In different usage scenarios, you may need different polyfill solutions. Rsbuild provides [output.polyfill](/config/output/polyfill) config to switch between different polyfill modes.
 
-### Default Behavior
+### Default behavior
 
 Rsbuild does not inject any polyfills by default:
 
@@ -242,7 +242,7 @@ export default {
 };
 ```
 
-### UA Polyfill
+### UA polyfill
 
 Cloudflare provides a [polyfill service](https://cdnjs.cloudflare.com/polyfill/) that can automatically generate polyfill bundle based on the user's browser User-Agent.
 
diff --git a/website/docs/en/guide/advanced/browserslist.mdx b/website/docs/en/guide/advanced/browserslist.mdx
index e46a1bcb7f..faf2843ff5 100644
--- a/website/docs/en/guide/advanced/browserslist.mdx
+++ b/website/docs/en/guide/advanced/browserslist.mdx
@@ -2,7 +2,7 @@
 
 Rsbuild supports using [Browserslist](https://browsersl.ist/) to specify which browsers should be supported in your Web application.
 
-## What is Browserslist
+## What is browserslist
 
 Since different browsers support ECMAScript and CSS differently, developers need to set the correct browser range for web applications.
 
@@ -10,7 +10,7 @@ Since different browsers support ECMAScript and CSS differently, developers need
 
 When you specify a browser range through Browserslist, Rsbuild will compile JavaScript and CSS code to the specified syntax.
 
-## Polyfill Injection
+## Polyfill injection
 
 If you enabled [output.polyfill](/config/output/polyfill), Rsbuild will also inject the corresponding polyfill code based on browserslist. **When you only need to support more modern browsers, the build process will introduce less compatibility code and polyfills, and the performance of the page will be better.**
 
@@ -26,7 +26,7 @@ For example, when you need to be compatible with IE11 browser, Rsbuild will comp
 
 > Please refer to [Browser Compatibility](/guide/advanced/browser-compatibility) for more information.
 
-## Set Browserslist
+## Set browserslist
 
 You can set the Browserslist value in the `package.json` or `.browserslistrc` file in the root directory of the current project.
 
@@ -56,13 +56,13 @@ last 2 versions
 not dead
 ```
 
-### Effective Scope
+### Effective scope
 
 By default, the `.browserslistrc` file only takes effect for browser-side bundles, including the `web` and `web-worker` target types.
 
 When you are building multiple targets at the same time, for example if the targets contains both `web` and `node`, only the `web` bundles will be affected by the `.browserslistrc` file. If you want to make changes to the `node` bundles, you can use the `output.overrideBrowserslist` configuration below.
 
-### Set by Env
+### Set by env
 
 You can set different browserslist based on `NODE_ENV` to specify different browser ranges for development and production.
 
@@ -123,7 +123,7 @@ export default {
 
 In most cases, it is recommended to use the `.browserslistrc` file rather than the `overrideBrowserslist` config. Because the `.browserslistrc` file is the official config file, it is more general and can be recognized by other libraries in the community.
 
-## Commonly used Browserslist
+## Commonly used browserslist
 
 The following are some commonly used Browserslist, you can choose according to your project type.
 
@@ -186,11 +186,11 @@ not dead
 not op_mini all
 ```
 
-## Default Browserslist
+## Default browserslist
 
 Rsbuild will set different default values of Browserslist according to [output.target](/config/output/target), but we recommend that you explicitly set Browserslist in your project, which will make the compatible scope of the project more clear.
 
-### Web Target
+### Web target
 
 The default values of web target are as follows:
 
@@ -203,7 +203,7 @@ safari >= 14
 
 Under this browser range, JavaScript code will be compatible with browsers that support [native ES Modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules).
 
-### Node Target
+### Node target
 
 Node target will be compatible with Node.js 16.0 by default.
 
@@ -211,7 +211,7 @@ Node target will be compatible with Node.js 16.0 by default.
 node >= 16
 ```
 
-### Web Worker Target
+### Web Workers target
 
 The default Browserslist of the web worker target is consistent with the web target.
 
@@ -222,7 +222,7 @@ firefox >= 78
 safari >= 14
 ```
 
-### Service Worker Target
+### Service Worker target
 
 The default Browserslist of the service worker target is consistent with the web target.
 
diff --git a/website/docs/en/guide/advanced/env-vars.mdx b/website/docs/en/guide/advanced/env-vars.mdx
index c306058fd2..7a66c75442 100644
--- a/website/docs/en/guide/advanced/env-vars.mdx
+++ b/website/docs/en/guide/advanced/env-vars.mdx
@@ -1,10 +1,10 @@
-# Environment Variables
+# Environment variables
 
 Rsbuild supports injecting env variables or expressions into the code during build, which is helpful for distinguishing the running environment or replacing constants.
 
 This chapter introduces how to use env variables in Rsbuild.
 
-## Default Variables
+## Default variables
 
 Rsbuild by default injects the some env variables into the code using [source.define](#using-define). These will be replaced with specified values during the build:
 
@@ -190,7 +190,7 @@ When a `.env` file exists in the project root directory, Rsbuild CLI will automa
 
 You can access these env variables through `import.meta.env.[name]` or `process.env.[name]`.
 
-### File Types
+### File types
 
 Rsbuild supports reading the following types of env files:
 
@@ -205,7 +205,7 @@ Rsbuild supports reading the following types of env files:
 
 If several of the above files exist at the same time, they will all be loaded, with the files listed at the bottom of the table having higher priority.
 
-### Env Mode
+### Env mode
 
 Rsbuild also supports reading `.env.[mode]` and `.env.[mode].local` files. You can specify the env mode using the `--env-mode <mode>` flag.
 
@@ -229,7 +229,7 @@ It is recommended to use `--env-mode` to set the env mode, and not to modify `pr
 
 :::
 
-### Env Directory
+### Env directory
 
 By default, the `.env` file is located in the root directory of the project. You can specify the env directory by using the `--env-dir <dir>` option in the CLI.
 
@@ -273,7 +273,7 @@ console.log(import.meta.env.BAR); // '2'
 console.log(process.env.BAR); // '2'
 ```
 
-### Manually Load Env
+### Manually load env
 
 If you are not using the Rsbuild CLI and are using the Rsbuild [JavaScript API](/api/start/index) instead, you will need to manually call the [loadEnv](/api/javascript-api/core#loadenv) method to read env variables and inject them into the code via the [source.define](/config/source/define) config.
 
@@ -293,7 +293,7 @@ const mergedConfig = mergeRsbuildConfig(
 );
 ```
 
-## Public Variables
+## Public variables
 
 All env variables starting with `PUBLIC_` can be accessed in client code. For example, if the following variables are defined:
 
@@ -319,7 +319,7 @@ console.log(process.env.PASSWORD); // -> undefined
 
 :::
 
-### Replacement Scope
+### Replacement scope
 
 Public variables will replace identifiers in the client code, with the replacement scope including:
 
@@ -334,7 +334,7 @@ Note that public variables will not replace identifiers in the following files:
 
 - CSS files, such as `.css`, `.scss`, `.less`, etc.
 
-### Custom Prefix
+### Custom prefix
 
 Rsbuild provides the [loadEnv](/api/javascript-api/core#loadenv) method, which can inject env variables with any prefix into client code.
 
@@ -358,7 +358,7 @@ By using [source.define](/config/source/define), you can replace global identifi
 
 `define` is similar to the macro definition capabilities provided by other languages. It is often used to inject env variables and other information to the code during build time.
 
-### Replace Identifiers
+### Replace identifiers
 
 The most basic use case for `define` is to replace global identifiers in compile time.
 
@@ -384,7 +384,7 @@ For more about `source.define`, just refer to [API References](/config/source/de
 The environment variable `NODE_ENV` shown in the example above is already injected by the Rsbuild, and you usually do not need to configure it manually.
 :::
 
-### Identifiers Matching
+### Identifiers matching
 
 Note that `source.define` can only match complete global identifiers. You can think of it as a text replacement process.
 
@@ -430,7 +430,7 @@ If the above usage is adopted, the following problems will be caused:
 
 Therefore, please inject the env variables on `process.env` according to actual needs and avoid replacing them in its entirety.
 
-## Type Declarations
+## Type declarations
 
 When you access an environment variable in a TypeScript file, TypeScript may prompt that the variable lacks a type definition, and you need to add the corresponding type declaration.
 
@@ -480,7 +480,7 @@ declare namespace NodeJS {
 }
 ```
 
-## Tree Shaking
+## Tree shaking
 
 `define` can also be used to mark dead code to assist the Rspack with tree shaking optimization.
 
diff --git a/website/docs/en/guide/advanced/environments.mdx b/website/docs/en/guide/advanced/environments.mdx
index 0cdc482fc1..a2ab5a312f 100644
--- a/website/docs/en/guide/advanced/environments.mdx
+++ b/website/docs/en/guide/advanced/environments.mdx
@@ -64,7 +64,7 @@ export default {
 };
 ```
 
-### Config Merging
+### Config merging
 
 If you configure `environments`, Rsbuild will merge the config in `environments` with the outer base config. When merging, the config in `environments` has higher priority.
 
@@ -75,7 +75,7 @@ In the example above, after merging the configs, Rsbuild generates two standalon
 
 Then, Rsbuild will use these environments configs to internally generate two Rspack configs and execute a single build using Rspack’s MultiCompiler.
 
-### Debug Config
+### Debug config
 
 When you execute the command `npx rsbuild inspect` in the project root directory, you will find the following output:
 
diff --git a/website/docs/en/guide/advanced/hmr.mdx b/website/docs/en/guide/advanced/hmr.mdx
index 3015f7af76..baab166612 100644
--- a/website/docs/en/guide/advanced/hmr.mdx
+++ b/website/docs/en/guide/advanced/hmr.mdx
@@ -1,4 +1,4 @@
-# Hot Module Replacement
+# Hot module replacement
 
 Hot Module Replacement (HMR) exchanges, adds, or removes modules while an application is running, without a full reload. This can significantly speed up development in a few ways:
 
@@ -6,7 +6,7 @@ Hot Module Replacement (HMR) exchanges, adds, or removes modules while an applic
 - Save valuable development time by only updating what's changed.
 - Instantly update the browser when modifications are made to CSS / JS in the source code, which is almost comparable to changing styles directly in the browser's dev tools.
 
-## HMR Toggle
+## HMR toggle
 
 Rsbuild has built-in support for HMR, which is enabled by default in development mode.
 
@@ -20,7 +20,7 @@ export default {
 };
 ```
 
-If you need to disable both HMR and liveReload, you can set both [dev.hmr](/config/dev/hmr) and [dev.liveReload](/config/dev/live-reload) to `false`. Then, no Web Socket requests will be made to the dev server on the page, and the page will not automatically refresh when files change.
+If you need to disable both HMR and liveReload, you can set both [dev.hmr](/config/dev/hmr) and [dev.liveReload](/config/dev/live-reload) to `false`. Then, no WebSocket requests will be made to the dev server on the page, and the page will not automatically refresh when files change.
 
 ```js title="rsbuild.config.ts"
 export default {
@@ -48,7 +48,7 @@ export default {
 };
 ```
 
-## File Watching
+## File watching
 
 By default, Rsbuild does not watching files in the `.git/` and `node_modules/` directories. When files in these directories changed, Rsbuild will not trigger a rebuild. This helps to reduce memory usage and improve build performance.
 
diff --git a/website/docs/en/guide/advanced/module-federation.mdx b/website/docs/en/guide/advanced/module-federation.mdx
index cc46223795..a4a38234e9 100644
--- a/website/docs/en/guide/advanced/module-federation.mdx
+++ b/website/docs/en/guide/advanced/module-federation.mdx
@@ -4,7 +4,7 @@ Module Federation is an architectural pattern for JavaScript application decompo
 
 The Rspack team works closely with the Module Federation development team and provides first-class support for Module Federation.
 
-## Use Cases
+## Use cases
 
 Module Federation has several typical use cases, including:
 
@@ -68,7 +68,7 @@ export default defineConfig({
 });
 ```
 
-## Example Repositories
+## Example repositories
 
 Rsbuild has provided some example projects of Module Federation, you can refer to:
 
diff --git a/website/docs/en/guide/advanced/ssr.mdx b/website/docs/en/guide/advanced/ssr.mdx
index 7f0883a684..df45091296 100644
--- a/website/docs/en/guide/advanced/ssr.mdx
+++ b/website/docs/en/guide/advanced/ssr.mdx
@@ -12,7 +12,7 @@ In traditional client-side rendering, the server sends an empty HTML shell and s
 
 With SSR, the server generates HTML that already contains dynamic content and sends it to the client. This makes the initial page loading faster and more SEO-friendly, as search engines can crawl the rendered page.
 
-## File Structure
+## File structure
 
 A typical SSR application will have the following files:
 
@@ -152,7 +152,7 @@ If you need to preview the online effect of SSR rendering, you also need to modi
 
 Now, you can run the `npm run dev` command to start the dev server with SSR rendering function, and visit `http://localhost:3000/` to see that the SSR content has been rendered to the HTML page.
 
-## Get Manifest
+## Get manifest
 
 By default, scripts and links associated with the current page are automatically inserted into the HTML template. At this time, the compiled HTML template content can be obtained through [getTransformedHtml](/guide/advanced/environments#environment-api).
 
diff --git a/website/docs/en/guide/basic/cli.mdx b/website/docs/en/guide/basic/cli.mdx
index 4380072231..aa4323800e 100644
--- a/website/docs/en/guide/basic/cli.mdx
+++ b/website/docs/en/guide/basic/cli.mdx
@@ -47,7 +47,7 @@ Options:
   -h, --help            display help for command
 ```
 
-### Opening Page
+### Opening page
 
 The `--open` option allows you to automatically open a page when starting the dev server, which is equivalent to setting [server.open](/config/server/open) to `true`.
 
@@ -146,7 +146,7 @@ Inspect config succeed, open following files to view the content:
   - Rspack Config (web): /project/dist/.rsbuild/rspack.config.web.mjs
 ```
 
-### Specifying Mode
+### Specifying mode
 
 By default, the inspect command outputs the configuration for the development mode. You can add the `--env production` option to output the configuration for the production mode:
 
@@ -162,7 +162,7 @@ By default, the inspect command omits the content of functions in the configurat
 rsbuild inspect --verbose
 ```
 
-### Multiple Targets
+### Multiple targets
 
 If the current project has multiple build targets, such as building browser artifact and Node.js artifact simultaneously, multiple Rspack configuration files will be generated in the `dist/.rsbuild` directory.
 
diff --git a/website/docs/en/guide/basic/configure-rsbuild.mdx b/website/docs/en/guide/basic/configure-rsbuild.mdx
index e6cb9e99c3..b532e63123 100644
--- a/website/docs/en/guide/basic/configure-rsbuild.mdx
+++ b/website/docs/en/guide/basic/configure-rsbuild.mdx
@@ -4,7 +4,7 @@ Rsbuild provides a wide range of configuration options and sets a common default
 
 If you need to customize build behaviors, you can use these configuration options.
 
-## Configuration Structure
+## Configuration structure
 
 The configuration structure of Rsbuild looks like this:
 
@@ -52,7 +52,7 @@ export default {
 
 You can find detailed descriptions of all configs on the [Configure Overview](/config/) page.
 
-## Configuration File
+## Configuration file
 
 When you use the CLI of Rsbuild, Rsbuild will automatically read the configuration file in the root directory of the current project and resolve it in the following order:
 
@@ -97,7 +97,7 @@ export default defineConfig({
 When you use the `.ts`, `.mts`, and `.cts` extensions, Rsbuild will use [jiti](https://github.com/unjs/jiti) to load configuration files, providing interoperability between ESM and CommonJS. The behavior of module resolution differs slightly from the native behavior of Node.js.
 :::
 
-## Specify Config File
+## Specify config file
 
 Rsbuild CLI uses the `--config` option to specify the config file, which can be set to a relative path or an absolute path.
 
@@ -117,7 +117,7 @@ You can also abbreviate the `--config` option to `-c`:
 rsbuild build -c rsbuild.prod.config.mjs
 ```
 
-## Using Environment Variables
+## Using environment variables
 
 In the configuration file, you can use Node.js environment variables such as `process.env.NODE_ENV` to dynamically set different configurations:
 
@@ -136,7 +136,7 @@ export default defineConfig({
 });
 ```
 
-## Export Function
+## Export function
 
 Rsbuild supports the export of a function in the config file, where you can dynamically compute the config and return it to Rsbuild.
 
@@ -183,7 +183,7 @@ For example, when running `rsbuild build --env-mode test`, the value of `envMode
 
 The current running CLI command, such as `dev`, `build`, `preview`.
 
-## Export Async Function
+## Export async function
 
 Rsbuild also supports the export of an async function in the config file, where you can perform some async operations:
 
@@ -201,7 +201,7 @@ export default defineConfig(async ({ env, command }) => {
 });
 ```
 
-## Merge Configurations
+## Merge configurations
 
 You can use the [mergeRsbuildConfig](/api/javascript-api/core#mergersbuildconfig) function exported by `@rsbuild/core` to merge multiple configurations.
 
diff --git a/website/docs/en/guide/basic/configure-rspack.mdx b/website/docs/en/guide/basic/configure-rspack.mdx
index 8441f92665..d9ba62cc62 100644
--- a/website/docs/en/guide/basic/configure-rspack.mdx
+++ b/website/docs/en/guide/basic/configure-rspack.mdx
@@ -6,13 +6,13 @@ Rsbuild supports directly modifying the Rspack configuration object, and also su
 The built-in Rspack config in Rsbuild may change with iterations, and these changes won't be reflected in semver. Therefore, your custom config may become invalid when you upgrade Rsbuild.
 :::
 
-## View Rspack Config
+## View Rspack config
 
 Rsbuild provides the [rsbuild inspect](/guide/basic/cli#rsbuild-inspect) command to view the final Rspack config generated by Rsbuild.
 
 You can also view it through [debug mode](/guide/debug/debug-mode).
 
-## Modify Config Object
+## Modify config object
 
 You can use the [tools.rspack](/config/tools/rspack) option of Rsbuild to modify the Rspack config object.
 
@@ -45,7 +45,7 @@ export default {
 
 > Please refer to the [tools.rspack documentation](/config/tools/rspack) for detailed usage.
 
-## Use Bundler Chain
+## Use bundler chain
 
 import RspackChain from '@en/shared/rspackChain.mdx';
 
@@ -108,7 +108,7 @@ export default {
 };
 ```
 
-#### ID Types
+#### ID types
 
 The `CHAIN_ID` object contains various IDs, which correspond to the following configurations:
 
@@ -228,7 +228,7 @@ export default {
 };
 ```
 
-#### Configure Plugin
+#### Configure plugin
 
 Here are examples of adding, modifying, and deleting Rspack plugins.
 
diff --git a/website/docs/en/guide/basic/configure-swc.mdx b/website/docs/en/guide/basic/configure-swc.mdx
index 69dfce86fc..6e4867b799 100644
--- a/website/docs/en/guide/basic/configure-swc.mdx
+++ b/website/docs/en/guide/basic/configure-swc.mdx
@@ -7,11 +7,11 @@ Rsbuild enables the following SWC features by default:
 - Transform JavaScript and TypeScript code using Rspack's [builtin:swc-loader](https://rspack.dev/guide/features/builtin-swc-loader), which is the Rust version of [swc-loader](https://github.com/swc-project/pkgs/tree/main/packages/swc-loader).
 - Minify JavaScript code using Rspack's [SwcJsMinimizerRspackPlugin](https://rspack.dev/plugins/rspack/swc-js-minimizer-rspack-plugin).
 
-## Loader Options
+## Loader options
 
 The options for `builtin:swc-loader` are consistent with the JS version of swc-loader. Rsbuild provides the [tools.swc](/config/tools/swc) option to configure `builtin:swc-loader`. Here are some examples:
 
-### Register SWC Plugin
+### Register SWC plugin
 
 `tools.swc` can be used to register SWC's Wasm plugins, for example, registering [@swc/plugin-styled-components](https://www.npmjs.com/package/@swc/plugin-styled-components):
 
@@ -31,13 +31,13 @@ export default {
 
 > You can check out the [awesome-swc](https://github.com/swc-contrib/awesome-swc) repository to see the SWC plugins available in the community.
 
-### SWC Plugin Version
+### SWC plugin version
 
 Please note that the SWC plugin is still an experimental feature, and the SWC Wasm plugin is currently not backward compatible. The version of the SWC plugin is closely tied to the version of `swc_core` that Rspack depends on.
 
 This means that you must to choose an SWC plugin that matches the current version of `swc_core` to ensure that it works properly. If the version of the SWC plugin you are using does not match the version of `swc_core` that Rspack depends on, Rspack will throw an error during the build process. Please refer to [Rspack FAQ - SWC Plugin Version Unmatched](https://rspack.dev/errors/swc-plugin-version) for more information.
 
-### Enable Emotion Support
+### Enable Emotion support
 
 Example of enabling the Emotion support using the `builtin:swc-loader`:
 
@@ -57,7 +57,7 @@ export default {
 
 For more options, please refer to [@swc/plugin-emotion](https://www.npmjs.com/package/@swc/plugin-emotion).
 
-### Enable Relay Support
+### Enable Relay support
 
 Example of enabling the Relay support using the `builtin:swc-loader`:
 
@@ -77,11 +77,11 @@ export default {
 
 For more options, please refer to [@swc/plugin-relay](https://www.npmjs.com/package/@swc/plugin-relay).
 
-## Minimizer Options
+## Minimizer options
 
 Rsbuild provides the [output.minify.js](/config/output/minify) option to configure the SwcJsMinimizerRspackPlugin. Here are some examples:
 
-### Exclude Files
+### Exclude files
 
 You can exclude certain files from being minified using the `exclude` option:
 
@@ -97,7 +97,7 @@ export default {
 };
 ```
 
-## Switching Minimizer
+## Switching minimizer
 
 If the `SwcJsMinimizerRspackPlugin` does not meet your needs, you can switch to other minimizers through the [tools.bundlerChain](/config/tools/bundler-chain) option.
 
diff --git a/website/docs/en/guide/basic/css-modules.mdx b/website/docs/en/guide/basic/css-modules.mdx
index f5addb0402..e99bfab096 100644
--- a/website/docs/en/guide/basic/css-modules.mdx
+++ b/website/docs/en/guide/basic/css-modules.mdx
@@ -13,7 +13,7 @@ The following style files are considered CSS Modules:
 - `*.module.styl`
 - `*.module.stylus`
 
-## Usage Example
+## Usage example
 
 - Write style:
 
@@ -33,7 +33,7 @@ export default () => {
 };
 ```
 
-## Named Import
+## Named import
 
 If you prefer to use named imports in CSS Modules, you can enable it through the [output.cssModules.namedExport](/config/output/css-modules#cssmodulesnamedexport) config.
 
@@ -57,7 +57,7 @@ export default () => {
 };
 ```
 
-## CSS Modules Recognition Rules
+## CSS Modules recognition rules
 
 By default, only files ending with `*.module.css` are recognized as CSS Modules.
 
@@ -84,7 +84,7 @@ import styles1 from './foo.module.css';
 import styles2 from './shared/bar.css';
 ```
 
-## Custom Class Names
+## Custom class names
 
 Customizing the class names generated by CSS Modules is also a commonly used function, you can use [output.cssModules.localIdentName](/config/output/css-modules#cssmoduleslocalidentname) to configure it.
 
@@ -100,7 +100,7 @@ export default {
 
 If you need to customize other configs of CSS Modules, you can set them via [output.cssModules](/config/output/css-modules).
 
-## Type Declaration
+## Type declaration
 
 When you import CSS Modules in TypeScript code, TypeScript may prompt that the module is missing a type definition:
 
@@ -158,7 +158,7 @@ declare module '*.module.stylus';
 
 After adding the type declaration, if the type error still exists, you can try to restart the current IDE, or adjust the directory where `env.d.ts` is located, making sure the TypeScript can correctly identify the type definition.
 
-## Type Generation
+## Type generation
 
 Although the above method can provide the type of CSS Modules, it cannot accurately prompt which classNames are exported by a certain CSS file.
 
diff --git a/website/docs/en/guide/basic/css-usage.mdx b/website/docs/en/guide/basic/css-usage.mdx
index 2d9c76e83c..8b2fd51a6a 100644
--- a/website/docs/en/guide/basic/css-usage.mdx
+++ b/website/docs/en/guide/basic/css-usage.mdx
@@ -1,4 +1,4 @@
-# Import CSS Files
+# Import CSS files
 
 Rsbuild provides out-of-the-box support for CSS, including PostCSS, CSS Modules, CSS preprocessors, CSS inlining, and CSS compression.
 
@@ -44,7 +44,7 @@ export default {
 - [postcss-preset-env](https://github.com/csstools/postcss-plugins/tree/main/plugin-packs/postcss-preset-env): Converts modern CSS into something most browsers can understand.
 - [postcss-nesting](https://github.com/csstools/postcss-plugins/tree/main/plugins/postcss-nesting): Supports CSS nesting.
 
-## CSS Minification
+## CSS minification
 
 When building for production, Rsbuild enables Rspack's built-in [LightningCssMinimizerRspackPlugin](https://rspack.dev/plugins/rspack/lightning-css-minimizer-rspack-plugin) plugin to minify CSS assets for better transmission efficiency.
 
@@ -99,7 +99,7 @@ Rsbuild supports popular CSS preprocessors through plugins, including Sass, Less
 
 Please read the [React - CSS-in-JS](/guide/framework/react#css-in-js) section to learn how to use common CSS-in-JS libraries in Rsbuild.
 
-## Inline CSS Files
+## Inline CSS files
 
 By default, Rsbuild will extract CSS into a separate `.css` file and output it to the dist directory.
 
diff --git a/website/docs/en/guide/basic/html-template.mdx b/website/docs/en/guide/basic/html-template.mdx
index 9e2cb1ee08..342e6359a4 100644
--- a/website/docs/en/guide/basic/html-template.mdx
+++ b/website/docs/en/guide/basic/html-template.mdx
@@ -1,10 +1,10 @@
-# HTML Template
+# HTML template
 
 During the build process, Rsbuild will compile based on the HTML template and template parameters to generate several HTML files.
 
 Rsbuild provides some configs to set the HTML template. Through this chapter, you can learn the basic usage of these configs.
 
-## Set Template
+## Set template
 
 In Rsbuild, you can use [html.template](/config/html/template) config to define the path to the custom HTML template.
 
@@ -28,7 +28,7 @@ If `html.template` is not set, Rsbuild will use the built-in HTML template:
 </html>
 ```
 
-## Set Page Title
+## Set page title
 
 You can set the HTML `<title>` tag through the [html.title](/config/html/title) config.
 
@@ -62,7 +62,7 @@ export default {
 For single-page applications (SPA), Rsbuild will include an initial title in the HTML page, but you usually need to dynamically update the page title on route switching, for example using some routing libraries or libraries like [React Helmet](https://github.com/nfl/react-helmet).
 :::
 
-## Set Page Icon
+## Set page icon
 
 Rsbuild supports setting [favicon](https://developer.mozilla.org/en-US/docs/Glossary/Favicon) icon and [apple-touch-icon](https://webhint.io/docs/user-guide/hints/hint-apple-touch-icons/) icon.
 
@@ -92,7 +92,7 @@ export default {
 };
 ```
 
-## Set Meta Tags
+## Set meta tags
 
 You can set the meta tags through the [html.meta](/config/html/meta) config.
 
@@ -121,7 +121,7 @@ The generated meta tag in HTML is:
 <meta name="description" content="a description of the page" />
 ```
 
-## Default Template Engine
+## Default template engine
 
 Rsbuild comes with a built-in default template engine to handle HTML template files, and its syntax is similar to a subset of EJS, but it has some differences. When the suffix of an HTML template file is `.html`, Rsbuild will use the built-in template engine to parse the HTML template.
 
@@ -135,7 +135,7 @@ For example, if a `text` param is defined in the template with the value `'world
 <div>hello world!</div>
 ```
 
-### Template Parameters
+### Template parameters
 
 In HTML templates, you can use a variety of template parameters. The template parameters injected by Rsbuild by default include:
 
@@ -186,7 +186,7 @@ The compiled HTML code will be:
 <div>hello world!</div>
 ```
 
-### Parameter Escaping
+### Parameter escaping
 
 When using `<%= text %>`, the parameters will not be escaped. You can use `<%- text %>` to escape parameters.
 
@@ -204,7 +204,7 @@ For example, if the value of the parameter `text` is `'<script>'`, it will be es
 Note that Rsbuild's default escape syntax is different from EJS. In EJS, the default escape syntax is `<%= text %>`, whereas Rsbuild's default escape syntax is `<%- text %>`.
 :::
 
-## Other Template Engines
+## Other template engines
 
 Rsbuild also supports using other template engines via plugins, such as [EJS](https://ejs.co/) and [Pug](https://pugjs.org/).
 
@@ -216,7 +216,7 @@ Rsbuild's built-in template syntax has some differences from [EJS](https://ejs.c
 
 Rsbuild supports the [Pug](https://pugjs.org/) template engine via a plugin. See [@rsbuild/plugin-pug](https://github.com/rspack-contrib/rsbuild-plugin-pug) for more details.
 
-## Injecting Tags
+## Injecting tags
 
 You can insert any tags into the HTML files generated by Rsbuild by configuring [html.tags](/config/html/tags).
 
@@ -266,7 +266,7 @@ export default {
 Typically, you do not need to manually use the `htmlPlugin.tags.headTags` and `htmlPlugin.tags.bodyTags` template parameters, because Rsbuild will automatically inject these tags. See [html.inject](/config/html/inject) for more details on adjusting the injection location.
 :::
 
-## HTML Plugin
+## HTML plugin
 
 Rsbuild internally implements HTML-related features based on [html-rspack-plugin](https://github.com/rspack-contrib/html-rspack-plugin). It is a fork of [html-webpack-plugin](https://github.com/jantimon/html-webpack-plugin), with the same features and options.
 
@@ -286,6 +286,6 @@ export default {
 };
 ```
 
-## HTML Minification
+## HTML minification
 
 Rsbuild currently does not minify HTML files. If you need to minify HTML files, you can use the [rsbuild-plugin-html-minifier-terser plugin](https://github.com/rspack-contrib/rsbuild-plugin-html-minifier-terser).
diff --git a/website/docs/en/guide/basic/json-files.mdx b/website/docs/en/guide/basic/json-files.mdx
index d49c6d94a4..332c9d573d 100644
--- a/website/docs/en/guide/basic/json-files.mdx
+++ b/website/docs/en/guide/basic/json-files.mdx
@@ -1,4 +1,4 @@
-# Import JSON Files
+# Import JSON files
 
 Rsbuild supports import JSON files in code, and also supports import [YAML](https://yaml.org/) and [Toml](https://toml.io/en/) files and converting them to JSON format.
 
@@ -22,7 +22,7 @@ console.log(example.name); // 'foo';
 console.log(example.items); // [1, 2];
 ```
 
-### Named Import
+### Named import
 
 Rsbuild also supports importing JSON files via named import:
 
@@ -92,7 +92,7 @@ console.log(example.hello); // 'world';
 console.log(example.foo); // { bar: 'baz' };
 ```
 
-## Type Declaration
+## Type declaration
 
 When you import YAML or Toml files in TypeScript code, please create a `src/env.d.ts` file in your project and add the corresponding type declarations.
 
diff --git a/website/docs/en/guide/basic/output-files.mdx b/website/docs/en/guide/basic/output-files.mdx
index 768bbf25db..30602f75cf 100644
--- a/website/docs/en/guide/basic/output-files.mdx
+++ b/website/docs/en/guide/basic/output-files.mdx
@@ -1,10 +1,10 @@
-# Output Files
+# Output files
 
 This chapter will introduces the directory structure of output files and how to control the output directory of different types of files.
 
 If you want to know how to deploy the build outputs of Rsbuild as a static site, please refer to [Deploy Static Site](/guide/basic/static-deploy).
 
-## Default Directory Structure
+## Default directory structure
 
 The following is a basic directory for output files. By default, the compiled files will be output in the `dist` directory of current project.
 
@@ -36,7 +36,7 @@ In addition, JS files and CSS files sometimes generate some related files:
 
 In the filename, `[name]` represents the entry name corresponding to this file, such as `index`, `main`. `[hash]` is the hash value generated based on the content of the file.
 
-## Development Mode Output
+## Development mode output
 
 In development mode, Rsbuild stores the build outputs in memory on the dev server by default, rather than writing then to disk. This can reduce the overhead of fs operations. You can refer to [View Static Assets](/guide/basic/server#view-static-assets) to view all static assets generated in the current build.
 
@@ -52,7 +52,7 @@ export default {
 };
 ```
 
-## Modify the Directory
+## Modify the directory
 
 Rsbuild provides some configs to modify the directory or filename, you can:
 
@@ -62,7 +62,7 @@ Rsbuild provides some configs to modify the directory or filename, you can:
 - Modify Source Map file through [output.sourceMap](/config/output/source-map).
 - Modify the output structure of the HTML files through [html.outputStructure](/config/html/output-structure).
 
-## Static Assets
+## Static assets
 
 When you import static assets such as images, SVG, fonts, media, etc. in the code, they will also be output to the `dist/static` directory, and automatically assigned to the corresponding subdirectories according to the file type:
 
@@ -108,7 +108,7 @@ dist
     └── qux.[hash].mp4
 ```
 
-## Node.js Output Directory
+## Node.js output directory
 
 When the [output.target](/config/output/target) of Rsbuild is `'node'`, Rsbuild will generate output files for Node.js:
 
@@ -144,7 +144,7 @@ export default {
 };
 ```
 
-## Flatten the Directory
+## Flatten the directory
 
 Sometimes you don't want the dist directory to have too many levels, you can set the directory to an empty string to flatten the generated directory.
 
diff --git a/website/docs/en/guide/basic/server.mdx b/website/docs/en/guide/basic/server.mdx
index 815ece0965..2ba111f98f 100644
--- a/website/docs/en/guide/basic/server.mdx
+++ b/website/docs/en/guide/basic/server.mdx
@@ -2,7 +2,7 @@
 
 Rsbuild comes with a built-in dev server designed to improve the development experience. When you run the `rsbuild dev` or `rsbuild preview` commands, the server will start, providing features such as page preview, routing, and hot module reloading.
 
-## Base Path
+## Base path
 
 By default, the base path of the server is `/`, and users can access output files such as `index.html` and public folder assets through http://localhost:3000/.
 
@@ -16,7 +16,7 @@ export default {
 };
 ```
 
-## View Static Assets
+## View static assets
 
 After starting the dev server, you can access `/rsbuild-dev-server` to view all static assets generated during the current build.
 
@@ -28,11 +28,11 @@ For example, open `http://localhost:3000/rsbuild-dev-server` in the browser, you
   width="600"
 />
 
-## Page Routing
+## Page routing
 
 Rsbuild Server offers a set of default routing convention, and allows users to customize it through configurations.
 
-### Default Behavior
+### Default behavior
 
 Rsbuild Server will generate the corresponding page route based on the [server.base](/config/server/base) and [source.entry](/config/source/entry) configurations.
 
@@ -51,7 +51,7 @@ export default {
 };
 ```
 
-### Fallback Behavior
+### Fallback behavior
 
 By default, when the request meets the following conditions and the corresponding resource is not found, it will fallback to `index.html`:
 
@@ -66,7 +66,7 @@ export default {
 };
 ```
 
-### Custom Fallback Behavior
+### Custom fallback behavior
 
 When Rsbuild's default [server.htmlFallback](/config/server/html-fallback) configuration cannot meet your needs, for example, if you want to be able to access `main.html` when accessing `/`, you can set it up using [server.historyApiFallback](/config/server/history-api-fallback).
 
@@ -86,7 +86,7 @@ export default {
 };
 ```
 
-### HTML Output Path
+### HTML output path
 
 Normally, `/` points to the dist root directory, and the HTML file is output to the dist root directory. At this time, the corresponding HTML page can be accessed through `/some-path`.
 
@@ -110,7 +110,7 @@ export default {
 };
 ```
 
-## Rspack Dev Server
+## Rspack dev server
 
 The built-in dev server of Rspack CLI is [@rspack/dev-server](https://www.npmjs.com/package/@rspack/dev-server). Rsbuild does not use `@rspack/dev-server`, but instead implemented its own more lightweight version.
 
@@ -176,7 +176,7 @@ export default {
 };
 ```
 
-## Custom Server
+## Custom server
 
 If you want to integrate Rsbuild dev server into a custom server, you can get the instance methods of Rsbuild dev server through the `createDevServer` method of Rsbuild and call them on demand.
 
diff --git a/website/docs/en/guide/basic/static-assets.mdx b/website/docs/en/guide/basic/static-assets.mdx
index 8641e1b130..85fea41f6f 100644
--- a/website/docs/en/guide/basic/static-assets.mdx
+++ b/website/docs/en/guide/basic/static-assets.mdx
@@ -1,4 +1,4 @@
-# Import Static Assets
+# Import static assets
 
 Rsbuild supports import static assets, including images, fonts, audio and video.
 
@@ -6,7 +6,7 @@ Rsbuild supports import static assets, including images, fonts, audio and video.
 Static assets are files that are part of a web application and do not change, even when the application is being used. Examples of static assets include images, fonts, medias, stylesheets, and JavaScript files. These assets are typically stored on a web server or CDN, and delivered to the user's web browser when the Web application is accessed. Because they do not change, static assets can be cached by the browser, which helps to improve the performance of the Web application.
 :::
 
-## Assets Format
+## Assets format
 
 The following are the formats supported by Rsbuild by default:
 
@@ -21,7 +21,7 @@ If you need to import assets in other formats, please refer to [Extend Asset Typ
 SVG image is a special case. Rsbuild support convert SVG to React components, so SVG is processed separately. For details, see [SVGR Plugin](/plugins/list/plugin-svgr).
 :::
 
-## Import Assets in JS file
+## Import assets in JS file
 
 In JS files, you can import static assets with relative paths:
 
@@ -74,7 +74,7 @@ const fooCss = new URL('./foo.css', import.meta.url).href;
 console.log(fooCss); // "/static/foo.[hash].css"
 ```
 
-## Import Assets in CSS file
+## Import assets in CSS file
 
 In CSS files, you can reference static assets in relative paths:
 
@@ -120,7 +120,7 @@ export default {
 };
 ```
 
-## Import Results
+## Import results
 
 The result of importing static assets depends on the file size:
 
@@ -137,7 +137,7 @@ console.log(smallImage); // "data:image/png;base64,iVBORw0KGgo..."
 
 For a more detailed introduction to asset inlining, please refer to the [Static Asset Inlining](/guide/optimization/inline-assets) chapter.
 
-## Output Files
+## Output files
 
 When static assets are imported, they will be output to the dist directory. You can:
 
@@ -146,7 +146,7 @@ When static assets are imported, they will be output to the dist directory. You
 
 Please read [Output Files](/guide/basic/output-files) for details.
 
-## URL Prefix
+## URL prefix
 
 The URL returned after importing a asset will automatically include the path prefix:
 
@@ -161,7 +161,7 @@ import logo from './static/logo.png';
 console.log(logo); // "https://example.com/static/logo.[hash].png"
 ```
 
-## Public Folder
+## Public folder
 
 The public folder at the project root can be used to place some static assets. These assets will not be built by Rsbuild and can be directly referenced via URL.
 
@@ -206,7 +206,7 @@ import logo from './assets/logo.png';
 
 - During the production build, the files in public folder will be copied to the output folder (default is `dist`). Please be careful to avoid name conflicts with the output files. When files in the `public` folder have the same name as outputs, the outputs have higher priority and will overwrite the files with the same name in the `public` folder. This feature can be disabled by setting [server.publicDir.copyOnBuild](/config/server/public-dir) to `false`.
 
-### Custom Behavior
+### Custom behavior
 
 Rsbuild provides the [server.publicDir](/config/server/public-dir) option which can be used to customize the name and behavior of the public folder, as well as to disable it.
 
@@ -218,7 +218,7 @@ export default {
 };
 ```
 
-## Type Declaration
+## Type declaration
 
 When you import static assets in TypeScript code, TypeScript may prompt that the module is missing a type definition:
 
@@ -246,7 +246,7 @@ declare module '*.png' {
 
 After adding the type declaration, if the type error still exists, you can try to restart the current IDE, or adjust the directory where `env.d.ts` is located, making sure the TypeScript can correctly identify the type definition.
 
-## Extend Asset Types
+## Extend asset types
 
 If the built-in asset types in Rsbuild cannot meet your requirements, you can extend additional static asset types in the following ways.
 
@@ -294,7 +294,7 @@ export default {
 
 For more information about asset modules, please refer to [Rspack - Asset modules](https://rspack.dev/guide/features/asset-module).
 
-### Related Configurations
+### Related configurations
 
 Extended static asset types will be affected by the following configurations:
 
@@ -302,7 +302,7 @@ Extended static asset types will be affected by the following configurations:
 - [output.distPath.assets](/config/output/dist-path): Set the output directory of extended static assets.
 - [output.dataUriLimit.assets](/config/output/data-uri-limit): Set the threshold of inlining for extended static assets.
 
-## Custom Rules
+## Custom rules
 
 In some scenarios, you may need to bypass the built-in assets processing rules of Rsbuild and add some custom rules.
 
@@ -333,7 +333,7 @@ export default {
 };
 ```
 
-## Image Format
+## Image format
 
 When using image assets, you can choose a appropriate image format according to the pros and cons in the table below.
 
diff --git a/website/docs/en/guide/basic/static-deploy.mdx b/website/docs/en/guide/basic/static-deploy.mdx
index 687569a479..060f1768c6 100644
--- a/website/docs/en/guide/basic/static-deploy.mdx
+++ b/website/docs/en/guide/basic/static-deploy.mdx
@@ -1,8 +1,8 @@
-# Deploy Static Site
+# Deploy static site
 
 This section introduces how to deploy the build outputs of Rsbuild as a static site.
 
-## Background Information
+## Background information
 
 Before starting the deployment, you need to understand some background information:
 
@@ -10,7 +10,7 @@ Before starting the deployment, you need to understand some background informati
 - The directory structure of the build outputs.
 - The URL prefix of static assets.
 
-### Build Commands
+### Build commands
 
 The build commands provided by Rsbuild:
 
@@ -30,7 +30,7 @@ The build commands provided by Rsbuild:
 The preview command is only used for local preview. Do not use it for production servers, as it is not designed for that.
 :::
 
-### Output Directory
+### Output directory
 
 Rsbuild's build outputs typically includes HTML, JS, CSS, and other assets, and is output to the `dist` directory by default. The name and structure of the dist directory can be changed using some configuration options. See the [Output Files](/guide/basic/output-files) section for more information.
 
@@ -43,7 +43,7 @@ dist
 └── [name].html
 ```
 
-### Asset Prefix
+### Asset prefix
 
 We can divide the build output into two parts: **HTML files** and **static assets**.
 
@@ -80,7 +80,7 @@ In this way, when referencing static assets in HTML, the specified prefix will b
 <script src="https://cdn.com/path/static/js/index.some-hash.js"></script>
 ```
 
-## GitHub Pages
+## GitHub pages
 
 [GitHub Pages](https://pages.github.com/) is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on GitHub
 
@@ -112,7 +112,7 @@ on:
   # Runs on pushes targeting the default branch
   push:
     branches: ['main']
-  # Allows you to run this workflow manually from the Actions tab
+  # Allows you to run this workflow manually from the actions tab
   workflow_dispatch:
 
 # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
@@ -166,7 +166,7 @@ jobs:
 
 [Netlify Core](https://www.netlify.com/) is a frontend cloud solution for developers to build and deploy future-proof digital solutions with modern, composable tooling.
 
-### Add New Site
+### Add new site
 
 Netlify provides a detailed guide, you can follow the instructions in [Netlify - Add new site](https://docs.netlify.com/welcome/add-new-site/), set up some basic information, and then you can start the deployment.
 
@@ -177,7 +177,7 @@ You need to configure the following two fields:
 
 Then click on the **Deploy site** button to start the deployment.
 
-### Custom Domains
+### Custom domains
 
 If you want to make your sites accessible at your own domain names, you can configure it in the "Domain management" section of Netlify.
 
@@ -187,7 +187,7 @@ If you want to make your sites accessible at your own domain names, you can conf
 
 [Vercel](https://vercel.com/) is a platform for developers that provides the tools, workflows, and infrastructure you need to build and deploy your web apps faster, without the need for additional configuration.
 
-### Add New Site
+### Add new site
 
 Vercel provides a detailed guide that you can follow [Vercel - Projects](https://vercel.com/docs/projects/overview) to create a project in your dashboard and configure some basic information to start deployment.
 
@@ -197,7 +197,7 @@ You only need to configure the fields under "Build and Output Settings":
 
 Then click the **Deploy** button to start the deployment.
 
-### Configure Domains
+### Configure domains
 
 If you want to make your sites accessible at your own domain names, you can configure it in the "Domains" section of Vercel.
 
diff --git a/website/docs/en/guide/basic/tailwindcss.mdx b/website/docs/en/guide/basic/tailwindcss.mdx
index c9c35b7696..ec62065065 100644
--- a/website/docs/en/guide/basic/tailwindcss.mdx
+++ b/website/docs/en/guide/basic/tailwindcss.mdx
@@ -63,7 +63,7 @@ module.exports = {
 };
 ```
 
-### Other Configuration Methods
+### Other configuration methods
 
 - You can directly pass the Tailwind CSS configuration to `postcss.config.cjs`:
 
@@ -123,13 +123,13 @@ You can use Tailwind's utility classes in any component or HTML, such as:
 
 For more usage details, refer to the [Tailwind CSS documentation](https://tailwindcss.com/).
 
-## VS Code Extension
+## VS Code extension
 
 Tailwind CSS provides a [Tailwind CSS IntelliSense](https://github.com/tailwindlabs/tailwindcss-intellisense) plugin for VS Code to automatically complete Tailwind CSS class names, CSS functions, and directives.
 
 You can install this plugin in VS Code to enable the autocompletion feature.
 
-## Optimize Build Performance
+## Optimize build performance
 
 When using Tailwind CSS, if the `content` field in `tailwind.config.js` is not correctly configured, this can lead to poor build performance and HMR performance. This is because Tailwind CSS internally matches files based on the glob defined in `content`. The more files it matches, the greater the performance overhead.
 
@@ -161,7 +161,7 @@ module.exports = {
 };
 ```
 
-## Optimize CSS Size
+## Optimize CSS size
 
 If you need to optimize the size of Tailwind CSS styles, you can try [rsbuild-plugin-tailwindcss](https://github.com/rspack-contrib/rsbuild-plugin-tailwindcss).
 
diff --git a/website/docs/en/guide/basic/typescript.mdx b/website/docs/en/guide/basic/typescript.mdx
index 388a2ca030..20545c2a98 100644
--- a/website/docs/en/guide/basic/typescript.mdx
+++ b/website/docs/en/guide/basic/typescript.mdx
@@ -2,7 +2,7 @@
 
 Rsbuild supports TypeScript by default, allowing you to directly use `.ts` and `.tsx` files in your projects.
 
-## TypeScript Transpilation
+## TypeScript transpilation
 
 Rsbuild uses SWC by default for transpiling TypeScript code, and it also supports switching to Babel for transpilation.
 
@@ -40,7 +40,7 @@ You can create a `src/env.d.ts` file to reference it:
 /// <reference types="@rsbuild/core/types" />
 ```
 
-## Type Checking
+## Type checking
 
 When transpiling TypeScript code using tools like SWC and Babel, type checking is not performed.
 
@@ -60,7 +60,7 @@ export default {
 };
 ```
 
-## Path Extensions
+## Path extensions
 
 When importing another module in a TypeScript module, TypeScript allows using the `.js` file extension:
 
diff --git a/website/docs/en/guide/basic/unocss.mdx b/website/docs/en/guide/basic/unocss.mdx
index 1a09a951cb..a5f504832f 100644
--- a/website/docs/en/guide/basic/unocss.mdx
+++ b/website/docs/en/guide/basic/unocss.mdx
@@ -12,7 +12,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @unocss/webpack -D" />
 
-## Configuring Plugin
+## Configuring plugin
 
 Register the `UnoCSSRspackPlugin` plugin in [tools.rspack](/config/tools/rspack):
 
@@ -80,7 +80,7 @@ You can use UnoCSS's utility classes in any component or HTML, such as:
 
 For more usage details, refer to the [UnoCSS documentation](https://unocss.dev/).
 
-## VS Code Extension
+## VS Code extension
 
 UnoCSS provides a [VS Code Extension](https://unocss.dev/integrations/vscode) plugin for VS Code to decoration and tooltip for matched utilities.
 
diff --git a/website/docs/en/guide/basic/upgrade-rsbuild.mdx b/website/docs/en/guide/basic/upgrade-rsbuild.mdx
index 7dac8fd1d1..a4e0511757 100644
--- a/website/docs/en/guide/basic/upgrade-rsbuild.mdx
+++ b/website/docs/en/guide/basic/upgrade-rsbuild.mdx
@@ -4,7 +4,7 @@ This section explains how to upgrade the project's Rsbuild dependencies to the l
 
 > Please see [Releases](/community/releases/index) to understand the Rsbuild release strategy.
 
-## Using Taze
+## Using taze
 
 We recommend using [Taze](https://github.com/antfu-collective/taze) to upgrade the Rsbuild version. Taze is a CLI tool for updating npm dependencies.
 
diff --git a/website/docs/en/guide/basic/wasm-assets.mdx b/website/docs/en/guide/basic/wasm-assets.mdx
index cbf2726d7d..ce336dd6a2 100644
--- a/website/docs/en/guide/basic/wasm-assets.mdx
+++ b/website/docs/en/guide/basic/wasm-assets.mdx
@@ -1,4 +1,4 @@
-# Import Wasm Assets
+# Import Wasm assets
 
 Rsbuild supports import WebAssembly assets in code.
 
@@ -35,7 +35,7 @@ const wasmURL = new URL('./add.wasm', import.meta.url);
 console.log(wasmURL).pathname; // "/static/wasm/[hash].module.wasm"
 ```
 
-## Output Directory
+## Output directory
 
 When a `.wasm` asset is imported, it will be output by Rsbuild to the `dist/static/wasm` directory by default.
 
@@ -51,7 +51,7 @@ export default {
 };
 ```
 
-## Type Declaration
+## Type declaration
 
 When you import a Wasm file in TypeScript code, you usually need to add the corresponding type declaration.
 
diff --git a/website/docs/en/guide/basic/web-workers.mdx b/website/docs/en/guide/basic/web-workers.mdx
index 094ea7412f..4cca980e7c 100644
--- a/website/docs/en/guide/basic/web-workers.mdx
+++ b/website/docs/en/guide/basic/web-workers.mdx
@@ -8,7 +8,7 @@ Web Workers are a type of JavaScript program that runs in the background, indepe
 
 ## Use Web Workers
 
-### Import with Constructors
+### Import with constructors
 
 Web Workers are first-class citizens of Rspack, which means you don't need any loader to use web workers directly in Rspack or Rsbuild projects.
 
diff --git a/website/docs/en/guide/debug/build-profiling.mdx b/website/docs/en/guide/debug/build-profiling.mdx
index f84755b53f..8f2b46a896 100644
--- a/website/docs/en/guide/debug/build-profiling.mdx
+++ b/website/docs/en/guide/debug/build-profiling.mdx
@@ -1,4 +1,4 @@
-# Build Profiling
+# Build profiling
 
 Performing a performance analysis can help you identify performance bottlenecks in your project, allowing for targeted optimization.
 
@@ -35,7 +35,7 @@ npm install -g speedscope
 speedscope CPU.date.000000.00000.0.001.cpuprofile
 ```
 
-## Rspack Profiling
+## Rspack profiling
 
 Rsbuild supports the use of the `RSPACK_PROFILE` environment variable for Rspack build performance profile.
 
diff --git a/website/docs/en/guide/debug/debug-mode.mdx b/website/docs/en/guide/debug/debug-mode.mdx
index 7bfd518adc..8d5e7f4f50 100644
--- a/website/docs/en/guide/debug/debug-mode.mdx
+++ b/website/docs/en/guide/debug/debug-mode.mdx
@@ -1,4 +1,4 @@
-# Debug Mode
+# Debug mode
 
 Rsbuild provides a debug mode to troubleshoot problems, you can add the `DEBUG=rsbuild` environment variable when building to enable Rsbuild's debug mode.
 
@@ -12,7 +12,7 @@ DEBUG=rsbuild pnpm build
 
 In debug mode, Rsbuild will output some additional log information, and write the Rsbuild config and Rspack config to the dist directory, which is convenient for developers to view and debug.
 
-## Log Information
+## Log information
 
 In debug mode, you will see some logs in the terminal starting with `rsbuild`, including internal operations performed by Rsbuild and the current version of Rspack being used.
 
@@ -35,7 +35,7 @@ Inspect config succeeds, open following files to view the content:
    - Rspack Config (web): /Project/demo/dist/.rsbuild/rspack.config.web.mjs
 ```
 
-## Rsbuild Config File
+## Rsbuild config file
 
 In debug mode, Rsbuild will automatically generate `dist/.rsbuild/rsbuild.config.mjs` file, which contains the final generated Rsbuild config. In this file, you can know the final result of the Rsbuild config you passed in after being processed by the framework and Rsbuild.
 
@@ -55,7 +55,7 @@ export default {
 
 For a complete introduction to Rsbuild config, please see the [Configure Rsbuild](/guide/basic/configure-rsbuild) chapter.
 
-## Rspack Config File
+## Rspack config file
 
 Rsbuild will also automatically generate `dist/.rsbuild/rspack.config.web.mjs` file, which contains the final generated Rspack config. In this file, you can see what is included in the config that Rsbuild finally passes to Rspack.
 
diff --git a/website/docs/en/guide/debug/rsdoctor.mdx b/website/docs/en/guide/debug/rsdoctor.mdx
index b59d0985b7..1db74a5b73 100644
--- a/website/docs/en/guide/debug/rsdoctor.mdx
+++ b/website/docs/en/guide/debug/rsdoctor.mdx
@@ -4,7 +4,7 @@
 
 If you need to debug the build outputs or build process, you can use Rsdoctor for troubleshooting.
 
-## Quick Start
+## Quick start
 
 In a Rsbuild-based project, you can enable Rsdoctor as follows:
 
diff --git a/website/docs/en/guide/faq/features.mdx b/website/docs/en/guide/faq/features.mdx
index 591356474f..8ed3c7b735 100644
--- a/website/docs/en/guide/faq/features.mdx
+++ b/website/docs/en/guide/faq/features.mdx
@@ -1,6 +1,6 @@
 # Features FAQ
 
-### How to import UI Component library on demand?
+### How to import UI component library on demand?
 
 If you need to configure the on-demand import of the component library, you can configure it through [source.transformImport](/config/source/transform-import), which is equivalent to [babel-plugin-import](https://npmjs.com/package/babel-plugin-import).
 
diff --git a/website/docs/en/guide/faq/hmr.mdx b/website/docs/en/guide/faq/hmr.mdx
index f7b0b19ee1..b3eee82328 100644
--- a/website/docs/en/guide/faq/hmr.mdx
+++ b/website/docs/en/guide/faq/hmr.mdx
@@ -16,7 +16,7 @@ Before starting the troubleshooting process, it is helpful to have a basic under
 
 After understanding the principle of HMR, you can follow these steps for basic troubleshooting:
 
-#### 1. Check the WebSocket Connection
+#### 1. Check the WebSocket connection
 
 Open the browser console and check for the presence of the `[HMR] connected.` log.
 
@@ -25,7 +25,7 @@ Open the browser console and check for the presence of the `[HMR] connected.` lo
 
 There can be various reasons why the WebSocket connection fails to establish, such as using a network proxy that prevents the WebSocket request from reaching the dev server. You can check whether the WebSocket request address matches your dev server address. If it does not match, you can configure the WebSocket request address using [dev.client](/config/dev/client).
 
-#### 2. Check the hot-update Requests
+#### 2. Check the hot-update requests
 
 When you modify the code of a module and trigger a recompilation, the browser sends several `hot-update.json` and `hot-update.js` requests to the dev server to fetch the updated code.
 
@@ -33,7 +33,7 @@ You can try modifying a module and inspect the content of the `hot-update.(js|js
 
 If the content of the request is incorrect, it is likely due to a network proxy. Check whether the address of the `hot-update.(js|json)` request matches your dev server address. If it does not match, you need to adjust the proxy rules to route the `hot-update.(js|json)` request to the dev server address.
 
-#### 3. Check for Other Causes
+#### 3. Check for other causes
 
 If the above two steps do not reveal any issues, it is possible that other factors are causing the HMR to fail. For example, it could be that the code does not meet React's requirements for HMR. You can refer to the following questions for further troubleshooting.
 
diff --git a/website/docs/en/guide/framework/preact.mdx b/website/docs/en/guide/framework/preact.mdx
index 5126efe2ee..f475e8b667 100644
--- a/website/docs/en/guide/framework/preact.mdx
+++ b/website/docs/en/guide/framework/preact.mdx
@@ -2,7 +2,7 @@
 
 In this document, you will learn how to build a Preact application using Rsbuild.
 
-## Create Preact Project
+## Create Preact project
 
 You can use `create-rsbuild` to create a project with Rsbuild + Preact. Just execute the following command:
 
diff --git a/website/docs/en/guide/framework/react.mdx b/website/docs/en/guide/framework/react.mdx
index 37afdf18ff..543604f63b 100644
--- a/website/docs/en/guide/framework/react.mdx
+++ b/website/docs/en/guide/framework/react.mdx
@@ -2,7 +2,7 @@
 
 In this document, you will learn how to build a React application using Rsbuild.
 
-## Create React Project
+## Create React project
 
 You can use `create-rsbuild` to create a project with Rsbuild + React. Just execute the following command:
 
diff --git a/website/docs/en/guide/framework/solid.mdx b/website/docs/en/guide/framework/solid.mdx
index da3d5c2515..414859272f 100644
--- a/website/docs/en/guide/framework/solid.mdx
+++ b/website/docs/en/guide/framework/solid.mdx
@@ -2,7 +2,7 @@
 
 In this document, you will learn how to build a Solid application using Rsbuild.
 
-## Create Solid Project
+## Create Solid project
 
 You can use `create-rsbuild` to create a project with Rsbuild + Solid. Just execute the following command:
 
diff --git a/website/docs/en/guide/framework/svelte.mdx b/website/docs/en/guide/framework/svelte.mdx
index ce8ea50445..ef08372844 100644
--- a/website/docs/en/guide/framework/svelte.mdx
+++ b/website/docs/en/guide/framework/svelte.mdx
@@ -2,7 +2,7 @@
 
 In this document, you will learn how to build a Svelte 5 or Svelte 4 application using Rsbuild.
 
-## Create Svelte Project
+## Create Svelte project
 
 You can use `create-rsbuild` to create a project with Rsbuild + Svelte. Just execute the following command:
 
diff --git a/website/docs/en/guide/framework/vue.mdx b/website/docs/en/guide/framework/vue.mdx
index 4e8323bfa0..cf1c8bdfe9 100644
--- a/website/docs/en/guide/framework/vue.mdx
+++ b/website/docs/en/guide/framework/vue.mdx
@@ -2,7 +2,7 @@
 
 In this document, you will learn how to build a Vue 3 or Vue 2 application using Rsbuild.
 
-## Create Vue Project
+## Create Vue project
 
 You can use `create-rsbuild` to create a project with Rsbuild + Vue. Just execute the following command:
 
@@ -44,7 +44,7 @@ For projects using Vue CLI, you can refer to the [Vue CLI Migration Guide](/guid
 
 If you need to use the JSX syntax of Vue, you also need to register the [@rsbuild/plugin-vue-jsx](https://github.com/rspack-contrib/rsbuild-plugin-vue-jsx).
 
-### TypeScript Support
+### TypeScript support
 
 Rsbuild supports compiling TypeScript by default.
 
@@ -78,7 +78,7 @@ export default defineConfig({
 
 If you need to use the JSX syntax of Vue, you also need to register the [@rsbuild/plugin-vue2-jsx](https://github.com/rspack-contrib/rsbuild-plugin-vue2-jsx).
 
-### Type Declarations
+### Type declarations
 
 In a TypeScript project, you need to add type definitions for `*.vue` files so that TypeScript can recognize them correctly.
 
diff --git a/website/docs/en/guide/migration/cra.mdx b/website/docs/en/guide/migration/cra.mdx
index 58a02a0869..917892decb 100644
--- a/website/docs/en/guide/migration/cra.mdx
+++ b/website/docs/en/guide/migration/cra.mdx
@@ -9,7 +9,7 @@ After ejecting a CRA project, it becomes more like a project directly using webp
 
 :::
 
-## Installing Dependencies
+## Installing dependencies
 
 First, you need to replace the npm dependencies of CRA with Rsbuild's dependencies.
 
@@ -46,7 +46,7 @@ Next, you need to update the npm scripts in package.json to Rsbuild's CLI comman
 Rsbuild does not integrate testing frameworks, so it does not provide a command to replace `react-scripts test`. You can directly use testing frameworks such as Jest or Vitest. You can refer to the [Rsbuild react-jest](https://github.com/rspack-contrib/rspack-examples/tree/main/rsbuild/react-jest) example project for configuration.
 :::
 
-## Creating Configuration File
+## Creating configuration file
 
 Create a Rsbuild configuration file `rsbuild.config.ts` in the same directory as package.json and add the following content:
 
@@ -59,7 +59,7 @@ export default defineConfig({
 });
 ```
 
-## HTML Template
+## HTML template
 
 CRA uses the `public/index.html` file as the default HTML template. In Rsbuild, you can specify the HTML template through [html.template](/config/html/template):
 
@@ -80,7 +80,7 @@ In the HTML template, if you are using the `%PUBLIC_URL%` variable from CRA, rep
 
 This completes the basic migration from CRA to Rsbuild. You can now run the `npm run start` command to try starting the dev server.
 
-## Output Directory
+## Output directory
 
 By default, CRA outputs to the `build` directory, while Rsbuild's default output directory is `dist`.
 
@@ -98,7 +98,7 @@ export default {
 
 > For more details, please refer to the [Output Files](/guide/basic/output-files) section.
 
-## Using CSS Preprocessors
+## Using CSS preprocessors
 
 Rsbuild supports CSS preprocessors such as Sass and Less through plugins. Please refer to:
 
@@ -134,7 +134,7 @@ export default {
 
 Please refer to the [SVGR plugin](/plugins/list/plugin-svgr) documentation to learn how to use SVGR in Rsbuild.
 
-## Configuration Migration
+## Configuration migration
 
 Here is the corresponding Rsbuild configuration for [CRA configuration](https://create-react-app.dev/docs/advanced-configuration/):
 
@@ -163,7 +163,7 @@ By default, CRA uses Babel to compile dependencies in node_modules, but Rsbuild
 
 If you need to handle syntax compatibility issues caused by dependencies in node_modules, you can use the [source.include](/config/source/include#compile-node_modules) config to compile node_modules.
 
-## Env Variables
+## Env variables
 
 CRA injects environment variables starting with `REACT_APP_` into the client code by default, while Rsbuild injects environment variables starting with `PUBLIC_` by default (see [public variables](/guide/advanced/env-vars#public-variables)).
 
@@ -207,7 +207,7 @@ export default defineConfig({
 });
 ```
 
-## Import Unknown Assets
+## Import unknown assets
 
 In CRA, if you import an asset that the build tool cannot recognize, CRA will by default output the file to the `build/static/media` directory, for example, the `document.pdf` file:
 
@@ -281,7 +281,7 @@ In non-TypeScript projects, CRA supports reading the `paths` field in jsconfig.j
 
 If you want to use this feature in Rsbuild, you can refer to the [Path Alias - jsconfig.json](/guide/advanced/alias#jsconfigjson).
 
-## CRACO Migration
+## CRACO migration
 
 If your project is using [CRACO](https://craco.js.org) to override CRA configuration, you can refer to the table below for migration:
 
@@ -336,7 +336,7 @@ export default {
 };
 ```
 
-## Contents Supplement
+## Contents supplement
 
 The current document only covers part of the migration process. If you find suitable content to add, feel free to contribute to the documentation via pull request 🤝.
 
diff --git a/website/docs/en/guide/migration/modern-builder.mdx b/website/docs/en/guide/migration/modern-builder.mdx
index 3224e72aec..02b422f4cd 100644
--- a/website/docs/en/guide/migration/modern-builder.mdx
+++ b/website/docs/en/guide/migration/modern-builder.mdx
@@ -2,7 +2,7 @@
 
 This chapter introduces how to migrate a Modern.js Builder (or EdenX Builder) project to Rsbuild.
 
-## Key Differences
+## Key differences
 
 Rsbuild is the new version of Modern.js Builder, with the following key differences:
 
@@ -10,7 +10,7 @@ Rsbuild is the new version of Modern.js Builder, with the following key differen
 - Rsbuild only supports Rspack as the bundler and no longer supports Webpack.
 - Rsbuild's CLI tool and dev server are more powerful and support more features.
 
-## Installing Dependencies
+## Installing dependencies
 
 First, you need to replace the npm dependencies related to Builder with Rsbuild's dependencies.
 
@@ -24,7 +24,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/core -D" />
 
-## Updating npm Scripts
+## Updating npm scripts
 
 Next, you need to update the npm scripts in the package.json to Rsbuild's CLI commands.
 
@@ -41,7 +41,7 @@ Next, you need to update the npm scripts in the package.json to Rsbuild's CLI co
 }
 ```
 
-## Modifying Configuration Files
+## Modifying configuration files
 
 - Rename `builder.config.ts` to `rsbuild.config.ts`.
 - Change the import of the `defineConfig` method from `@modern-js/builder-cli` to `@rsbuild/core`.
@@ -57,7 +57,7 @@ export default defineConfig({
 });
 ```
 
-## Replacing Plugins
+## Replacing plugins
 
 Rsbuild and Builder have incompatible plugin systems, so you need to replace Builder's plugins with Rsbuild's plugins.
 
@@ -85,7 +85,7 @@ export default defineConfig({
 });
 ```
 
-## Add React-related Plugins
+## Add React-related plugins
 
 Rsbuild is not coupled with any front-end UI framework. Therefore, if you are a React project, you need to manually add [React Plugin](/plugins/list/plugin-react):
 
@@ -109,7 +109,7 @@ export default {
 
 If you are a user of other frameworks, you can refer to [Rsbuild Plugin List](/plugins/list/index) to select the corresponding framework plugin.
 
-## Configuration Migration
+## Configuration migration
 
 Most configs in Rsbuild and Builder are consistent, with only a few adjustments.
 
@@ -123,13 +123,13 @@ It is worth noting that, compared to Builder, **there are some differences in de
 - **TypeScript type check:** not enabled by default, you need to manually register the [@rsbuild/plugin-type-check](https://github.com/rspack-contrib/rsbuild-plugin-type-check).
 - **Modify DevServer configuration:** Modify `dev` and `server` configuration instead.
 
-## Validating Results
+## Validating results
 
 After completing the above steps, you have migrated from Modern.js Builder to Rsbuild. You can now try starting the dev server by running the `npm run dev` command.
 
 If you encounter any issues during the build process, please debug according to the error logs.
 
-## Contents Supplement
+## Contents supplement
 
 The current document only covers part of the migration process. If you find suitable content to add, feel free to contribute to the documentation via pull request 🤝.
 
diff --git a/website/docs/en/guide/migration/rsbuild-0-x.mdx b/website/docs/en/guide/migration/rsbuild-0-x.mdx
index ac37be013e..51e18119c4 100644
--- a/website/docs/en/guide/migration/rsbuild-0-x.mdx
+++ b/website/docs/en/guide/migration/rsbuild-0-x.mdx
@@ -92,7 +92,7 @@ export default {
 };
 ```
 
-## [Important] Rspack Config Validation
+## [Important] Rspack config validation
 
 Rsbuild now enables Rspack's scheme validation by default to ensure the Rspack configuration is correct.
 
diff --git a/website/docs/en/guide/migration/vite.mdx b/website/docs/en/guide/migration/vite.mdx
index 5d75daee4e..76b8e46eb0 100644
--- a/website/docs/en/guide/migration/vite.mdx
+++ b/website/docs/en/guide/migration/vite.mdx
@@ -2,7 +2,7 @@
 
 This chapter introduces how to migrate a Vite project to Rsbuild.
 
-## Installing Dependencies
+## Installing dependencies
 
 First, you need to replace the npm dependencies of Vite with Rsbuild's dependencies.
 
@@ -33,7 +33,7 @@ Next, you need to update the npm scripts in your package.json to use Rsbuild's C
 }
 ```
 
-## Create Configuration File
+## Create configuration file
 
 Create a Rsbuild configuration file `rsbuild.config.ts` in the same directory as package.json, and add the following content:
 
@@ -45,7 +45,7 @@ export default defineConfig({
 });
 ```
 
-## Build Entry
+## Build entry
 
 The default build entry points for Rsbuild and Vite are different. Vite uses `index.html` as the default entry, while Rsbuild uses `src/index.js`.
 
@@ -74,7 +74,7 @@ export default {
 
 Rsbuild will automatically inject the `<script>` tags into the generated HTML files during the build process.
 
-## Migrating Plugins
+## Migrating plugins
 
 Most common Vite plugins can be easily migrated to Rsbuild plugins, such as:
 
@@ -99,7 +99,7 @@ Most common Vite plugins can be easily migrated to Rsbuild plugins, such as:
 
 You can refer to [Plugin List](/plugins/list/index) to learn more about available plugins.
 
-## Configuration Migration
+## Configuration migration
 
 Here is the corresponding Rsbuild configuration for Vite configuration:
 
@@ -155,7 +155,7 @@ Notes:
 
 - The above table does not cover all configurations of Vite, feel free to add more.
 
-## Environment Variables
+## Environment variables
 
 Vite injects environment variables starting with `VITE_` into the client code by default, while Rsbuild injects environment variables starting with `PUBLIC_` by default (see [public variables](/guide/advanced/env-vars#public-variables)).
 
@@ -206,7 +206,7 @@ export default defineConfig({
 });
 ```
 
-## Preset Types
+## Preset types
 
 Vite provides some preset type definitions through the `vite-env.d.ts` file. When migrating to Rsbuild, you can use the [preset types](/guide/basic/typescript#preset-types) provided by `@rsbuild/core`:
 
@@ -215,7 +215,7 @@ Vite provides some preset type definitions through the `vite-env.d.ts` file. Whe
 + /// <reference types="@rsbuild/core/types" />
 ```
 
-## Glob Import
+## Glob import
 
 Vite provides `import.meta.glob()` for importing multiple modules.
 
@@ -248,13 +248,13 @@ for (const path of context.keys()) {
 }
 ```
 
-## Validating Results
+## Validating results
 
 After completing the above steps, you have completed the basic migration from Vite to Rsbuild. You can now run the `npm run dev` command to try starting the dev server.
 
 If you encounter any issues during the build process, please debug according to the error log, or check the Vite configuration to see if there are any necessary configurations that have not been migrated to Rsbuild.
 
-## Contents Supplement
+## Contents supplement
 
 The current document only covers part of the migration process. If you find suitable content to add, feel free to contribute to the documentation via pull request 🤝.
 
diff --git a/website/docs/en/guide/migration/vue-cli.mdx b/website/docs/en/guide/migration/vue-cli.mdx
index 38811b8ad9..c25ac40ddc 100644
--- a/website/docs/en/guide/migration/vue-cli.mdx
+++ b/website/docs/en/guide/migration/vue-cli.mdx
@@ -2,7 +2,7 @@
 
 This chapter introduces how to migrate a [Vue CLI](https://github.com/vuejs/vue-cli) project to Rsbuild.
 
-## Install Dependencies
+## Install dependencies
 
 First, you need to replace the npm dependencies of Vue CLI with Rsbuild's dependencies.
 
@@ -38,7 +38,7 @@ Next, you need to update the npm scripts in the package.json file to Rsbuild's C
 Rsbuild does not integrate ESLint, so it does not provide a command to replace `vue-cli-service lint`. You can directly use ESLint's [CLI commands](https://eslint.org/docs/latest/use/command-line-interface) as an alternative.
 :::
 
-## Create Configuration File
+## Create configuration file
 
 Create a Rsbuild configuration file `rsbuild.config.ts` in the same directory as package.json, and add the following content:
 
@@ -61,7 +61,7 @@ export default defineConfig({
 If your project is based on Vue 2, use `import { pluginVue2 } from '@rsbuild/plugin-vue2';`.
 :::
 
-## HTML Template
+## HTML template
 
 Vue CLI uses the `public/index.html` file as the default HTML template. In Rsbuild, you can specify the HTML template through [html.template](/config/html/template):
 
@@ -82,7 +82,7 @@ In the HTML template, if you are using the `BASE_URL` variable from Vue CLI, rep
 
 This completes the basic migration from Vue CLI to Rsbuild. You can now run the `npm run serve` command to try starting the dev server.
 
-## Configuration Migration
+## Configuration migration
 
 Here is the corresponding Rsbuild configuration for Vue CLI configuration:
 
@@ -106,7 +106,7 @@ Notes:
 - When migrating `configureWebpack`, note that most of the Webpack and Rsbuild configs are the same, but there are also some differences or functionalities not implemented in Rsbuild.
 - The above table does not cover all configurations of Vue CLI, feel free to add more.
 
-## Environment Variables
+## Environment variables
 
 Vue CLI injects environment variables starting with `VUE_APP_` into the client code by default, while Rsbuild injects environment variables starting with `PUBLIC_` by default (see [public variables](/guide/advanced/env-vars#public-variables)).
 
@@ -124,7 +124,7 @@ export default defineConfig({
 });
 ```
 
-## Contents Supplement
+## Contents supplement
 
 The current document only covers part of the migration process. If you find suitable content to add, feel free to contribute to the documentation via pull request 🤝.
 
diff --git a/website/docs/en/guide/migration/webpack.mdx b/website/docs/en/guide/migration/webpack.mdx
index 2a52f05fc0..f83415351a 100644
--- a/website/docs/en/guide/migration/webpack.mdx
+++ b/website/docs/en/guide/migration/webpack.mdx
@@ -2,7 +2,7 @@
 
 This section introduces how to migrate a project using webpack to Rsbuild.
 
-## Installing Dependencies
+## Installing dependencies
 
 First, you need to replace the npm dependencies of webpack with Rsbuild's dependencies.
 
@@ -31,7 +31,7 @@ Next, you need to update the npm scripts in your package.json to use Rsbuild's C
 }
 ```
 
-## Create Configuration File
+## Create configuration file
 
 Create a Rsbuild configuration file `rsbuild.config.ts` in the same directory as package.json, and add the following content:
 
@@ -45,7 +45,7 @@ export default defineConfig({
 
 > See [Configure Rsbuild](/guide/basic/configure-rsbuild) for more.
 
-## Configuration Migration
+## Configuration migration
 
 In a webpack project, there might be some complex `webpack.config.js` configuration files.
 
@@ -69,7 +69,7 @@ export default {
 
 > See [Configure Rspack](/guide/basic/configure-rspack) for more.
 
-### Build Entry
+### Build entry
 
 webpack uses the `entry` field to set the build entry. In Rsbuild, you can use [source.entry](/config/source/entry) to set it.
 
@@ -84,7 +84,7 @@ export default {
 };
 ```
 
-### Cleaning Up Config
+### Cleaning up config
 
 Since Rsbuild has built-in some common loaders and plugins, you can remove the following dependencies, which will significantly improve the dependency installation speed of the project:
 
@@ -105,7 +105,7 @@ Since Rsbuild has built-in some common loaders and plugins, you can remove the f
 The above only lists some of the common dependencies that can be removed. In actual webpack projects, there may be many other dependencies, please handle them as appropriate.
 :::
 
-### Using Plugins
+### Using plugins
 
 Rsbuild offers a rich set of plugins that provide out-of-the-box support for common scenarios. You can refer to the [Plugin List](/plugins/list/index) documentation to learn about these plugins.
 
@@ -150,17 +150,17 @@ Most of the common webpack loaders and plugins can still be used in Rsbuild, but
 | [eslint-webpack-plugin](https://www.npmjs.com/package/eslint-webpack-plugin)                   | [ESLint Plugin](https://github.com/rspack-contrib/rsbuild-plugin-eslint)                                        |
 | [babel-plugin-styled-components](https://www.npmjs.com/package/babel-plugin-styled-components) | [Styled Components Plugin](https://github.com/rsbuild-contrib/rsbuild-plugin-styled-components)                 |
 
-### Configure Dev Server
+### Configure dev server
 
 Rsbuild does not support the use of Rspack's [devServer](https://rspack.dev/config/dev-server) config. Please refer to [Rspack Dev Server](/guide/basic/server#rspack-dev-server) for replacement.
 
-## Validating Results
+## Validating results
 
 After completing the above steps, you have completed the basic migration from webpack to Rsbuild. You can now run the `npm run dev` command to try starting the dev server.
 
 If you encounter any issues during the build process, please debug according to the error log, or check the webpack configuration to see if there are any necessary configurations that have not been migrated to Rsbuild.
 
-## Contents Supplement
+## Contents supplement
 
 The current document only covers part of the migration process. If you find suitable content to add, feel free to contribute to the documentation via pull request 🤝.
 
diff --git a/website/docs/en/guide/optimization/build-performance.mdx b/website/docs/en/guide/optimization/build-performance.mdx
index 0f8084805f..2936e6953c 100644
--- a/website/docs/en/guide/optimization/build-performance.mdx
+++ b/website/docs/en/guide/optimization/build-performance.mdx
@@ -1,20 +1,20 @@
-# Improve Build Performance
+# Improve build performance
 
 Rsbuild optimizes build performance by default, but as the project becomes larger, you may encounter some build performance problems.
 
 This document provides some optional speed-up methods, developers can choose some of them to improve the build performance.
 
-## Performance Profiling
+## Performance profiling
 
 Performing a performance analysis can help you identify performance bottlenecks in your project, allowing for targeted optimization.
 
 Please refer to the [Performance Building Analysis](/guide/debug/build-profiling) section for more information.
 
-## General Optimization
+## General optimization
 
 The following are some general optimization methods, which can speed up the development build and production build.
 
-### Reducing Modules
+### Reducing modules
 
 Optimizing the number of modules referenced by the application can reduce the bundle size and improve build performance. Please read the [Bundle Size Optimization](/guide/optimization/optimize-bundle) section to learn some optimization methods.
 
@@ -28,7 +28,7 @@ Please refer to [Tailwind CSS - Optimize Build Performance](/guide/basic/tailwin
 
 The following are methods for improving performance in development mode.
 
-### Enable Lazy Compilation
+### Enable lazy compilation
 
 Enabling lazy compilation can significantly reduce the number of modules compiled at dev startup and improve startup time.
 
@@ -42,7 +42,7 @@ export default {
 
 > Please refer to [dev.lazyCompilation](/config/dev/lazy-compilation) for more information.
 
-### Source Map Format
+### Source map format
 
 In order to provide a good debugging experience, Rsbuild uses the `cheap-module-source-map` format source map by default in development mode, which is a high-quality source map format and will bring certain performance overhead.
 
diff --git a/website/docs/en/guide/optimization/code-splitting.mdx b/website/docs/en/guide/optimization/code-splitting.mdx
index fd2423fc87..da62469efd 100644
--- a/website/docs/en/guide/optimization/code-splitting.mdx
+++ b/website/docs/en/guide/optimization/code-splitting.mdx
@@ -1,4 +1,4 @@
-# Code Splitting
+# Code splitting
 
 A great chunk splitting strategy is very important to improve the loading performance of the application. It can make full use of the browser's caching mechanism to reduce the number of requests and improve the loading speed of the application.
 
@@ -158,7 +158,7 @@ export default {
 };
 ```
 
-## Custom Splitting Strategy
+## Custom splitting strategy
 
 In addition to using the built-in strategies, you can also customize the splitting strategy to meet more customization needs. Custom strategy is divided into two parts:
 
@@ -167,7 +167,7 @@ In addition to using the built-in strategies, you can also customize the splitti
 
 It is worth noting that these two custom capabilities can be used together with the built-in strategy, that is, you can use the built-in strategy to split commonly used packages, and then use the custom function to split other packages.
 
-### Custom Group
+### Custom group
 
 Rsbuild supports custom group, which is more flexible than the built-in strategies, and simpler than writing Rspack's `splitChunks` config.
 
@@ -191,7 +191,7 @@ Through `forceSplitting` config, you can easily split some packages into a Chunk
 
 Chunks split using the `forceSplitting` configuration will be inserted into the HTML file as resources requested for the initial screen using `<script>` tags. Therefore, please split them appropriately based on the actual scenario to avoid excessive size of initial screen resources.
 
-### Custom Config
+### Custom config
 
 In addition to using custom grouping, you can also customize Rspack's `splitChunks` config through `override`, for example:
 
@@ -234,7 +234,7 @@ export default {
 
 The `override` config will be merged with Rspack's `splitChunks` config. For specific config details, please refer to [Rspack - splitChunks](https://rspack.dev/config/optimization#optimization-splitchunks).
 
-## Using Dynamic Import for Code Splitting
+## Using dynamic import for code splitting
 
 In addition to the `chunkSplit` configurations, using [dynamic import](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import) for code splitting is also an important optimization technique that can effectively reduce the initial bundle size.
 
diff --git a/website/docs/en/guide/optimization/inline-assets.mdx b/website/docs/en/guide/optimization/inline-assets.mdx
index 3751cc57ee..bb88f057f9 100644
--- a/website/docs/en/guide/optimization/inline-assets.mdx
+++ b/website/docs/en/guide/optimization/inline-assets.mdx
@@ -1,4 +1,4 @@
-# Inline Static Assets
+# Inline static assets
 
 Inline static assets refer to the practice of including the content of a static asset directly in a HTML or JS file, instead of linking to an external file. This can improve the performance of a website by reducing the number of HTTP requests that the browser has to make to load the page.
 
@@ -6,7 +6,7 @@ However, static assets inlining also has some disadvantages, such as increasing
 
 Rsbuild will automatically inline static assets that are less than 4KiB, but sometimes you may need to manually control assets to force them to be inlined or not, and this document explains how to precisely control the inlining behavior of static assets.
 
-## Automatic Inlining
+## Automatic inlining
 
 By default, Rsbuild will inline assets when the file size of is less than a threshold (the default is 4KiB). When inlined, the asset will be converted to a Base64 encoded string and will no longer send a separate HTTP request. When the file size is greater than this threshold, it is loaded as a separate file with a separate HTTP request.
 
@@ -23,7 +23,7 @@ export default {
 };
 ```
 
-## Force Inlining
+## Force inlining
 
 You can force an asset to be inlined by adding the `inline` query when importing the asset, regardless of whether the asset's size is smaller than the size threshold.
 
@@ -112,7 +112,7 @@ export default {
 };
 ```
 
-## Type Declaration
+## Type declaration
 
 When you use URL queries such as `?inline` and `?url` in TypeScript code, TypeScript may prompt that the module is missing a type definition:
 
diff --git a/website/docs/en/guide/optimization/optimize-bundle.mdx b/website/docs/en/guide/optimization/optimize-bundle.mdx
index 6edbc94157..d25bb13ac5 100644
--- a/website/docs/en/guide/optimization/optimize-bundle.mdx
+++ b/website/docs/en/guide/optimization/optimize-bundle.mdx
@@ -1,4 +1,4 @@
-# Bundle Size Optimization
+# Bundle size optimization
 
 Bundle size optimization is an important part in production build because it directly affects the user experience of online users. In this document, we will introduce some common bundle size optimization methods in Rsbuild.
 
@@ -50,7 +50,7 @@ BUNDLE_ANALYZE=true pnpm build
 
 See the [performance.bundleAnalyze](/config/performance/bundle-analyze) configuration for details.
 
-## Adjust Browserslist
+## Adjust browserslist
 
 The Rsbuild will compile the code according to the project's Browserslist config, and inject some Polyfills. If the project does not need to be compatible with legacy browsers, you can adjust the Browserslist and drop some legacy browsers, thereby reducing the compilation overhead on syntax and polyfill.
 
@@ -88,7 +88,7 @@ export default {
 Please read the [Browser Compatibility](/guide/advanced/browser-compatibility) chapter to know more about the usage of Browserslist.
 :::
 
-## Image Compression
+## Image compression
 
 In general front-end projects, the size of image often accounts for a large proportion of the total bundle size of the project.So if the image size can be reduced as much as possible, it will have a significant optimization effect on the project bundle size. You can enable image compression by registering a plugin in the Rsbuild:
 
@@ -102,7 +102,7 @@ export default {
 
 See details in [@rsbuild/plugin-image-compress](https://github.com/rspack-contrib/rsbuild-plugin-image-compress).
 
-## Split Chunk
+## Split chunk
 
 A great chunk splitting strategy is very important to improve the loading performance of the application. It can make full use of the browser's caching mechanism to reduce the number of requests and improve the loading speed of the application.
 
diff --git a/website/docs/en/guide/start/features.mdx b/website/docs/en/guide/start/features.mdx
index 0ac8108920..c83d4c7ded 100644
--- a/website/docs/en/guide/start/features.mdx
+++ b/website/docs/en/guide/start/features.mdx
@@ -50,7 +50,7 @@ Here are all the main features supported by Rsbuild.
 | Inline JS files         | Optional feature, inline JS files into HTML  | <ul><li>[Inline Static Assets](/guide/optimization/inline-assets)</li><li>[output.inlineScripts](/config/output/inline-scripts)</li></ul> |
 | Inline CSS files        | Optional feature, inline CSS files into HTML | <ul><li>[Inline Static Assets](/guide/optimization/inline-assets)</li><li>[output.inlineStyles](/config/output/inline-styles)</li></ul>   |
 
-## Development and Preview
+## Development and preview
 
 | Features   | Description                                                                    | Links                                                           |
 | ---------- | ------------------------------------------------------------------------------ | --------------------------------------------------------------- |
@@ -59,7 +59,7 @@ Here are all the main features supported by Rsbuild.
 | Open page  | Optional feature, automatically open page in browser when starting server      | <ul><li>[server.open](/config/server/open)</li></ul>            |
 | HTTPS      | Optional feature, enable HTTPS server                                          | <ul><li>[server.https](/config/server/https)</li></ul>          |
 
-## Frontend Framework
+## Frontend framework
 
 | Features      | Description                                                                | Links                                                                                              |
 | ------------- | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
@@ -73,7 +73,7 @@ Here are all the main features supported by Rsbuild.
 | Svelte        | Optional feature, enable compilation of Svelte component                   | <ul><li>[Svelte Plugin](/plugins/list/plugin-svelte)</li></ul>                                     |
 | Solid         | Optional feature, enable compilation of Solid JSX                          | <ul><li>[Solid Plugin](/plugins/list/plugin-solid)</li></ul>                                       |
 
-## Static Assets
+## Static assets
 
 | Features               | Description                                                                  | Links                                                                                                                                    |
 | ---------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/website/docs/en/guide/start/index.mdx b/website/docs/en/guide/start/index.mdx
index 40ad6a2885..0464a97c67 100644
--- a/website/docs/en/guide/start/index.mdx
+++ b/website/docs/en/guide/start/index.mdx
@@ -75,7 +75,7 @@ The following diagram illustrates the relationship between Rsbuild and other too
 
 Come and chat with us on [Discord](https://discord.gg/XsaKEEk4mW)! The Rspack / Rsbuild team and users are active there, and we're always looking for contributions.
 
-## ✨ Next Step
+## ✨ Next step
 
 You may want:
 
diff --git a/website/docs/en/guide/start/quick-start.mdx b/website/docs/en/guide/start/quick-start.mdx
index d811aea89d..9d29372ad9 100644
--- a/website/docs/en/guide/start/quick-start.mdx
+++ b/website/docs/en/guide/start/quick-start.mdx
@@ -1,12 +1,12 @@
-# Quick Start
+# Quick start
 
-## Online Example
+## Online example
 
 We provide an online example based on Rsbuild. The example gives an intuitive feel for the build performance of Rspack and the development experience of Rsbuild:
 
 - [Rsbuild CodeSandbox example](https://codesandbox.io/p/github/rspack-contrib/rsbuild-codesandbox-example)
 
-## Setup Environment
+## Setup environment
 
 Rsbuild supports using [Node.js](https://nodejs.org/), [Deno](https://deno.com/), or [Bun](https://bun.sh/) as the runtime.
 
@@ -31,7 +31,7 @@ nvm install --lts
 nvm use --lts
 ```
 
-## Creating an Rsbuild Project
+## Creating an Rsbuild project
 
 You can use the `create-rsbuild` to create a new Rsbuild project. Just execute the following command:
 
@@ -63,7 +63,7 @@ When creating a project, you can choose from the following templates provided by
 | svelte   | [Svelte 5](https://svelte.dev/) | TypeScript        |
 | solid    | [Solid](https://solidjs.com/)   | TypeScript        |
 
-### Optional Tools
+### Optional tools
 
 `create-rsbuild` can help you set up some commonly used tools, including [Biome](https://github.com/biomejs/biome), [ESLint](https://github.com/eslint/eslint), and [prettier](https://github.com/prettier/prettier). You can use the arrow keys and the space bar to make your selections. If you don't need these tools, you can simply press Enter to skip.
 
@@ -79,7 +79,7 @@ When creating a project, you can choose from the following templates provided by
 Biome provides similar linting and formatting features to ESLint and Prettier. If you select Biome, you typically won't need to choose ESLint or Prettier as well.
 :::
 
-### Current Directory
+### Current directory
 
 If you need to create a project in the current directory, you can set the target folder to `.`:
 
@@ -93,7 +93,7 @@ If you need to create a project in the current directory, you can set the target
 │  Continue and override files
 ```
 
-### Quick Creation
+### Quick creation
 
 [create-rsbuild](https://www.npmjs.com/package/create-rsbuild) provides some CLI flags. By setting these CLI flags, you can skip the interactive selection steps and create the project with one command.
 
@@ -124,7 +124,7 @@ Templates:
   react-js, react-ts, vue3-js, vue3-ts, vue2-js, vue2-ts, svelte-js, svelte-ts, solid-js, solid-ts, vanilla-js, vanilla-ts
 ```
 
-## Migrate from Existing Projects
+## Migrate from existing projects
 
 If you need to migrate from an existing project to Rsbuild, you can refer to the following guides:
 
@@ -134,7 +134,7 @@ If you need to migrate from an existing project to Rsbuild, you can refer to the
 - [Migrate from Vite](/guide/migration/vite)
 - [Migrate from Modern.js Builder](/guide/migration/modern-builder)
 
-### Other Projects
+### Other projects
 
 For other types of projects, you can manually install the [@rsbuild/core](https://www.npmjs.com/package/@rsbuild/core) package:
 
@@ -146,7 +146,7 @@ Then refer to the guide and documentation to enable the features you need:
 - See [Plugin List](/plugins/list/index) to select Rsbuild plugins.
 - See [Configure Rsbuild](/guide/basic/configure-rsbuild) to configure Rsbuild.
 
-## Command Line Interface
+## Command line interface
 
 Rsbuild comes with a lightweight CLI that includes commands such as `dev` and `build`.
 
@@ -165,11 +165,11 @@ Rsbuild comes with a lightweight CLI that includes commands such as `dev` and `b
 
 Refer to the [CLI](/guide/basic/cli) to learn about all available commands and options.
 
-## Entry Module
+## Entry module
 
 By default, Rsbuild CLI uses `src/index.(js|ts|jsx|tsx)` as the entry module. You can modify the entry module using the [source.entry](/config/source/entry) option.
 
-## Core Packages
+## Core packages
 
 ### @rsbuild/core
 
@@ -203,7 +203,7 @@ Rsbuild core package, providing CLI commands and JavaScript API.
 
 Create a new Rsbuild project.
 
-## Next Step
+## Next step
 
 You may want:
 
diff --git a/website/docs/en/plugins/dev/core.mdx b/website/docs/en/plugins/dev/core.mdx
index 392b1efd4e..4edfe234b4 100644
--- a/website/docs/en/plugins/dev/core.mdx
+++ b/website/docs/en/plugins/dev/core.mdx
@@ -1,4 +1,4 @@
-# Plugin Core
+# Plugin core
 
 This section describes the core plugin types and APIs.
 
@@ -78,7 +78,7 @@ const pluginBar = {
 
 The Bar plugin is configured with the Foo plugin in its `post` field, so the Foo plugin will always be executed after the Bar plugin.
 
-### Removing Plugins
+### Removing plugins
 
 You can remove other plugins within a plugin using the `remove` field.
 
@@ -199,7 +199,7 @@ const pluginPug = () => ({
 });
 ```
 
-### Descriptor Param
+### Descriptor param
 
 The descriptor param is an object describing the module's matching conditions.
 
@@ -261,7 +261,7 @@ api.transform({ test: /\.node$/, raw: true }, ({ code }) => {
 - `layer`: the same as Rspack's [Rule.layer](https://rspack.dev/config/module#rulelayer).
 - `issuerLayer`: the same as Rspack's [Rule.issuerLayer](https://rspack.dev/config/module#ruleissuerlayer).
 
-### Handler Param
+### Handler param
 
 The handler param is a transformation function that takes the current module code and returns the transformed code.
 
@@ -347,7 +347,7 @@ api.resolve(({ resolveData }) => {
 });
 ```
 
-### Handler Param
+### Handler param
 
 The `handler` parameter is a callback function that receives a module require information and allows you to modify it.
 
@@ -433,7 +433,7 @@ api.processAssets({ stage: 'optimize' }, ({ assets, compilation }) => {
 });
 ```
 
-### Descriptor Param
+### Descriptor param
 
 The descriptor parameter is an object to describes the stage and matching conditions that trigger `processAssets`.
 
@@ -476,7 +476,7 @@ api.processAssets(
 );
 ```
 
-### Handler Param
+### Handler param
 
 The `handler` parameter is a callback function that receives an assets object and allows you to modify it.
 
@@ -613,7 +613,7 @@ const pluginChild = () => ({
 });
 ```
 
-### Type Declaration
+### Type declaration
 
 You can declare types through the generics of the function:
 
@@ -637,7 +637,7 @@ const pluginChild = () => ({
 });
 ```
 
-### Execution Order
+### Execution order
 
 When communicating between plugins, you need to be aware of the order in which the plugins are executed.
 
diff --git a/website/docs/en/plugins/dev/hooks.mdx b/website/docs/en/plugins/dev/hooks.mdx
index 2e7c17f62a..0e700bc406 100644
--- a/website/docs/en/plugins/dev/hooks.mdx
+++ b/website/docs/en/plugins/dev/hooks.mdx
@@ -1,10 +1,10 @@
-# Plugin Hooks
+# Plugin hooks
 
 This chapter introduces the plugin hooks available for Rsbuild plugins.
 
 ## Overview
 
-### Common Hooks
+### Common hooks
 
 - [modifyRsbuildConfig](#modifyrsbuildconfig): Modify the configuration passed to Rsbuild.
 - [modifyEnvironmentConfig](#modifyenvironmentconfig): Modify the Rsbuild configuration of a specific environment.
@@ -17,7 +17,7 @@ This chapter introduces the plugin hooks available for Rsbuild plugins.
 - [onAfterEnvironmentCompile](#onafterenvironmentcompile): Called after the compilation of a single environment. You can get the build result information.
 - [onExit](#onexit): Called when the process is about to exit.
 
-### Dev Hooks
+### Dev hooks
 
 Called only when running the `rsbuild dev` command or the `rsbuild.startDevServer()` method.
 
@@ -29,7 +29,7 @@ Called only when Rsbuild is restarted or when the `close()` method of `rsbuild.b
 
 - [onCloseDevServer](#onclosedevserver): Called when the dev server is closed.
 
-### Build Hooks
+### Build hooks
 
 Called only when running the `rsbuild build` command or the `rsbuild.build()` method.
 
@@ -40,16 +40,16 @@ Called only when Rsbuild is restarted or when the `close()` method of `rsbuild.b
 
 - [onCloseBuild](#onclosebuild): Called when the build is closed.
 
-### Preview Hooks
+### Preview hooks
 
 Called only when running the `rsbuild preview` command or the `rsbuild.preview()` method.
 
 - [onBeforeStartProdServer](#onbeforestartprodserver): Called before starting the production server.
 - [onAfterStartProdServer](#onafterstartprodserver): Called after starting the production server.
 
-## Hooks Order
+## Hooks order
 
-### Dev Hooks
+### Dev hooks
 
 When the `rsbuild dev` command or `rsbuild.startDevServer()` method is executed, Rsbuild will execute the following hooks in order:
 
@@ -75,7 +75,7 @@ When rebuilding, the following hooks will be triggered again:
 - [onAfterEnvironmentCompile](#onafterenvironmentcompile)
 - [onDevCompileDone](#ondevcompiledone)
 
-### Build Hooks
+### Build hooks
 
 When the `rsbuild build` command or `rsbuild.build()` method is executed, Rsbuild will execute the following hooks in order:
 
@@ -101,7 +101,7 @@ When rebuilding, the following hooks will be triggered again:
 - [onAfterEnvironmentCompile](#onafterenvironmentcompile)
 - [onAfterBuild](#onafterbuild)
 
-### Preview Hooks
+### Preview hooks
 
 When executing the `rsbuild preview` command or `rsbuild.preview()` method, Rsbuild will execute the following hooks in order:
 
@@ -111,16 +111,16 @@ When executing the `rsbuild preview` command or `rsbuild.preview()` method, Rsbu
 - [onAfterStartProdServer](#onafterstartprodserver)
 - [onExit](#onexit)
 
-## Global Hooks vs Environment Hooks
+## Global hooks vs environment hooks
 
 In Rsbuild, some of the plugin hooks are global hooks. The execution of these hooks is often related to Rsbuild's own startup process or global logic and is shared under all environments. Such as:
 
 - `modifyRsbuildConfig` is used to modify the basic configuration of Rsbuild. The basic configuration will eventually be merged with the environment configuration;
-- `onBeforeStartDevServer` and `onAfterStartDevServer` are related to the Rsbuild dev server startup process, all environments share Rsbuild's dev server, middlewares, and Web Socket.
+- `onBeforeStartDevServer` and `onAfterStartDevServer` are related to the Rsbuild dev server startup process, all environments share Rsbuild's dev server, middlewares, and WebSocket.
 
 Correspondingly, there are some plugin hooks that are related to the current environment. These hooks are executed with a specific environment context and are triggered multiple times depending on the environment.
 
-### Global Hooks
+### Global hooks
 
 - [modifyRsbuildConfig](#modifyrsbuildconfig)
 - [onBeforeStartDevServer](#onbeforestartdevserver)
@@ -136,7 +136,7 @@ Correspondingly, there are some plugin hooks that are related to the current env
 - [onAfterStartProdServer](#onafterstartprodserver)
 - [onExit](#onexit)
 
-### Environment Hooks
+### Environment hooks
 
 - [modifyEnvironmentConfig](#modifyenvironmentconfig)
 - [modifyBundlerChain](#modifybundlerchain)
@@ -145,9 +145,9 @@ Correspondingly, there are some plugin hooks that are related to the current env
 - [onBeforeEnvironmentCompile](#onbeforeenvironmentcompile)
 - [onAfterEnvironmentCompile](#onafterenvironmentcompile)
 
-## Callback Order
+## Callback order
 
-### Default Behavior
+### Default behavior
 
 If multiple plugins register the same hook, the callback functions of the hook will execute in the order in which they were registered.
 
@@ -201,7 +201,7 @@ const plugin2 = () => ({
 rsbuild.addPlugins([plugin1, plugin2]);
 ```
 
-## Common Hooks
+## Common hooks
 
 ### modifyRsbuildConfig
 
@@ -588,7 +588,7 @@ const myPlugin = () => ({
 });
 ```
 
-## Build Hooks
+## Build hooks
 
 ### onBeforeBuild
 
@@ -644,7 +644,7 @@ const myPlugin = () => ({
 });
 ```
 
-## Dev Hooks
+## Dev hooks
 
 ### onBeforeStartDevServer
 
@@ -741,7 +741,7 @@ rsbuild.onCloseDevServer(async () => {
 });
 ```
 
-## Preview Hooks
+## Preview hooks
 
 ### onBeforeStartProdServer
 
@@ -780,7 +780,7 @@ const myPlugin = () => ({
 });
 ```
 
-## Other Hooks
+## Other hooks
 
 ### onExit
 
diff --git a/website/docs/en/plugins/dev/index.mdx b/website/docs/en/plugins/dev/index.mdx
index 8886db73e5..f6d11f62b3 100644
--- a/website/docs/en/plugins/dev/index.mdx
+++ b/website/docs/en/plugins/dev/index.mdx
@@ -1,4 +1,4 @@
-# Plugin System
+# Plugin system
 
 Rsbuild provides a lightweight yet powerful plugin system to implement most of its functionality and allows for user extension.
 
@@ -59,11 +59,11 @@ const rsbuildPlugin = () => ({
 });
 ```
 
-## Developing Plugins
+## Developing plugins
 
 Plugins provide a function similar to `(options?: PluginOptions) => RsbuildPlugin` as an entry point.
 
-### Plugin Example
+### Plugin example
 
 ```ts title="pluginFoo.ts"
 import type { RsbuildPlugin } from '@rsbuild/core';
@@ -94,7 +94,7 @@ export default {
 };
 ```
 
-### Plugin Structure
+### Plugin structure
 
 Function-based plugins can **accept an options object** and **return a plugin instance**, managing internal state through closures.
 
@@ -104,7 +104,7 @@ The roles of each part are as follows:
 - `setup` serves as the main entry point for the plugin logic.
 - The `api` object contains various hooks and utility functions.
 
-### Naming Convention
+### Naming convention
 
 The naming convention for plugins is as follows:
 
@@ -126,11 +126,11 @@ export const pluginFooBar = (): RsbuildPlugin => ({
 The `name` of official Rsbuild plugins uniformly uses `rsbuild:` as a prefix, for example, `rsbuild:react` corresponds to `@rsbuild/plugin-react`.
 :::
 
-### Template Repository
+### Template repository
 
 [rsbuild-plugin-template](https://github.com/rspack-contrib/rsbuild-plugin-template) is a minimal Rsbuild plugin template repository that you can use as a basis for developing your Rsbuild plugin.
 
-### Environment Plugin
+### Environment plugin
 
 Rsbuild supports building outputs for multiple environments at the same time, and supports [add plugins for specified environment](/guide/advanced/environments#add-plugins-for-specified-environment).
 
@@ -165,7 +165,7 @@ export const pluginFoo = (options: PluginFooOptions = {}): RsbuildPlugin => ({
 });
 ```
 
-### Reference Other Plugins
+### Reference other plugins
 
 Rsbuild's [plugins](/config/plugins) config supports passing a nested array, which means you can reference and register other Rsbuild plugins within your plugin.
 
@@ -185,7 +185,7 @@ export const pluginFoo = (): RsbuildPlugin => {
 };
 ```
 
-## Lifetime Hooks
+## Lifetime hooks
 
 Rsbuild uses lifetime planning work internally, and plugins can also register hooks to take part in any stage of the workflow and implement their own features.
 
@@ -193,7 +193,7 @@ The full list of Rsbuild's lifetime hooks can be found in the [API References](/
 
 The Rsbuild does not take over the hooks of the underlying Rspack, whose documents can be found here: [Rspack Plugin API](https://rspack.dev/api/plugin-api).
 
-## Use Rsbuild Config
+## Use Rsbuild config
 
 Custom plugins can usually get config from function parameters,
 just define and use it at your pleasure.
@@ -273,7 +273,7 @@ Therefore, the best way to use configuration options is to
 - **Modify the config** with `api.modifyRsbuildConfig(config => {})`
 - Read `api.getNormalizedConfig()` as the **actual config used by the plugin** in the further lifetime.
 
-## Modify Rspack Configuration
+## Modify Rspack configuration
 
 Rsbuild plugin allows you to modify the built-in Rspack configuration, including:
 
diff --git a/website/docs/en/plugins/list/index.mdx b/website/docs/en/plugins/list/index.mdx
index 6e43116832..e25cc117a6 100644
--- a/website/docs/en/plugins/list/index.mdx
+++ b/website/docs/en/plugins/list/index.mdx
@@ -1,16 +1,16 @@
-# Plugin List
+# Plugin list
 
-## Plugin System
+## Plugin system
 
 You can read about the functionality of Rsbuild plugins and how to develop an Rsbuild plugin in the [Plugin System](/plugins/dev/index) documentation.
 
-## Using Plugins
+## Using plugins
 
 You can register Rsbuild plugins in the `rsbuild.config.ts` file using the `plugins` option. For more details, refer to [plugins](/config/plugins).
 
 If you are using Rsbuild's JavaScript API, you can register the plugin using the [addPlugins](/api/javascript-api/instance#rsbuildaddplugins) method.
 
-## Official Plugins
+## Official plugins
 
 The following are official plugins that can be used in Rsbuild.
 
@@ -82,7 +82,7 @@ The following are common framework-agnostic plugins:
 You can find the source code of all official plugins in [web-infra-dev/rsbuild](https://github.com/web-infra-dev/rsbuild) and [rspack-contrib](https://github.com/rspack-contrib).
 :::
 
-## Community Plugins
+## Community plugins
 
 You can check out the Rsbuild plugins provided by the community at [awesome-rspack - Rsbuild Plugins](https://github.com/web-infra-dev/awesome-rspack?tab=readme-ov-file#rsbuild-plugins).
 
diff --git a/website/docs/en/plugins/list/plugin-assets-retry.mdx b/website/docs/en/plugins/list/plugin-assets-retry.mdx
index 749ecf77bb..198ef144c9 100644
--- a/website/docs/en/plugins/list/plugin-assets-retry.mdx
+++ b/website/docs/en/plugins/list/plugin-assets-retry.mdx
@@ -1,4 +1,4 @@
-# Assets Retry Plugin
+# Assets retry plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -6,9 +6,9 @@ import { SourceCode } from 'rspress/theme';
 
 The Assets Retry plugin is used to automatically resend requests when static assets fail to load.
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -16,7 +16,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/plugin-assets-retry -D" />
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
diff --git a/website/docs/en/plugins/list/plugin-babel.mdx b/website/docs/en/plugins/list/plugin-babel.mdx
index bf0bb39522..c94ed695bc 100644
--- a/website/docs/en/plugins/list/plugin-babel.mdx
+++ b/website/docs/en/plugins/list/plugin-babel.mdx
@@ -1,4 +1,4 @@
-# Babel Plugin
+# Babel plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -6,9 +6,9 @@ import { SourceCode } from 'rspress/theme';
 
 Rsbuild uses SWC transpilation by default. When existing functions cannot meet the requirements, and some Babel presets or plugins need to be added for additional processing, you can use Rsbuild's Babel Plugin.
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -16,7 +16,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/plugin-babel -D" />
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
@@ -28,7 +28,7 @@ export default {
 };
 ```
 
-## Compilation Cache
+## Compilation cache
 
 After using the Babel plugin, Rsbuild will perform the Babel transpilation in addition to the standard SWC transpilation, which adds additional compilation overhead. This can cause a noticeable decrease in build speed.
 
@@ -75,7 +75,7 @@ const defaultOptions = {
 };
 ```
 
-#### Function Type
+#### Function type
 
 When configuration is of type `Function`, the default Babel configuration will be passed as the first parameter. You can directly modify the configuration object or return an object as the final `babel-loader` configuration.
 
@@ -103,7 +103,7 @@ The second parameter of the function provides some more convenient utility funct
 The above example is just for reference, usually you don't need to manually configure `babel-plugin-import`, because the Rsbuild already provides a more general `source.transformImport` configuration.
 :::
 
-#### Object Type
+#### Object type
 
 When configuration's type is `Object`, the config will be shallow merged with default config by `Object.assign`.
 
@@ -128,7 +128,7 @@ pluginBabel({
 });
 ```
 
-#### Util Functions
+#### Util functions
 
 When configuration is a Function, the tool functions available for the second parameter are as follows:
 
@@ -231,7 +231,7 @@ Used to specify the files that do not need to be compiled by Babel.
 
 Due to the performance overhead of Babel compilation, excluding certain files through `exclude` can reduce the number of modules compiled by Babel, thereby improving build performance.
 
-## Debugging Configs
+## Debugging configs
 
 After modifying the `babel-loader` configuration, you can view the final generated configuration in [Rsbuild debug mode](/guide/debug/debug-mode).
 
@@ -249,7 +249,7 @@ Then open the generated `rspack.config.web.mjs` file and search for the `babel-l
 
 ## FAQ
 
-### Compilation Freezes
+### Compilation freezes
 
 After using the babel plugin, if the compilation progress bar is stuck, but there is no Error log on the terminal, it is usually because an exception occurred during the compilation. In some cases, when Error is caught by webpack or other modules, the error log can not be output correctly. The most common scenario is that there is an exception in the Babel config, which is caught by webpack, and webpack swallows the Error in some cases.
 
diff --git a/website/docs/en/plugins/list/plugin-less.mdx b/website/docs/en/plugins/list/plugin-less.mdx
index f837e9f20d..4358cfa39f 100644
--- a/website/docs/en/plugins/list/plugin-less.mdx
+++ b/website/docs/en/plugins/list/plugin-less.mdx
@@ -1,4 +1,4 @@
-# Less Plugin
+# Less plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -6,9 +6,9 @@ import { SourceCode } from 'rspress/theme';
 
 Use [Less](https://lesscss.org/) as the CSS preprocessor, implemented based on [less-loader](https://github.com/webpack-contrib/less-loader).
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -23,7 +23,7 @@ import { PackageManagerTabs } from '@theme';
 
 :::
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
@@ -120,7 +120,7 @@ pluginLess({
 });
 ```
 
-## Modifying Less Version
+## Modifying Less version
 
 In some scenarios, if you need to use a specific version of Less instead of the built-in Less v4 in Rsbuild, you can install the desired Less version in your project and set it up using the `implementation` option of the `less-loader`.
 
diff --git a/website/docs/en/plugins/list/plugin-preact.mdx b/website/docs/en/plugins/list/plugin-preact.mdx
index b797f7cef0..c23f107801 100644
--- a/website/docs/en/plugins/list/plugin-preact.mdx
+++ b/website/docs/en/plugins/list/plugin-preact.mdx
@@ -1,4 +1,4 @@
-# Preact Plugin
+# Preact plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -6,9 +6,9 @@ import { SourceCode } from 'rspress/theme';
 
 The Preact plugin provides support for Preact, integrating features such as JSX compilation and React aliasing.
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -16,7 +16,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/plugin-preact -D" />
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
diff --git a/website/docs/en/plugins/list/plugin-react.mdx b/website/docs/en/plugins/list/plugin-react.mdx
index c6e6da4278..04983f6c2c 100644
--- a/website/docs/en/plugins/list/plugin-react.mdx
+++ b/website/docs/en/plugins/list/plugin-react.mdx
@@ -1,4 +1,4 @@
-# React Plugin
+# React plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -6,9 +6,9 @@ import { SourceCode } from 'rspress/theme';
 
 The React plugin provides support for React, integrating features such as JSX compilation and React Refresh.
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -16,7 +16,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/plugin-react -D" />
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
diff --git a/website/docs/en/plugins/list/plugin-sass.mdx b/website/docs/en/plugins/list/plugin-sass.mdx
index 07c28af529..b29320339f 100644
--- a/website/docs/en/plugins/list/plugin-sass.mdx
+++ b/website/docs/en/plugins/list/plugin-sass.mdx
@@ -1,4 +1,4 @@
-# Sass Plugin
+# Sass plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -6,9 +6,9 @@ import { SourceCode } from 'rspress/theme';
 
 Use [Sass](https://sass-lang.com/) as the CSS preprocessor, implemented based on [sass-loader](https://github.com/webpack-contrib/sass-loader).
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -23,7 +23,7 @@ import { PackageManagerTabs } from '@theme';
 
 :::
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
@@ -117,7 +117,7 @@ pluginSass({
 
 ## Practices
 
-### Modify Sass Implementation
+### Modify Sass implementation
 
 Sass provides several implementations, including [sass](https://www.npmjs.com/package/sass), [sass-embedded](https://www.npmjs.com/package/sass-embedded), and [node-sass](https://www.npmjs.com/package/node-sass).
 
@@ -153,7 +153,7 @@ pluginSass({
 Sass's `legacy` API has been deprecated and will be removed in Sass 2.0. It is recommended to migrate to the `modern-compiler` API. For more details, see [Sass - Legacy JS API](https://sass-lang.com/documentation/breaking-changes/legacy-js-api/).
 :::
 
-### Ignore Sass Deprecation Warnings
+### Ignore Sass deprecation warnings
 
 Sass uses warning logs to notify you of deprecated usages that will be removed in future major releases of Sass. It is recommended to make changes as suggested by the logs. If you do not want to see these logs, you can ignore these warnings by using the [silenceDeprecations](https://sass-lang.com/documentation/js-api/interfaces/stringoptions/#silenceDeprecations) option in Sass.
 
diff --git a/website/docs/en/plugins/list/plugin-solid.mdx b/website/docs/en/plugins/list/plugin-solid.mdx
index a24b4bcbb6..1582113570 100644
--- a/website/docs/en/plugins/list/plugin-solid.mdx
+++ b/website/docs/en/plugins/list/plugin-solid.mdx
@@ -1,4 +1,4 @@
-# Solid Plugin
+# Solid plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -10,9 +10,9 @@ The Solid plugin provides support for Solid features. The plugin internally inte
 The Solid plugin relies on Babel transpilation and requires an additional [Babel Plugin](/plugins/list/plugin-babel). At the same time, adding the Babel plugin will cause additional compilation overhead.
 :::
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -20,7 +20,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/plugin-babel @rsbuild/plugin-solid -D" />
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
diff --git a/website/docs/en/plugins/list/plugin-stylus.mdx b/website/docs/en/plugins/list/plugin-stylus.mdx
index 621dea8e56..e9f8d2b64b 100644
--- a/website/docs/en/plugins/list/plugin-stylus.mdx
+++ b/website/docs/en/plugins/list/plugin-stylus.mdx
@@ -1,4 +1,4 @@
-# Stylus Plugin
+# Stylus plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -6,9 +6,9 @@ import { SourceCode } from 'rspress/theme';
 
 [Stylus](https://stylus-lang.com/) is an Expressive, dynamic and robust CSS preprocessor. With Stylus plugins, you can use Stylus as the CSS preprocessor.
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -16,7 +16,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/plugin-stylus -D" />
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
diff --git a/website/docs/en/plugins/list/plugin-svelte.mdx b/website/docs/en/plugins/list/plugin-svelte.mdx
index 9038a4fb9e..f9874b0805 100644
--- a/website/docs/en/plugins/list/plugin-svelte.mdx
+++ b/website/docs/en/plugins/list/plugin-svelte.mdx
@@ -1,4 +1,4 @@
-# Svelte Plugin
+# Svelte plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -6,9 +6,9 @@ import { SourceCode } from 'rspress/theme';
 
 The Svelte plugin provides support for Svelte components (`.svelte` files). The plugin internally integrates [svelte-loader](https://github.com/sveltejs/svelte-loader).
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -16,7 +16,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/plugin-svelte -D" />
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
diff --git a/website/docs/en/plugins/list/plugin-svgr.mdx b/website/docs/en/plugins/list/plugin-svgr.mdx
index 26c806c05d..5f1958b29f 100644
--- a/website/docs/en/plugins/list/plugin-svgr.mdx
+++ b/website/docs/en/plugins/list/plugin-svgr.mdx
@@ -1,4 +1,4 @@
-# SVGR Plugin
+# SVGR plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -8,9 +8,9 @@ By default, Rsbuild will treat SVG files as static assets. For processing rules,
 
 With SVGR plugin, Rsbuild supports transform SVG to React components via [SVGR](https://react-svgr.com/).
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -18,7 +18,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/plugin-svgr -D" />
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
@@ -32,7 +32,7 @@ export default {
 
 ## Example
 
-### Default Usage
+### Default usage
 
 After registering the plugin, when import an SVG in a JS file, if the imported path contains the `?react` suffix, Rsbuild will call SVGR to transform the SVG into a React component.
 
@@ -50,7 +50,7 @@ import logoURL from './static/logo.svg';
 console.log(logoURL); // => "/static/logo.6c12aba3.png"
 ```
 
-### Named Import
+### Named import
 
 `@rsbuild/plugin-svgr` supports named imports for `ReactComponent` when using SVGR. You need to set [svgrOptions.exportType](#svgroptionsexporttype) to `'named'`:
 
@@ -334,7 +334,7 @@ console.log(url); // => Resource url
 The query in the module path has a higher priority than `exclude` and `excludeImporter`. For example, if a module is excluded, adding `?react` can still make it transformed by SVGR.
 :::
 
-## Type Declaration
+## Type declaration
 
 When you reference an SVG asset in TypeScript code, TypeScript may prompt that the module is missing a type definition:
 
diff --git a/website/docs/en/plugins/list/plugin-vue.mdx b/website/docs/en/plugins/list/plugin-vue.mdx
index f801f01522..e67a1f735c 100644
--- a/website/docs/en/plugins/list/plugin-vue.mdx
+++ b/website/docs/en/plugins/list/plugin-vue.mdx
@@ -1,4 +1,4 @@
-# Vue Plugin
+# Vue plugin
 
 import { SourceCode } from 'rspress/theme';
 
@@ -10,9 +10,9 @@ The Vue plugin provides support for Vue 3 SFC (Single File Components). The plug
 For Vue 3 JSX / TSX syntax, please use the [Vue JSX plugin](https://github.com/rspack-contrib/rsbuild-plugin-vue-jsx).
 :::
 
-## Quick Start
+## Quick start
 
-### Install Plugin
+### Install plugin
 
 You can install the plugin using the following command:
 
@@ -20,7 +20,7 @@ import { PackageManagerTabs } from '@theme';
 
 <PackageManagerTabs command="add @rsbuild/plugin-vue -D" />
 
-### Register Plugin
+### Register plugin
 
 You can register the plugin in the `rsbuild.config.ts` file:
 
diff --git a/website/docs/zh/api/javascript-api/core.mdx b/website/docs/zh/api/javascript-api/core.mdx
index bb553f4160..971ec46280 100644
--- a/website/docs/zh/api/javascript-api/core.mdx
+++ b/website/docs/zh/api/javascript-api/core.mdx
@@ -1,4 +1,4 @@
-# Rsbuild Core
+# Rsbuild core
 
 本章节描述了 Rsbuild 提供的一些核心方法。
 
diff --git a/website/docs/zh/api/javascript-api/environment-api.mdx b/website/docs/zh/api/javascript-api/environment-api.mdx
index 7ba821f710..5aa687cd3e 100644
--- a/website/docs/zh/api/javascript-api/environment-api.mdx
+++ b/website/docs/zh/api/javascript-api/environment-api.mdx
@@ -4,7 +4,7 @@
 
 > 参考 [多环境构建](/guide/advanced/environments) 了解更多。
 
-## Environment Context
+## Environment context
 
 Environment context 是一个只读对象，提供一些和当前环境有关的上下文信息。
 
diff --git a/website/docs/zh/api/javascript-api/instance.mdx b/website/docs/zh/api/javascript-api/instance.mdx
index 5465004743..3423f7f3f7 100644
--- a/website/docs/zh/api/javascript-api/instance.mdx
+++ b/website/docs/zh/api/javascript-api/instance.mdx
@@ -1,4 +1,4 @@
-# Rsbuild Instance
+# Rsbuild instance
 
 本章节描述了 Rsbuild 实例对象上所有的属性和方法。
 
diff --git a/website/docs/zh/api/javascript-api/types.mdx b/website/docs/zh/api/javascript-api/types.mdx
index 6ed4d41a3a..df17c5d19b 100644
--- a/website/docs/zh/api/javascript-api/types.mdx
+++ b/website/docs/zh/api/javascript-api/types.mdx
@@ -1,4 +1,4 @@
-# Rsbuild Types
+# Rsbuild types
 
 本章节描述了 Rsbuild 提供的一些类型定义。
 
diff --git a/website/docs/zh/community/releases/v0-2.mdx b/website/docs/zh/community/releases/v0-2.mdx
index 26037d342a..f1dbc5b15d 100644
--- a/website/docs/zh/community/releases/v0-2.mdx
+++ b/website/docs/zh/community/releases/v0-2.mdx
@@ -63,7 +63,7 @@ export default {
 };
 ```
 
-## Write to Disk
+## Write to disk
 
 `dev.writeToDisk` 的默认值变更为 `false`.
 
@@ -109,7 +109,7 @@ pluginBabel([
 
 这种改变使我们能为 `pluginBabel` 添加更多选项，如 `include` 和 `exclude`。
 
-## Source Map
+## Source map
 
 `output.disableSourceMap` 已经更名为 `output.sourceMap`.
 
@@ -144,7 +144,7 @@ source map 的默认值已更新，以提升构建性能。
 - 之前：在开发阶段生成 JS / CSS 的 source map，在生产阶段生成 JS 的 source map。
 - 之后：在开发阶段生成 JS 的 source map，在生产阶段不生成 source map。
 
-## Inject Styles
+## Inject styles
 
 将 `output.disableCssExtract` 更名为 `output.injectStyles` 以更加直观：
 
diff --git a/website/docs/zh/config/dev/lazy-compilation.mdx b/website/docs/zh/config/dev/lazy-compilation.mdx
index 99d94b359e..02017526a2 100644
--- a/website/docs/zh/config/dev/lazy-compilation.mdx
+++ b/website/docs/zh/config/dev/lazy-compilation.mdx
@@ -42,7 +42,7 @@ Lazy compilation 是一个提升 dev 启动性能的良好手段，它可以按
 
 ## 示例
 
-### 启用 Lazy Compilation
+### 启用 Lazy compilation
 
 ```ts
 export default {
diff --git a/website/docs/zh/config/dev/live-reload.mdx b/website/docs/zh/config/dev/live-reload.mdx
index 322b5d5e22..b2b8f465b8 100644
--- a/website/docs/zh/config/dev/live-reload.mdx
+++ b/website/docs/zh/config/dev/live-reload.mdx
@@ -11,7 +11,7 @@
 
 ## 禁用 liveReload
 
-如果你需要禁用 liveReload，可以将 `dev.hmr` 和 `dev.liveReload` 同时设置为 `false`，此时页面上不会发起 Web Socket 请求到 dev server，也不会在文件变更时自动刷新页面。
+如果你需要禁用 liveReload，可以将 `dev.hmr` 和 `dev.liveReload` 同时设置为 `false`，此时页面上不会发起 WebSocket 请求到 dev server，也不会在文件变更时自动刷新页面。
 
 ```js
 export default {
diff --git a/website/docs/zh/config/output/filename.mdx b/website/docs/zh/config/output/filename.mdx
index 6e433390e9..ee6559b5ef 100644
--- a/website/docs/zh/config/output/filename.mdx
+++ b/website/docs/zh/config/output/filename.mdx
@@ -168,7 +168,7 @@ export default {
 除了 `output.filename.js` 和 `output.filename.css` 以外，其他类型的文件目前暂不支持使用函数。
 :::
 
-## Query Hash
+## Query hash
 
 如果你需要在资源的 URL query 上生成 hash 值，可以参考以下配置：
 
diff --git a/website/docs/zh/config/output/source-map.mdx b/website/docs/zh/config/output/source-map.mdx
index 703e34ea34..008c25f8d8 100644
--- a/website/docs/zh/config/output/source-map.mdx
+++ b/website/docs/zh/config/output/source-map.mdx
@@ -61,7 +61,7 @@ export default {
 };
 ```
 
-## JS Source Map
+## JS source map
 
 JS 文件的 source map 通过 `sourceMap.js` 来控制，可以传入 Rspack [devtool](https://rspack.dev/zh/config/devtool) 选项支持的所有 source map 格式，设置为 `false` 为关闭。
 
@@ -94,7 +94,7 @@ export default {
 };
 ```
 
-## CSS Source Map
+## CSS source map
 
 CSS 文件的 source map 通过 `sourceMap.css` 来控制，设置为 `true` 为开启，设置为 `false` 为关闭。
 
diff --git a/website/docs/zh/config/output/target.mdx b/website/docs/zh/config/output/target.mdx
index 51e29f5e55..b27ea49427 100644
--- a/website/docs/zh/config/output/target.mdx
+++ b/website/docs/zh/config/output/target.mdx
@@ -72,7 +72,7 @@ export default {
 - 将 Browserslist 的默认值设置为 `['node >= 16']`。
 - 将 [output.emitCss](/config/output/emit-css) 的默认值设置为 `false`。这意味着 CSS 代码不会被抽取为单独的文件，但产物中会包含 CSS Modules 的 id 信息。
 
-### Node Addons
+### Node addons
 
 当 `target` 为 `'node'` 时，Rsbuild 允许你在 JavaScript 文件中引入 Node.js [Addons](https://nodejs.org/api/addons.html)。
 
@@ -91,7 +91,7 @@ dist/index.js
 dist/addon.node
 ```
 
-## Web Worker 产物
+## Web Workers 产物
 
 指运行在 [Web Worker](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API) 环境的产物。
 
diff --git a/website/docs/zh/config/performance/bundle-analyze.mdx b/website/docs/zh/config/performance/bundle-analyze.mdx
index 05a8607299..d0204b7bce 100644
--- a/website/docs/zh/config/performance/bundle-analyze.mdx
+++ b/website/docs/zh/config/performance/bundle-analyze.mdx
@@ -15,7 +15,7 @@ const defaultConfig = {
 };
 ```
 
-## 启用 Bundle Analyze
+## 启用 Bundle analyze
 
 你有两种方式开启 `webpack-bundle-analyzer` 来分析构建产物的体积。
 
diff --git a/website/docs/zh/config/server/public-dir.mdx b/website/docs/zh/config/server/public-dir.mdx
index 4838b522d3..ff433720bf 100644
--- a/website/docs/zh/config/server/public-dir.mdx
+++ b/website/docs/zh/config/server/public-dir.mdx
@@ -91,7 +91,7 @@ export default {
 
 需要注意的是，将 `copyOnBuild` 的值为 false 后，如果执行 `rsbuild preview` 进行生产环境预览，将无法访问对应的静态资源文件。
 
-#### Node Target
+#### Node target
 
 默认情况下，当 [output.target](/config/output/target) 为 `'node'` 时，Rsbuild 不会复制 public 目录下的文件。
 
diff --git a/website/docs/zh/guide/advanced/browser-compatibility.mdx b/website/docs/zh/guide/advanced/browser-compatibility.mdx
index ea9a91aae4..34a41407dc 100644
--- a/website/docs/zh/guide/advanced/browser-compatibility.mdx
+++ b/website/docs/zh/guide/advanced/browser-compatibility.mdx
@@ -74,7 +74,7 @@ foo === null || foo === void 0 ? void 0 : foo.bar();
 
 如果代码被转换为 AST 成功，引擎会将 AST 转为可执行代码，并在引擎内部正常执行。
 
-### API Polyfill
+### API polyfill
 
 JavaScript 是解释型脚本语言，不同于 Rust 等编译型语言。Rust 会在编译阶段对代码中的调用进行检查，而 JavaScript 在真正运行到某一行代码之前，并不知道这一行代码所调用的函数是否存在，因此一些错误只有在运行时才会出现。
 
@@ -242,7 +242,7 @@ export default {
 };
 ```
 
-### UA Polyfill
+### UA polyfill
 
 Cloudflare 提供了一个 [polyfill 服务](https://cdnjs.cloudflare.com/polyfill/)，可以根据用户浏览器的 User-Agent 自动生成 polyfill 文件。
 
diff --git a/website/docs/zh/guide/advanced/browserslist.mdx b/website/docs/zh/guide/advanced/browserslist.mdx
index 6163c9601a..1d9a86ced2 100644
--- a/website/docs/zh/guide/advanced/browserslist.mdx
+++ b/website/docs/zh/guide/advanced/browserslist.mdx
@@ -211,7 +211,7 @@ Node 产物默认最低兼容到 Node.js 16.0 版本。
 node >= 16
 ```
 
-### Web Worker 产物
+### Web Workers 产物
 
 Web worker 产物默认的浏览器范围与 web 一致。
 
diff --git a/website/docs/zh/guide/advanced/env-vars.mdx b/website/docs/zh/guide/advanced/env-vars.mdx
index 5105429a28..472a2c287d 100644
--- a/website/docs/zh/guide/advanced/env-vars.mdx
+++ b/website/docs/zh/guide/advanced/env-vars.mdx
@@ -480,7 +480,7 @@ declare namespace NodeJS {
 }
 ```
 
-## Tree Shaking
+## Tree shaking
 
 `define` 还可以用于标记死代码以协助 Rspack 进行 tree shaking 优化。
 
diff --git a/website/docs/zh/guide/advanced/hmr.mdx b/website/docs/zh/guide/advanced/hmr.mdx
index 40b6dc39f9..fa4561e0ac 100644
--- a/website/docs/zh/guide/advanced/hmr.mdx
+++ b/website/docs/zh/guide/advanced/hmr.mdx
@@ -20,7 +20,7 @@ export default {
 };
 ```
 
-如果你需要同时禁用 HMR 和 liveReload，可以将 [dev.hmr](/config/dev/hmr) 和 [dev.liveReload](/config/dev/live-reload) 都设置为 `false`，此时页面上不会发起 Web Socket 请求到 dev server，也不会在文件变更时自动刷新页面。
+如果你需要同时禁用 HMR 和 liveReload，可以将 [dev.hmr](/config/dev/hmr) 和 [dev.liveReload](/config/dev/live-reload) 都设置为 `false`，此时页面上不会发起 WebSocket 请求到 dev server，也不会在文件变更时自动刷新页面。
 
 ```js title="rsbuild.config.ts"
 export default {
diff --git a/website/docs/zh/guide/basic/configure-rspack.mdx b/website/docs/zh/guide/basic/configure-rspack.mdx
index e79aaa9378..bf622ab80e 100644
--- a/website/docs/zh/guide/basic/configure-rspack.mdx
+++ b/website/docs/zh/guide/basic/configure-rspack.mdx
@@ -45,7 +45,7 @@ export default {
 
 > 请查看 [tools.rspack 文档](/config/tools/rspack) 来了解完整用法。
 
-## 使用 Rspack Chain
+## 使用 Rspack chain
 
 import RspackChain from '@zh/shared/rspackChain.mdx';
 
diff --git a/website/docs/zh/guide/basic/server.mdx b/website/docs/zh/guide/basic/server.mdx
index 3a4745dbd8..10aa38c7e4 100644
--- a/website/docs/zh/guide/basic/server.mdx
+++ b/website/docs/zh/guide/basic/server.mdx
@@ -110,7 +110,7 @@ export default {
 };
 ```
 
-## Rspack Dev Server
+## Rspack dev server
 
 Rspack CLI 内置的开发服务器是 [@rspack/dev-server](https://www.npmjs.com/package/@rspack/dev-server)，Rsbuild 没有使用 `@rspack/dev-server`，而是自行实现了一个更轻量的版本。
 
diff --git a/website/docs/zh/guide/basic/static-deploy.mdx b/website/docs/zh/guide/basic/static-deploy.mdx
index 08bfe4ad6d..a27a4acf09 100644
--- a/website/docs/zh/guide/basic/static-deploy.mdx
+++ b/website/docs/zh/guide/basic/static-deploy.mdx
@@ -112,7 +112,7 @@ on:
   # 在推送到默认分支时触发
   push:
     branches: ['main']
-  # 允许你从 Actions Tabs 手动运行这个工作流
+  # 允许你从 Actions tabs 手动运行这个工作流
   workflow_dispatch:
 
 # 设置 GITHUB_TOKEN 的权限以允许部署到 GitHub Pages
diff --git a/website/docs/zh/guide/debug/build-profiling.mdx b/website/docs/zh/guide/debug/build-profiling.mdx
index a06eab589c..0527ee215d 100644
--- a/website/docs/zh/guide/debug/build-profiling.mdx
+++ b/website/docs/zh/guide/debug/build-profiling.mdx
@@ -35,7 +35,7 @@ npm install -g speedscope
 speedscope CPU.date.000000.00000.0.001.cpuprofile
 ```
 
-## Rspack Profiling
+## Rspack profiling
 
 Rsbuild 支持使用 `RSPACK_PROFILE` 环境变量来对 Rspack 进行构建性能分析。
 
diff --git a/website/docs/zh/guide/faq/hmr.mdx b/website/docs/zh/guide/faq/hmr.mdx
index 8ffd7b40bb..a41dfe9643 100644
--- a/website/docs/zh/guide/faq/hmr.mdx
+++ b/website/docs/zh/guide/faq/hmr.mdx
@@ -8,22 +8,22 @@
 
 :::tip 热更新原理
 
-1. 浏览器和开发服务器建立一个 Web Socket 连接，用于实时通信。
-2. 当开发服务器每次重新编译完成后，会通过 Web Socket 通知浏览器，浏览器向开发服务器发送 `hot-update.(js|json)` 请求，从而加载编译后的新模块。
+1. 浏览器和开发服务器建立一个 WebSocket 连接，用于实时通信。
+2. 当开发服务器每次重新编译完成后，会通过 WebSocket 通知浏览器，浏览器向开发服务器发送 `hot-update.(js|json)` 请求，从而加载编译后的新模块。
 3. 当浏览器收到新的模块后，如果是 React 项目，则会通过 React 官方的 React Refresh 来更新 React 组件，其他框架也是类似。
 
 :::
 
 了解完热更新的原理后，你可以按照以下步骤来进行基本的排查：
 
-#### 1. 检查 Web Socket 连接
+#### 1. 检查 WebSocket 连接
 
 打开浏览器的控制台，查看是否有 `[HMR] connected.` 日志。
 
-- 如果有，说明 Web Socket 连接正常，请继续检查后续步骤。
-- 如果没有，请打开 Chrome 的 Network 面板，查看 `ws://[host]:[port]/rsbuild-hmr` 的请求状态，若请求异常，说明热更新失败的原因是 Web Socket 请求没有建立成功。
+- 如果有，说明 WebSocket 连接正常，请继续检查后续步骤。
+- 如果没有，请打开 Chrome 的 Network 面板，查看 `ws://[host]:[port]/rsbuild-hmr` 的请求状态，若请求异常，说明热更新失败的原因是 WebSocket 请求没有建立成功。
 
-Web Socket 请求没有建立成功的原因可能有很多种，例如开启了网络代理，导致 Web Socket 请求没有正确发送到开发服务器。你可以检查 Web Socket 请求的地址是否为你的开发服务器地址，如果不是，则可以通过 [dev.client](/config/dev/client) 来配置 Web Socket 请求的地址。
+WebSocket 请求没有建立成功的原因可能有很多种，例如开启了网络代理，导致 WebSocket 请求没有正确发送到开发服务器。你可以检查 WebSocket 请求的地址是否为你的开发服务器地址，如果不是，则可以通过 [dev.client](/config/dev/client) 来配置 WebSocket 请求的地址。
 
 #### 2. 检查 hot-update 请求
 
diff --git a/website/docs/zh/guide/migration/vite.mdx b/website/docs/zh/guide/migration/vite.mdx
index c28d2dcaa7..edb628f3e2 100644
--- a/website/docs/zh/guide/migration/vite.mdx
+++ b/website/docs/zh/guide/migration/vite.mdx
@@ -215,7 +215,7 @@ Vite 通过 `vite-env.d.ts` 文件提供了一些预设的类型定义，迁移
 + /// <reference types="@rsbuild/core/types" />
 ```
 
-## Glob Import
+## Glob import
 
 Vite 提供了 `import.meta.glob()` 来批量导入模块。
 
diff --git a/website/docs/zh/guide/migration/webpack.mdx b/website/docs/zh/guide/migration/webpack.mdx
index 1498c7b99e..43c3951d15 100644
--- a/website/docs/zh/guide/migration/webpack.mdx
+++ b/website/docs/zh/guide/migration/webpack.mdx
@@ -150,7 +150,7 @@ export default {
 | [eslint-webpack-plugin](https://www.npmjs.com/package/eslint-webpack-plugin)                   | [ESLint 插件](https://github.com/rspack-contrib/rsbuild-plugin-eslint)                                      |
 | [babel-plugin-styled-components](https://www.npmjs.com/package/babel-plugin-styled-components) | [Styled Components 插件](https://github.com/rspack-contrib/rsbuild-plugin-styled-components)                |
 
-### 配置 Dev Server
+### 配置 Dev server
 
 Rsbuild 不支持使用 Rspack 的 [devServer](https://rspack.dev/config/dev-server) 配置项，请参考 [Rspack Dev Server](/guide/basic/server#rspack-dev-server) 进行替换。
 
diff --git a/website/docs/zh/guide/optimization/build-performance.mdx b/website/docs/zh/guide/optimization/build-performance.mdx
index f2058e7915..085e9b238d 100644
--- a/website/docs/zh/guide/optimization/build-performance.mdx
+++ b/website/docs/zh/guide/optimization/build-performance.mdx
@@ -28,7 +28,7 @@ Rsbuild 默认对构建性能进行了充分优化，但是随着使用场景变
 
 以下是针对开发构建进行提速的方法。
 
-### 开启 Lazy Compilation
+### 开启 Lazy compilation
 
 启用 lazy compilation 可以显著减少开发启动时编译的模块数量，从而提升启动时间。
 
@@ -42,7 +42,7 @@ export default {
 
 > 请参考 [dev.lazyCompilation](/config/dev/lazy-compilation) 了解更多。
 
-### Source Map 格式
+### Source map 格式
 
 为了提供良好的调试体验，Rsbuild 在开发模式下默认使用 `cheap-module-source-map` 格式 source map，这是一种高质量的 source map 格式，会带来一定的性能开销。
 
diff --git a/website/docs/zh/guide/optimization/code-splitting.mdx b/website/docs/zh/guide/optimization/code-splitting.mdx
index 62290ae0c3..12a96392d4 100644
--- a/website/docs/zh/guide/optimization/code-splitting.mdx
+++ b/website/docs/zh/guide/optimization/code-splitting.mdx
@@ -230,7 +230,7 @@ export default {
 
 其中，`override` 配置会与 Rspack 的 `splitChunks` 配置进行合并，具体配置项请参考 [Rspack - splitChunks](https://rspack.dev/zh/config/optimization#optimization-splitchunks)。
 
-## 使用 Dynamic Import 拆包
+## 使用 Dynamic import 拆包
 
 除了 `chunkSplit` 配置，使用 [dynamic import](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import) 拆包也是一项重要的优化手段，它可以有效减少首屏的包体积。
 
diff --git a/website/docs/zh/plugins/dev/core.mdx b/website/docs/zh/plugins/dev/core.mdx
index d99e1b0ce0..d0b9543398 100644
--- a/website/docs/zh/plugins/dev/core.mdx
+++ b/website/docs/zh/plugins/dev/core.mdx
@@ -1,4 +1,4 @@
-# Plugin Core
+# Plugin core
 
 本章节描述了 Rsbuild 插件核心的类型定义和 API。
 
diff --git a/website/docs/zh/plugins/dev/hooks.mdx b/website/docs/zh/plugins/dev/hooks.mdx
index 4f3daaab72..f1f7a6bb19 100644
--- a/website/docs/zh/plugins/dev/hooks.mdx
+++ b/website/docs/zh/plugins/dev/hooks.mdx
@@ -1,10 +1,10 @@
-# Plugin Hooks
+# Plugin hooks
 
 本章节介绍 Rsbuild 插件可用的 plugin hooks。
 
 ## 总览
 
-### Common Hooks
+### Common hooks
 
 - [modifyRsbuildConfig](#modifyrsbuildconfig)：修改传递给 Rsbuild 的配置。
 - [modifyEnvironmentConfig](#modifyenvironmentconfig): 修改特定 environment 的 Rsbuild 配置。
@@ -17,7 +17,7 @@
 - [onAfterEnvironmentCompile](#onafterenvironmentcompile): 在每次单个 environment 的构建结束后调用。
 - [onExit](#onexit)：在进程即将退出时调用。
 
-### Dev Hooks
+### Dev hooks
 
 仅在执行 `rsbuild dev` 命令或 `rsbuild.startDevServer()` 方法时调用。
 
@@ -29,7 +29,7 @@
 
 - [onCloseDevServer](#onclosedevserver)：在关闭开发服务器时调用。
 
-### Build Hooks
+### Build hooks
 
 仅在执行 `rsbuild build` 命令或 `rsbuild.build()` 方法时调用。
 
@@ -40,7 +40,7 @@
 
 - [onCloseBuild](#onclosebuild)：在关闭构建时调用。
 
-### Preview Hooks
+### Preview hooks
 
 仅在执行 `rsbuild preview` 命令或 `rsbuild.preview()` 方法时调用。
 
@@ -49,7 +49,7 @@
 
 ## Hooks 顺序
 
-### Dev Hooks
+### Dev hooks
 
 执行 `rsbuild dev` 命令或 `rsbuild.startDevServer()` 方法时，Rsbuild 会依次执行以下 hooks：
 
@@ -75,7 +75,7 @@
 - [onAfterEnvironmentCompile](#onafterenvironmentcompile)
 - [onDevCompileDone](#ondevcompiledone)
 
-### Build Hooks
+### Build hooks
 
 执行 `rsbuild build` 命令或 `rsbuild.build()` 方法时，Rsbuild 会依次执行以下 hooks：
 
@@ -101,7 +101,7 @@
 - [onAfterEnvironmentCompile](#onafterenvironmentcompile)
 - [onAfterBuild](#onafterbuild)
 
-### Preview Hooks
+### Preview hooks
 
 执行 `rsbuild preview` 命令或 `rsbuild.preview()` 方法时，Rsbuild 会依次执行以下 hooks：
 
@@ -111,16 +111,16 @@
 - [onAfterStartProdServer](#onafterstartprodserver)
 - [onExit](#onexit)
 
-## Global Hooks vs Environment Hooks
+## Global hooks vs environment hooks
 
 在 Rsbuild 中，有一些插件 hooks 是全局 hooks，这些 hook 的执行往往和 Rsbuild 自身的启动流程或全局逻辑相关，在所有 environment 下共享。如：
 
 - `modifyRsbuildConfig` 用来修改 Rsbuild 的基础配置，基础配置最终会和 environment 配置合并；
-- `onBeforeStartDevServer`、`onAfterStartDevServer` 和 Rsbuild dev server 启动流程相关，所有 environments 共享 Rsbuild 的 dev server、middlewares、Web Socket。
+- `onBeforeStartDevServer`、`onAfterStartDevServer` 和 Rsbuild dev server 启动流程相关，所有 environments 共享 Rsbuild 的 dev server、middlewares、WebSocket。
 
 与之对应的，有一些插件 hooks 是和当前 environment 相关的 hook，这些 hook 执行时会带有特定的 environment 上下文，并根据 environment 的不同而触发多次。
 
-### Global Hooks
+### Global hooks
 
 - [modifyRsbuildConfig](#modifyrsbuildconfig)
 - [onBeforeStartDevServer](#onbeforestartdevserver)
@@ -136,7 +136,7 @@
 - [onAfterStartProdServer](#onafterstartprodserver)
 - [onExit](#onexit)
 
-### Environment Hooks
+### Environment hooks
 
 - [modifyEnvironmentConfig](#modifyenvironmentconfig)
 - [modifyBundlerChain](#modifybundlerchain)
@@ -201,7 +201,7 @@ const plugin2 = () => ({
 rsbuild.addPlugins([plugin1, plugin2]);
 ```
 
-## Common Hooks
+## Common hooks
 
 ### modifyRsbuildConfig
 
@@ -584,7 +584,7 @@ const myPlugin = () => ({
 });
 ```
 
-## Build Hooks
+## Build hooks
 
 ### onBeforeBuild
 
@@ -640,7 +640,7 @@ const myPlugin = () => ({
 });
 ```
 
-## Dev Hooks
+## Dev hooks
 
 ### onBeforeStartDevServer
 
@@ -737,7 +737,7 @@ rsbuild.onCloseDevServer(async () => {
 });
 ```
 
-## Preview Hooks
+## Preview hooks
 
 ### onBeforeStartProdServer
 
@@ -776,7 +776,7 @@ const myPlugin = () => ({
 });
 ```
 
-## Other Hooks
+## Other hooks
 
 ### onExit
 
diff --git a/website/docs/zh/plugins/list/plugin-assets-retry.mdx b/website/docs/zh/plugins/list/plugin-assets-retry.mdx
index 36d7df9990..91311e21d3 100644
--- a/website/docs/zh/plugins/list/plugin-assets-retry.mdx
+++ b/website/docs/zh/plugins/list/plugin-assets-retry.mdx
@@ -1,4 +1,4 @@
-# Assets Retry 插件
+# Assets retry 插件
 
 import { SourceCode } from 'rspress/theme';