docs: unify title capitalization style (#671)

Author: chenjiahan

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

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Rslib Contributing Guide
+# Rslib contributing guide
 
 Thanks for that you are interested in contributing to Rslib. Before starting your contribution, please take a moment to read the following guidelines.
 
@@ -14,7 +14,7 @@ fnm use
 nvm use
 ```
 
-## Install Dependencies
+## Install dependencies
 
 Enable [pnpm](https://pnpm.io/) with corepack:
 
@@ -34,19 +34,19 @@ 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/).
 
-## 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:
 
 ```sh
 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:
 
@@ -68,13 +68,13 @@ npx nx build @rslib/core --watch
 
 ## 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:
 

README.md

@@ -39,7 +39,7 @@ Rslib has the following features:
 - **Declaration file generation**: Including isolated declarations.
 - **Advanced features**: Module Federation, asset compression, PostCSS, Lightning CSS, and more.
 
-## 📚 Getting Started
+## 📚 Getting started
 
 To get started with Rslib, see the [Quick Start](https://lib.rsbuild.dev/guide/start/quick-start).
 
@@ -109,7 +109,7 @@ Please read the [Contributing Guide](https://github.com/web-infra-dev/rslib/blob
   </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.
 

examples/module-federation/mf-remote/README.md

@@ -7,7 +7,7 @@ A Module Federation remote module built with Rsbuild. It is consumed by [mf-reac
 
 Extra remote module is **optional**, it is used to demonstrate a complex Module Federation set up here.
 
-## Get Started
+## Get started
 
 Start the dev server:
 

packages/create-rslib/template-common/README.md

@@ -1,4 +1,4 @@
-# Rslib Project
+# Rslib project
 
 ## Setup
 
@@ -8,7 +8,7 @@ Install the dependencies:
 pnpm install
 ```
 
-## Get Started
+## Get started
 
 Build the library:
 

website/README.md

@@ -1,12 +1,16 @@
-# Rslib Website
+# Rslib 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.
 
 ## Contributing
 
 Currently Rslib 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.
 

website/docs/en/api/javascript-api/core.mdx

@@ -1 +1 @@
-# Rslib Core
+# Rslib core

website/docs/en/api/javascript-api/types.mdx

@@ -1 +1 @@
-# Rslib Types
+# Rslib types

website/docs/en/config/lib/auto-extension.mdx

@@ -5,7 +5,7 @@
 
 Whether to automatically set the file extension based on the [`format`](/config/lib/format) option in the JavaScript output files.
 
-## Default Extension
+## Default extension
 
 By default that when `autoExtension` is set to `true`, the file extension will be:
 
@@ -15,7 +15,7 @@ By default that when `autoExtension` is set to `true`, the file extension will b
 
 When `autoExtension` is set to `false`, the file extension will be default to `.js`.
 
-## Customize Extension
+## Customize extension
 
 You can set `autoExtension` to `false` and use [output.filename](https://rsbuild.dev/config/output/filename) to customize the JavaScript output files.
 

website/docs/en/config/lib/auto-external.mdx

@@ -29,7 +29,7 @@ type AutoExternal =
 
 Whether to automatically externalize dependencies of different dependency types and do not bundle them.
 
-## Object Type
+## Object type
 
 ### autoExternal.dependencies
 
@@ -59,7 +59,7 @@ Whether to automatically externalize dependencies of type `peerDependencies`.
 
 Whether to automatically externalize dependencies of type `devDependencies`.
 
-## Default Value
+## Default value
 
 The default value of `autoExternal` is `true`, which means the following dependency types will **not be bundled**:
 
@@ -91,7 +91,7 @@ export default {
 
 ## Example
 
-### Customize Externalized Dependency Types
+### Customize externalized dependency types
 
 To disable the processing of a specific type of dependency, you can configure `autoExternal` as an object like this:
 
@@ -109,7 +109,7 @@ export default {
 };
 ```
 
-### Disable Default Behavior
+### Disable default behavior
 
 If you want to disable the default behavior, you can set `autoExternal` to `false`: