@modern-js/main-doc 0.0.0-next-1686037191101 → 0.0.0-next-1686045734613

package/docs/en/guides/topic-detail/changesets/commit.mdx

@@ -4,7 +4,7 @@ sidebar_position: 7
 
 # Customizing Commit Messages
 
-Changesets supports configuring `commit` to automatically submit the current changes when executing the `change` and `bump` commands.
+Changesets supports configuring `commit` to automatically submit the current changes when running the `change` and `bump` commands.
 
 The default `commit` information is provided by `@changesets/cli/commit`, and the default information format is:
 
@@ -17,8 +17,8 @@ When the default commit information cannot meet the requirements, custom commit
 
 Commit information is divided into two types:
 
-- Commit information automatically generated when executing the `change` command.
-- Commit information automatically generated when executing the `bump` command.
+- Commit information automatically generated when running the `change` command.
+- Commit information automatically generated when running the `bump` command.
 
 The custom logic mainly implements two functions, `getAddMessage` and `getVersionMessage`, which are used to define the above two types of information, respectively.
 
@@ -101,18 +101,18 @@ type ComprehensiveRelease = {
 };
 
 type PreState = {
-  mode: 'pre' | 'exit'; // pre 模式当前状态
-  tag: string; // pre 的类型
+  mode: 'pre' | 'exit'; // Current state of pre mode
+  tag: string; // Type of pre
   initialVersions: {
-    [pkgName: string]: string; // 版本升级前包名及版本号信息，Map 格式
+    [pkgName: string]: string; // Package name and version information before version upgrade
   };
-  changesets: string[]; // 本次升级的 changeset id 列表
+  changesets: string[]; // List of changeset ids for this upgrade
 };
 
 type ReleasePlan = {
-  changesets: Changeset[]; // 本次升级的 changeset 列表
-  releases: ComprehensiveRelease[]; // 当前升级的包信息，包含包名称、当前版本、升级后版本、升级类型等
-  preState: PreState | undefined; // 当前如果为 pre 发布，提供相关状态信息
+  changesets: Changeset[]; // List of changesets for this upgrade
+  releases: ComprehensiveRelease[]; // Information of the current upgrade, including package name, current version, upgraded version, and upgrade type
+  preState: PreState | undefined; // If it is a pre-release, provide relevant state information
 };
 ```
 
@@ -128,7 +128,7 @@ Commit message content.
 
 #### Default Implementation
 
-The default processing logic of `@changesets/cli/commit` is to first display the number of packages that need to be released, then display the names and new version numbers of the released packages, and [skip ci] information is added according to the `skipCI` parameter configuration passed in.
+The default processing logic of `@changesets/cli/commit` is to first display the number of packages that need to be released, then display the names and new version of the released packages, and [skip ci] information is added according to the `skipCI` parameter configuration passed in.
 
 ```ts
 const getVersionMessage = async (
@@ -157,7 +157,7 @@ const getVersionMessage = async (
 
 ## Configuration
 
-The `commit` field in the changesets configuration file is used to mark whether to submit commit information when executing the `change` and `bump` commands, and the way to obtain commit information.
+The `commit` field in the changesets configuration file is used to mark whether to submit commit information when running the `change` and `bump` commands, and the way to obtain commit information.
 
 This configuration can be a `boolean`. When it is `true`, the default `@changesets/cli/commit` formatting commit information will be used.
 
@@ -191,15 +191,15 @@ Configure `commit` as `./my-commit-config.js`:
 }
 ```
 
-### Using Module Project
+### Using NPM Module
 
-Customizing commit can also be managed using the module project to provide a common solution.
+Customizing commit can also be managed using the NPM module project to provide a common solution.
 
-#### Use `npx @modern-js/create@latest` to create a module project.
+#### Use `npx @modern-js/create@latest` to create a module project
 
 ```md
 ? Please select the type of project you want to create: Npm Module
-? Please fill in the project name: custom-changelog
+? Please fill in the project name: custom-commit
 ? Please select the programming language: TS
 ? Please select the package manager: pnpm
 ```
@@ -212,11 +212,11 @@ export async function getAddMessage() {}
 export async function getVersionMessage() {}
 ```
 
-#### Publish the module to NPM.
+#### Publish the module to NPM
 
-#### Install the corresponding module in the root directory of the target repository, such as `custom-commit`.
+#### Install the corresponding module in the root directory of the target repository, such as `custom-commit`
 
-#### Configure the commit configuration of changesets as the package name.
+#### Configure the commit configuration of changesets as the package name
 
 ```json title="package.json"
 {
@@ -227,9 +227,9 @@ export async function getVersionMessage() {}
 
 ### Using Monorepo Sub-Project
 
-If your current repository is Monorepo, you can directly manage it using module sub-projects.
+If your current repository is Monorepo, you can directly manage it using NPM module sub-projects.
 
-#### Run `pnpm run new` to create a module sub-project.
+#### Run `pnpm run new` to create a module sub-project
 
 ```bash
 ? Please select the type of project you want to create: Npm Module
@@ -246,7 +246,7 @@ export async function getAddMessage() {}
 export async function getVersionMessage() {}
 ```
 
-Add the sub-project module dependency, such as `custom-commit`, to the Monorepo root directory.
+#### Add the sub-project module dependency, such as `custom-commit`, to the Monorepo root directory
 
 ```json title="package.json"
 {
@@ -257,7 +257,7 @@ Add the sub-project module dependency, such as `custom-commit`, to the Monorepo
 }
 ```
 
-Configure the commit configuration of Changesets as the package name.
+#### Configure the commit configuration of Changesets as the package name
 
 ```json title=".changesets/config.json"
 {

package/docs/en/guides/topic-detail/changesets/config.mdx

@@ -4,9 +4,9 @@ sidebar_position: 5
 
 # Changesets Configuration
 
-As we learned earlier, when initializing a Modern.js repository, the configuration file for changesets will be initialized by default, that is, the `.changeset/config.json` file. Below, we will learn in detail what configurations are supported in this file.
+When initializing a Modern.js repository, the configuration file for changesets will be initialized by default, that is, the `.changeset/config.json` file. Below, we will learn in detail what configurations are supported in this file.
 
-## Configuration introduction
+## Introduction
 
 ### commit
 
@@ -14,14 +14,14 @@ Type: `boolean`
 
 Default: `false`
 
-When this field is configured as `true`, the code submission operation will be automatically executed when executing the `change` and `bump` commands.
+When this field is configured as `true`, the code submission operation will be automatically executed when running the `change` and `bump` commands.
 
 The default commit information format is as follows:
 
 ![change commit](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/changeset-change-commit-info.png)
 ![bump commit](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/changeset-bump-commit-info.png)
 
-This commit information supports customization, which we will discuss in detail in the [Customizing Commit Information](/guides/topic-detail/changesets/commit) chapter.
+This commit information supports customization, which we will discuss in detail in the [Customizing Commit Messages](/guides/topic-detail/changesets/commit) chapter.
 
 ### access
 
@@ -58,7 +58,7 @@ Type: `string[]`
 
 Default: `[]`
 
-Used to declare packages to be ignored when executing the `bump` command. The usage is consistent with the `--ignore` parameter of the `bump` command. Note that the two cannot be used at the same time.
+Used to declare packages to be ignored when running the `bump` command. The usage is consistent with the `--ignore` parameter of the `bump` command. Note that the two cannot be used at the same time.
 
 ### fixed
 
@@ -66,7 +66,7 @@ Type: `string[][]`
 
 Default: `[]`
 
-Used to group packages in monorepos. The version numbers of packages in the same group will be bound, and each time the `bump` command is executed, if a package in the same group is upgraded, others will be upgraded together.
+Used to group packages in monorepos. The version of packages in the same group will be bound, and each time the `bump` command is run, a package in the same group is upgraded, others will be upgraded together.
 Regular expressions can be used to match package names.
 
 ### linked
@@ -75,7 +75,7 @@ Type: `string[][]`
 
 Default: `[]`
 
-Similar to `fixed`, it also groups packages in monorepos, but only the packages related to the changeset declaration will be upgraded when the `bump` command is executed, and the version numbers of the changeset packages in the same group will remain consistent.
+Similar to `fixed`, it also groups packages in monorepos, but only the packages related to the changeset declaration will be upgraded when the `bump` command is run, and the version of the changeset packages in the same group will remain consistent.
 Regular expressions can be used to match package names.
 
 ### updateInternalDependencies
@@ -86,7 +86,7 @@ Default: `patch`
 
 Used to declare the version number rule for updating internal dependencies.
 
-When upgrading the version number by executing the `bump` command, the dependency declaration using the package in the repository will be automatically updated by default. After configuring this field as `minor`, if the version number is upgraded to `patch`, the reference dependency declaration will not be updated automatically.
+When upgrading the version number by running the `bump` command, the dependency declaration using the package in the repository will be automatically updated by default. After configuring this field as `minor`, if the version number is upgraded to `patch`, the reference dependency declaration will not be updated automatically.
 
 For example:
 
@@ -108,7 +108,7 @@ Default: `@changesets/cli/changelog`
 
 The rule for generating changelog.
 
-When configured as `false`, only the version number will be declared in the `CHANGELOG.md` file when executing the `bump` command, and no other changelog information will be declared.
+When configured as `false`, only the version number will be declared in the `CHANGELOG.md` file when running the `bump` command, and no other changelog information will be declared.
 
 ![Close changelog configuration](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/changeset-empty-changelog.png)
 
@@ -136,7 +136,7 @@ Type: `always` | `out-of-range`
 
 Default: `always`
 
-When upgrading the version number by executing the `bump` command, the dependency declaration using the package in the repository will be automatically updated by default. When this parameter is set to `out-of-range`, the dependency declaration using the package in the repository will be updated only when it is outside the declared range.
+When upgrading the version number by running the `bump` command, the dependency declaration using the package in the repository will be automatically updated by default. When this parameter is set to `out-of-range`, the dependency declaration using the package in the repository will be updated only when it is outside the declared range.
 
 #### useCalculatedVersionForSnapshots
 

package/docs/en/guides/topic-detail/changesets/github.mdx

@@ -28,7 +28,7 @@ After the configuration is completed, the robot will automatically check whether
 
 ![](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/changeset-bot-no-changeset.png)
 
-You can execute `pnpm run change` in the repository to add changeset, or click the second link below to fill in changeset directly.
+You can run `pnpm run change` in the repository to add changeset, or click the second link below to fill in changeset directly.
 
 #### Changeset added
 
@@ -44,11 +44,11 @@ You can directly ignore the prompt information when no changeset is added, which
 
 ### Automatically create Release Pull Request
 
-Modern.js provides a Github Action to automatically create release Pull Request, which can automatically execute bump operation, update lock file and create Pull Request operation based on the selected branch.
+Modern.js provides a Github Action to automatically create release Pull Request, which can automatically run bump command, update lock file and create Pull Request operation based on the selected branch.
 
 #### Usage
 
-Create a `.github/workflows/release-pull-request.yml` file in the repository and fill in the following content:
+- Create a `.github/workflows/release-pull-request.yml` file in the repository and fill in the following content:
 
 ```yaml
 name: Release Pull Request
@@ -93,25 +93,25 @@ jobs:
           REF: ${{ github.ref }}
 ```
 
-After merging Workflow into the main branch, go to the Action page corresponding to the Github repository and select Release Pull Request:
+- After merging Workflow into the main branch, go to the Action page corresponding to the Github repository and select Release Pull Request:
 
 ![Release Pull Request Action](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/action-pull-request.png)
 
-Select the release type of this release, and click the Run workflow button:
+- Select the release type of this release, and click the Run workflow button:
 
 ![Run Release Pull Request](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/action-pull-request.jpeg)
 
-After the workflow is completed, a `Release-${version}` Pull Request will be automatically created, the related version number of `bump` changeset will be automatically updated, and the lock file will be updated. The content of Pull Request is the Release Note automatically generated by executing the `gen-release-note` command.
+- After the workflow is completed, a `Release-${version}` Pull Request will be automatically created, the related version number of `bump` changeset will be automatically updated, and the lock file will be updated. The content of Pull Request is the Release Note automatically generated by running the `gen-release-note` command.
 
 ![Release Pull Request](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/release-pull-request.jpeg)
 
 ### Automatic Release
 
-Modern.js provides a Github Action to automatically release versions, which can automatically execute release operation based on the selected branch and publish the package to NPM.
+Modern.js provides a Github Action to automatically release versions, which can automatically run release command based on the selected branch and publish the package to NPM.
 
 #### Usage
 
-Create a `.github/workflows/release.yml` file in the repository and fill in the following content:
+- Create a `.github/workflows/release.yml` file in the repository and fill in the following content:
 
 ```yaml
 name: Release
@@ -160,16 +160,16 @@ jobs:
           REF: ${{ github.ref }}
 ```
 
-Configure the NPM_TOKEN of the repository:
+- Configure the NPM_TOKEN of the repository:
 
 ![](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/github-set-npm-token.png)
 
-After merging Workflow into the main branch, go to the Action page corresponding to the Github repository and select Release:
+- After merging Workflow into the main branch, go to the Action page corresponding to the Github repository and select Release:
 
 ![Release Action](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/release-action.png)
 
-Select the branch name and release version type, and click the Run workflow button:
+- Select the branch name and release version type, and click the Run workflow button:
 
 ![Run Release Action](https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/run-release-workflow.png)
 
-Workflow will automatically complete the build and release to NPM process of the repository.
+- Workflow will automatically complete the build and release to NPM process of the repository.

package/docs/en/guides/topic-detail/changesets/introduce.mdx

@@ -2,25 +2,25 @@
 sidebar_position: 1
 ---
 
-# Introduction to Changesets
+# Introducing Changesets
 
-Modern.js integrates [changesets](https://github.com/changesets/changesets) by default for package version management in Npm Module and Monorepo project.
+Modern.js integrates [changesets](https://github.com/changesets/changesets) for package version management in Npm Module and Monorepo project.
 
 ## Features
 
 Changesets have the following features:
 
-- During development, developers need to provide the package names involved in this change, the type of version upgrade (`pathch`, `minor`, `major`), and change information, that is, changeset.
+- During development, developers need to provide the package names, the type of version upgrade (`pathch`, `minor`, `major`), and change information involved in this change.
 
 - When releasing a version, the version number of the corresponding package will be automatically upgraded based on the content of the changeset, and changelog information will be generated in the corresponding package.
 
-- In the Monorepo scenario, changesets will automatically generate a repository dependency graph, and only upgrade the version numbers of the changed packages and related dependent packages during upgrade.
+- In the Monorepo project, changesets will automatically generate a repository dependency graph, and only upgrade the version numbers of the changed packages and related dependent packages during upgrade.
 
 ## Initialization
 
-The module and Monorepo project schemes created by Modern.js have already initialized changesets. The `.changeset` directory and the configuration file `.changeset/config.json` will be automatically created in the project root directory.
+The Npm Module and Monorepo project created by Modern.js have already initialized changesets. The `.changeset` directory and the configuration file `.changeset/config.json` will be automatically created in the project root directory.
 
-In addition, Modern.js provides corresponding commands for changesets in its corresponding project scheme tools `@modern-js/module-tools` and `@modern-js/monorepo-tools`, and there is no need to manually install changeset-related dependencies.
+In addition, Modern.js provides corresponding commands for changesets in its corresponding project tools `@modern-js/module-tools` and `@modern-js/monorepo-tools`, and there is no need to manually install changeset-related dependencies.
 
 The default configuration for changesets is as follows:
 
@@ -37,20 +37,20 @@ The default configuration for changesets is as follows:
 }
 ```
 
-The configuration file provides some basic configurations for generating changesets. For detailed field descriptions, please refer to the following chapter: [changesets configuration](/guides/topic-detail/changesets/config).
+The configuration file provides some basic configurations for generating changesets. For detailed field descriptions, please refer to [Changesets configuration](/guides/topic-detail/changesets/config).
 
 ## Commands
 
-- `change` Creates a changeset. After executing this command, a changeset file will be automatically generated in the `.changeset` directory.
+- `change`: Creates a changeset. After running this command, a changeset file will be automatically generated in the `.changeset` directory.
 
-- `bump` Upgrades the version number of the corresponding package based on the current changeset.
+- `bump`: Upgrades the version of the corresponding package based on the current changeset.
 
-- `pre` Marks entering and exiting `pre release` mode. When executing the `bump` command in `pre release` mode, the version number format will be `x.x.x-${pre-tag}.x`.
+- `pre`: Marks entering and exiting `pre release` mode. When running the `bump` command in `pre release` mode, the version format will be `x.x.x-${pre-tag}.x`.
 
-- `release` Publishes the package to NPM.
+- `release`: Publishes the package to NPM.
 
-- `status` Views the current changeset status.
+- `status`: Views the current changeset status.
 
-- `gen-release-note` Generates Release Note information based on the current chagneset status.
+- `gen-release-note`: Generates Release Note information based on the current chagneset status.
 
 For specific command-supported parameters, please refer to the corresponding chapter introduction.

package/docs/en/guides/topic-detail/changesets/release-note.mdx

@@ -4,7 +4,7 @@ sidebar_position: 8
 
 # Customizing Release Note Format
 
-Modern.js provides the `modern gen-release-note` command, which supports automatically generating Release Note information through the current existing changeset and git commit information. Before executing the release command, you can execute this command to generate the Release Note for this release.
+Modern.js provides the `modern gen-release-note` command, which supports automatically generating Release Note through the current existing changeset and git commit information. Before running the release command, you can run this command to generate the Release Note for this release.
 
 The default generated Release Note format is:
 
@@ -12,25 +12,23 @@ The default generated Release Note format is:
 - fix: add missing type definitions by @zllkjc in https://github.com/web-infra-dev/modern.js/pull/3835
 ```
 
-Obtain the Pull Request ID of the changeset through the commit information, and generate a Github link, which includes the changeset's changelog information and author information.
+Get the Pull Request ID of the changeset through the commit information, and generate a Github link, which includes the changeset's changelog information and author information.
 
 :::info
-To obtain author information, you need to provide the Github Token environment variable, which is passed in through GITHUB_AUTH_TOKEN.
+To get author information, you need to provide the Github Token environment variable, which is passed in through GITHUB_AUTH_TOKEN.
 :::
 
 When the default generated Release Note logic cannot meet the requirements, custom Release Note format is supported.
 
 ## Information
 
-### Information Required for Customizing Release Note
+### getReleaseInfo
 
 To generate Release Note information, some information needs to be collected, such as commit ID, Pull Request ID, commit message, etc.
 
 This logic can be implemented through the `getReleaseInfo` function.
 
-#### getReleaseInfo
-
-##### Params
+#### Params
 
 - commit
 
@@ -42,29 +40,37 @@ The result of executing `git log --pretty=format:%h--%s--%ae .changeset/${change
 
 - commitObj
 
-Preliminary analysis of the commit to obtain basic information.
+Basic information about commit.
 
 ```ts
+export enum CommitType {
+  Performance = 'performance',
+  Features = 'features',
+  BugFix = 'bugFix',
+  Doc = 'doc',
+  Other = 'other',
+}
+
 interface Commit {
   id: string; // commit id
-  type: 'feature' | 'fix'; // commit 类型，默认通过开头字符串如果为 fix，类型为 fix，其他为 feature
-  repository?: string; // 参数传入的 repo 信息或者 package.json 中定义的 repository 信息
+  type: CommitType;
+  repository?: string; // Repo information passed in as a parameter or defined in package.json
   pullRequestId?: string;
   author?: string;
-  message: string; // commit message
-  summary: string; // changeset summary
-  summary_zh: string; // changeset zh summary
+  message: string; // Commit message
+  summary: string; // Changeset summary
+  summary_zh: string; // Changeset summary in Chinese
   [key: string]: string | undefined;
 }
 ```
 
-##### Returns
+#### Returns
 
 commitObj, the complete commit object after supplementation.
 
-##### Default Implementation
+#### Default Implementation
 
-The default implementation of Modern.js is to split out the Pull Request ID based on the commit information, and obtain the user information based on the commit ID and add it to the commitObj.
+The default implementation of Modern.js is to split out the Pull Request ID based on the commit information, and get the user information based on the commit ID and add it to the commitObj.
 
 ```ts
 function getReleaseInfo(commit: string, commitObj: Commit) {
@@ -108,19 +114,17 @@ const commitRegex = /(.*)\(#(\d*)\)/;
 }
 ```
 
-### Generating Release Note Based on Obtained Information
+### getReleaseNoteLine
 
-Generate the corresponding Release Note based on the commit object information obtained in `getReleaseInfo`.
+Generate the corresponding Release Note based on the commit object information getted in `getReleaseInfo`.
 
 This logic can be implemented through the `getReleaseNoteLine` function.
 
-#### getReleaseNoteLine
-
-##### Params
+#### Params
 
 - commit
 
-The type is the same as the above commitObj type.
+The type is the same as the above `commitObj` type.
 
 - lang
 
@@ -128,11 +132,11 @@ Type: string;
 
 Get the Release Note information of the corresponding language, supporting `en` and `zh`, the default is `en`.
 
-##### Returns
+#### Returns
 
 The generated Release Note.
 
-##### Default Implementation
+#### Default Implementation
 
 The default implementation of Modern.js is:
 
@@ -200,11 +204,11 @@ You can also define the command parameters directly in `package.json`:
 
 Run the command `pnpm run gen-release-note` directly.
 
-### Using Module Project
+### Using NPM Module
 
-Customizing release note can also be managed using the module project to provide a common solution.
+Customizing release note can also be managed using the NPM module project to provide a common solution.
 
-#### Use `npx @modern-js/create@latest` to create a module project.
+#### Use `npx @modern-js/create@latest` to create a module project
 
 ```md
 ? Please select the type of project you want to create: Npm Module
@@ -221,9 +225,9 @@ export function getReleaseInfo() {}
 export function getReleaseNoteLine() {}
 ```
 
-#### Publish the module to NPM.
-#### Install the corresponding module in the root directory of the target repository, such as `custom-release-note`.
-#### Run the `gen-release-note` command with the `custom` parameter added.
+#### Publish the module to NPM
+#### Install the corresponding module in the root directory of the target repository, such as `custom-release-note`
+#### Run the `gen-release-note` command with the `custom` parameter added
 
 ```bash
 pnpm run gen-release-note --custom custom-release-note
@@ -231,9 +235,9 @@ pnpm run gen-release-note --custom custom-release-note
 
 ### Using Monorepo Sub-Project
 
-If your current repository is Monorepo, you can directly manage it using module sub-projects.
+If your current repository is Monorepo, you can directly manage it using NPM module sub-projects.
 
-#### Run `pnpm run new` to create a module sub-project.
+#### Run `pnpm run new` to create a module sub-project
 
 ```md
 ? Please select the type of project you want to create: Npm Module
@@ -250,7 +254,7 @@ export function getReleaseInfo() {}
 export function getReleaseNoteLine() {}
 ```
 
-#### Add the sub-project module dependency, such as `custom-release-note`, to the Monorepo root directory.
+#### Add the sub-project module dependency, such as `custom-release-note`, to the Monorepo root directory
 
 ```json title="package.json"
 {
@@ -260,7 +264,7 @@ export function getReleaseNoteLine() {}
 }
 ```
 
-#### Run the `gen-release-note` command with the `custom` parameter added.
+#### Run the `gen-release-note` command with the `custom` parameter added
 
 ```bash
 pnpm run gen-release-note --custom custom-release-note

package/docs/en/guides/topic-detail/changesets/release-pre.mdx

@@ -2,17 +2,17 @@
 sidebar_position: 4
 ---
 
-# Publishing a pre-release version
+# Publishing Pre-Release Version
 
 Before doing an actual release, we also need to publish a pre-release version for internal testing and user use. Changesets also support publishing pre-release versions.
 
 ## Steps
 
 :::info
-The following example commands are all using pnpm as the package management tool. If you need to use other package management tools, please replace them as needed.
+The following example commands are all using pnpm. If you need to use other package management tools, please replace them as needed.
 :::
 
-#### Run the following command to upgrade the version number of the pre-release version:
+#### Run the bump command to upgrade the version of the pre-release
 
 ```bash
 pnpm run bump --canary --preid <preid>
@@ -24,17 +24,17 @@ After using the `--canary` parameter, the `bump` command completes the following
 
 - `changeset pre enter <preid>`: Enters pre-release mode.
 
-- `changeset version`: Upgrades the version number.
+- `changeset version`: Upgrades the version.
 
 - `changeset pre exit`: Exits pre-release mode.
 
 #### Check the changes and submit
 
-Check whether the version number changes are correct and submit the changes.
+Check whether the version changes are correct and submit the changes.
 
 It is recommended to perform pre-release operations not on the main branch and not merge them into the main branch. After the pre-release verification is completed, an actual version can be directly released based on the main branch.
 
-#### Run the following command to publish the pre-release version:
+#### Run the release command to publish the pre-release version:
 
 ```bash
 pnpm run release --tag <tag>