diff --git a/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_bootstrap-token.md b/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_bootstrap-token.md
index 2ea181aac10..5c77af37354 100644
--- a/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_bootstrap-token.md
+++ b/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_bootstrap-token.md
@@ -1,3 +1,18 @@
+<!--
+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.
+-->
+
+<!-- 
+Generates bootstrap tokens used to join a node to a cluster 
+-->
+生成用于将节点加入集群的引导令牌
 
 <!--
 ### Synopsis
@@ -55,9 +70,9 @@ kubeadm init phase bootstrap-token
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-Path to a kubeadm configuration file.
+<p>Path to a kubeadm configuration file.</p>
 -->
-kubeadm 配置文件的路径。
+<p>kubeadm 配置文件的路径。</p>
 </td>
 </tr>
 
@@ -67,9 +82,9 @@ kubeadm 配置文件的路径。
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-help for bootstrap-token
+<p>help for bootstrap-token</p>
 -->
-bootstrap-token 操作的帮助命令
+<p>bootstrap-token 操作的帮助命令</p>
 </td>
 </tr>
 
@@ -84,9 +99,9 @@ bootstrap-token 操作的帮助命令
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.
+<p>The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.</p>
 -->
-用于和集群通信的 kubeconfig 文件。如果它没有被设置，那么 kubeadm 将会搜索一个已经存在于标准路径的 kubeconfig 文件。
+<p>用于和集群通信的 kubeconfig 文件。如果它没有被设置，那么 kubeadm 将会搜索一个已经存在于标准路径的 kubeconfig 文件。</p>
 </td>
 </tr>
 
@@ -96,9 +111,9 @@ The kubeconfig file to use when talking to the cluster. If the flag is not set,
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-Skip printing of the default bootstrap token generated by 'kubeadm init'.
+<p>Skip printing of the default bootstrap token generated by 'kubeadm init'.</p>
 -->
-跳过打印 'kubeadm init' 生成的默认引导令牌。
+<p>跳过打印 'kubeadm init' 生成的默认引导令牌。</p>
 </td>
 </tr>
 
@@ -124,9 +139,9 @@ Skip printing of the default bootstrap token generated by 'kubeadm init'.
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-[EXPERIMENTAL] The path to the 'real' host root filesystem.
+<p>[EXPERIMENTAL] The path to the 'real' host root filesystem.</p>
 -->
-[实验] 到 '真实' 主机根文件系统的路径。
+<p>[实验] 到 '真实' 主机根文件系统的路径。</p>
 </td>
 </tr>
 
diff --git a/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-peer.md b/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-peer.md
index 9933975b92d..4a4ec4fd19b 100644
--- a/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-peer.md
+++ b/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-peer.md
@@ -1,3 +1,18 @@
+<!--
+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.
+-->
+
+<!-- 
+Generate the certificate for etcd nodes to communicate with each other 
+-->
+生成 etcd 节点相互通信的证书
 
 <!-- 
 ### Synopsis
@@ -6,10 +21,10 @@
 ### 概要
 
 <!--
-Generate the certificate for etcd nodes to communicate with each other, and save them into etcd/peer.cert and etcd/peer.key files.
+Generate the certificate for etcd nodes to communicate with each other, and save them into etcd/peer.crt and etcd/peer.key files.
 -->
 
-生成 etcd 节点相互通信的证书，并将其保存到 etcd/peer.cert 和 etcd/peer.key 文件中。
+生成 etcd 节点相互通信的证书，并将其保存到 etcd/peer.crt 和 etcd/peer.key 文件中。
 
 <!--
 Default SANs are localhost, 127.0.0.1, 127.0.0.1, ::1
@@ -56,8 +71,10 @@ kubeadm init phase certs etcd-peer [flags]
 </tr>
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
-<!-- The path where to save and store the certificates.  -->
-保存和存储证书的路径。
+<!-- 
+<p>The path where to save and store the certificates.</p>  
+-->
+<p>保存和存储证书的路径。</p>
 </td>
 </tr>
 
@@ -66,8 +83,10 @@ kubeadm init phase certs etcd-peer [flags]
 </tr>
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
-<!-- Path to kubeadm configuration file.  -->
-kubeadm 配置文件的路径。
+<!-- 
+<p>Path to kubeadm configuration file.</p>
+-->
+<p>kubeadm 配置文件的路径。</p>
 </td>
 </tr>
 
@@ -76,8 +95,10 @@ kubeadm 配置文件的路径。
 </tr>
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
-<!-- help for etcd-peer -->
-etcd-peer 操作的帮助命令
+<!-- 
+<p>help for etcd-peer</p> 
+-->
+<p>etcd-peer 操作的帮助命令</p>
 </td>
 </tr>
 
@@ -91,8 +112,10 @@ etcd-peer 操作的帮助命令
 </tr>
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
-<!-- Choose a specific Kubernetes version for the control plane.  -->
-为控制平面指定特定的 Kubernetes 版本。
+<!-- 
+<p>Choose a specific Kubernetes version for the control plane.</p>  
+-->
+<p>为控制平面指定特定的 Kubernetes 版本。</p>
 </td>
 </tr>
 
@@ -118,9 +141,9 @@ etcd-peer 操作的帮助命令
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-[EXPERIMENTAL] The path to the 'real' host root filesystem.
+<p>[EXPERIMENTAL] The path to the 'real' host root filesystem.</p>
 -->
-[实验] 到 '真实' 主机根文件系统的路径。
+<p>[实验] 到 '真实' 主机根文件系统的路径。</p>
 </td>
 </tr>
 
diff --git a/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_generate.md b/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_generate.md
index c91bb69ae86..da02baf36f4 100644
--- a/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_generate.md
+++ b/content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_generate.md
@@ -1,3 +1,18 @@
+<!--
+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.
+-->
+
+<!-- 
+Generate and print a bootstrap token, but do not create it on the server 
+-->
+生成并打印一个引导令牌，但不要在服务器上创建它
 
 <!--
 ### Synopsis
@@ -44,9 +59,9 @@ kubeadm token generate [flags]
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-help for generate
+<p>help for generate</p>
 -->
-generate 操作的帮助命令
+<p>generate 操作的帮助命令</p>
 </td>
 </tr>
 
@@ -71,8 +86,11 @@ generate 操作的帮助命令
 </tr>
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
-<!-- Whether to enable dry-run mode or not -->
-是否启用 `dry-run` 运行模式</td>
+<!-- 
+<p>Whether to enable dry-run mode or not</p> 
+-->
+<p>是否启用 `dry-run` 运行模式</p>
+</td>
 </tr>
 
 <tr>
@@ -86,9 +104,9 @@ generate 操作的帮助命令
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
 <!--
-The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.
+<p>The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.</p>
 -->
-用于和集群通信的 KubeConfig 文件。如果它没有被设置，那么 kubeadm 将会搜索一个已经存在于标准路径的 KubeConfig 文件。
+<p>用于和集群通信的 KubeConfig 文件。如果它没有被设置，那么 kubeadm 将会搜索一个已经存在于标准路径的 KubeConfig 文件。</p>
 </td>
 </tr>
 
@@ -97,8 +115,10 @@ The kubeconfig file to use when talking to the cluster. If the flag is not set,
 </tr>
 <tr>
 <td></td><td style="line-height: 130%; word-wrap: break-word;">
-<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem.  -->
-[实验] 指向 '真实' 宿主机根文件系统的路径。
+<!-- 
+<p>[EXPERIMENTAL] The path to the 'real' host root filesystem.</p>  
+-->
+<p>[实验] 指向 '真实' 宿主机根文件系统的路径。</p>
 </td>
 </tr>