diff --git a/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubelet-start.md b/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubelet-start.md
index 2067c9711e..8ccdb59ea8 100644
--- a/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubelet-start.md
+++ b/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubelet-start.md
@@ -1,15 +1,3 @@
-<!--
-The file is auto-generated from the Go source code of the component using a generic
-[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
-to generate the reference documentation, please read
-[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
-To update the reference conent, please follow the 
-[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
-guide. You can file document formatting bugs against the
-[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
--->
-
-
 <!--
 Write kubelet settings and (re)start the kubelet
 -->
@@ -34,22 +22,22 @@ kubeadm init phase kubelet-start [flags]
 <!--
 ### Examples
 -->
-
 ### 示例
 
 <!--
-# Writes a dynamic environment file with kubelet flags from a InitConfiguration file.
--->
-
 ```
-# 从 InitConfiguration 文件中写入带有 kubelet 参数的动态环境文件。
+  # Writes a dynamic environment file with kubelet flags from a InitConfiguration file.
+  kubeadm init phase kubelet-start --config config.yaml
+```
+-->
+```
+# 将来自 InitConfiguration 文件中的 kubelet 参数写入一个动态环境文件。
 kubeadm init phase kubelet-start --config config.yaml
 ```
 
 <!--
 ### Options
 -->
-
 ### 选项
 
    <table style="width: 100%; table-layout: fixed;">
@@ -79,7 +67,8 @@ kubeadm 配置文件的路径。
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
+Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if 
+you have more than one CRI installed or if you have non-standard CRI socket.
 -->
 <p>
 连接到 CRI 套接字的路径。如果为空，则 kubeadm 将尝试自动检测该值；仅当安装了多个 CRI 或具有非标准 CRI 套接字时，才使用此选项。
@@ -115,6 +104,23 @@ Specify the node name.
 </td>
 </tr>
 
+<tr>
+<td colspan="2">--patches string</td>
+</tr>
+<tr>
+<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>
+<!--
+Path to a directory that contains files named &quot;target[suffix][+patchtype].extension&quot;. For example, &quot;kube-apiserver0+merge.yaml&quot; or just &quot;etcd.json&quot;. &quot;target&quot; can be one of &quot;kube-apiserver&quot;, &quot;kube-controller-manager&quot;, &quot;kube-scheduler&quot;, &quot;etcd&quot;, &quot;kubeletconfiguration&quot;. &quot;patchtype&quot; can be one of &quot;strategic&quot;, &quot;merge&quot; or &quot;json&quot; and they match the patch formats supported by kubectl. The default &quot;patchtype&quot; is &quot;strategic&quot;. &quot;extension&quot; must be either &quot;json&quot; or &quot;yaml&quot;. &quot;suffix&quot; is an optional string that can be used to determine which patches are applied first alpha-numerically.
+-->
+目录路径，指向包含名为 “target[suffix][+patchtype].extension” 的文件的目录。
+例如，"kube-apiserver0+merge.yaml" 或 "etcd.json" 这种简单形式。
+"target" 可以是 “kube-apiserver”、“kube-controller-manager”、“kube-scheduler”、“etcd”、“kubeletconfiguration” 之一，
+"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
+默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
+"suffix" 是一个可选字符串，可用于确定按字母顺序首先应用哪些补丁。
+</p></td>
+</tr>
+
 </tbody>
 </table>