diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/agit-support.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/agit-support.md
index ebf2a882..31d6bb81 100644
--- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/agit-support.md
+++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/agit-support.md
@@ -35,7 +35,8 @@ git push origin HEAD:refs/for/main
   - `title`：PR 的标题
   - `topic`：PR 应该打开的分支名称
   - `description`：PR 的描述
-  - `force-push`：确认强制更新目标分支
+  - `force-push=true`: 是否强制更新目标分支
+    - 注意: 如果不传值，只用 `-o force-push` 也同样可以正常工作。
 
 下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `main`：
 
diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/agit-support.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/agit-support.md
index b07cdca1..7e9928bf 100644
--- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/agit-support.md
+++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/agit-support.md
@@ -31,7 +31,8 @@ git push origin HEAD:refs/for/master
   - `title`：PR 的标题
   - `topic`：PR 应该打开的分支名称
   - `description`：PR 的描述
-  - `force-push`：确认强制更新目标分支
+  - `force-push=true`: 是否强制更新目标分支
+    - 注意: 如果不传值，只用 `-o force-push` 是无法正常工作的。
 
 下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `master`：
 
diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/agit-support.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/agit-support.md
index 8d677b26..f496a0ec 100644
--- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/agit-support.md
+++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/agit-support.md
@@ -34,7 +34,8 @@ git push origin HEAD:refs/for/master
   - `title`：PR 的标题
   - `topic`：PR 应该打开的分支名称
   - `description`：PR 的描述
-  - `force-push`：确认强制更新目标分支
+  - `force-push=true`: 是否强制更新目标分支
+    - 注意: 如果不传值，只用 `-o force-push` 是无法正常工作的。
 
 下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `master`：
 
diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/agit-support.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/agit-support.md
index edf26c70..15ad451a 100644
--- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/agit-support.md
+++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/agit-support.md
@@ -34,7 +34,8 @@ git push origin HEAD:refs/for/main
   - `title`：PR 的标题
   - `topic`：PR 应该打开的分支名称
   - `description`：PR 的描述
-  - `force-push`：确认强制更新目标分支
+  - `force-push=true`: 是否强制更新目标分支
+    - 注意: 如果不传值，只用 `-o force-push` 是无法正常工作的。
 
 下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `main`：
 
diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/agit-support.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/agit-support.md
index edf26c70..15ad451a 100644
--- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/agit-support.md
+++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/agit-support.md
@@ -34,7 +34,8 @@ git push origin HEAD:refs/for/main
   - `title`：PR 的标题
   - `topic`：PR 应该打开的分支名称
   - `description`：PR 的描述
-  - `force-push`：确认强制更新目标分支
+  - `force-push=true`: 是否强制更新目标分支
+    - 注意: 如果不传值，只用 `-o force-push` 是无法正常工作的。
 
 下面是另一个高级示例，用于创建一个以 `topic`、`title` 和 `description` 为参数的新 PR，目标分支是 `main`：
 
diff --git a/versioned_docs/version-1.19/usage/agit.md b/versioned_docs/version-1.19/usage/agit.md
index 8502a9be..6e9e5bf3 100644
--- a/versioned_docs/version-1.19/usage/agit.md
+++ b/versioned_docs/version-1.19/usage/agit.md
@@ -33,7 +33,8 @@ The command has the following structure:
   - `title`: The PR title
   - `topic`: The branch name the PR should be opened for
   - `description`: The PR description
-  - `force-push`: confirm force update the target branch
+  - `force-push=true`: Specifies whether to force-update the target branch.
+    - Note: omitting the value and using just `-o force-push` will not work.
 
 Here's another advanced example for creating a new PR targeting `master` with `topic`, `title`, and `description`:
 
diff --git a/versioned_docs/version-1.20/usage/agit.md b/versioned_docs/version-1.20/usage/agit.md
index 1b14a8e7..c55ac094 100644
--- a/versioned_docs/version-1.20/usage/agit.md
+++ b/versioned_docs/version-1.20/usage/agit.md
@@ -35,7 +35,8 @@ The command has the following structure:
   - `title`: The PR title
   - `topic`: The branch name the PR should be opened for
   - `description`: The PR description
-  - `force-push`: confirm force update the target branch
+  - `force-push=true`: Specifies whether to force-update the target branch.
+    - Note: omitting the value and using just `-o force-push` will not work.
 
 Here's another advanced example for creating a new PR targeting `master` with `topic`, `title`, and `description`:
 
diff --git a/versioned_docs/version-1.21/usage/agit.md b/versioned_docs/version-1.21/usage/agit.md
index 2407e5b0..a33f2976 100644
--- a/versioned_docs/version-1.21/usage/agit.md
+++ b/versioned_docs/version-1.21/usage/agit.md
@@ -35,7 +35,8 @@ The command has the following structure:
   - `title`: The PR title
   - `topic`: The branch name the PR should be opened for
   - `description`: The PR description
-  - `force-push`: confirm force update the target branch
+  - `force-push=true`: Specifies whether to force-update the target branch.
+    - Note: omitting the value and using just `-o force-push` will not work.
 
 Here's another advanced example for creating a new PR targeting `main` with `topic`, `title`, and `description`:
 
diff --git a/versioned_docs/version-1.22/usage/agit.md b/versioned_docs/version-1.22/usage/agit.md
index 230583d0..64a846fb 100644
--- a/versioned_docs/version-1.22/usage/agit.md
+++ b/versioned_docs/version-1.22/usage/agit.md
@@ -37,7 +37,8 @@ The command has the following structure:
   - `topic`: The topic of this change. It will become the name of the branch holding the changes waiting for review.  This is REQUIRED to trigger a pull request.
   - `title`: The PR title (optional but recommended), only used for topics not already having an associated PR.
   - `description`: The PR description (optional but recommended), only used for topics not already having an associated PR.
-  - `force-push`: confirm force update the target branch
+  - `force-push=true`: Specifies whether to force-update the target branch.
+    - Note: omitting the value and using just `-o force-push` will not work.
 
 Here's another advanced example for creating a new PR targeting `main` with `topic`, `title`, and `description`: