[zh-cn] Adjust some lines to make changes compare line by line more e…

…fficiently

 in the future

content/zh-cn/docs/tasks/administer-cluster/kubeadm/kubeadm-reconfigure.md

@@ -1,14 +1,14 @@
 ---
 title: 重新配置 kubeadm 集群
 content_type: task
-weight: 10
+weight: 30
 ---
 <!--
 reviewers:
 - sig-cluster-lifecycle
 title: Reconfiguring a kubeadm cluster
 content_type: task
-weight: 10
+weight: 30
 -->
 
 <!-- overview -->
@@ -107,7 +107,6 @@ in a ConfigMap called `kubeadm-config` in the `kube-system` namespace.
 
 To change a particular option in the `ClusterConfiguration` you can edit the ConfigMap with this command:
 
-The configuration is located under the `data.ClusterConfiguration` key.
 -->
 ### 应用集群配置更改
 
@@ -123,6 +122,9 @@ The configuration is located under the `data.ClusterConfiguration` key.
 kubectl edit cm -n kube-system kubeadm-config
 ```
 
+<!--
+The configuration is located under the `data.ClusterConfiguration` key.
+-->
 配置位于 `data.ClusterConfiguration` 键下。
 
 {{< note >}}
@@ -170,7 +172,6 @@ Before proceeding with these changes, make sure you have backed up the directory
 <!--
 To write new certificates you can use:
 
-To write new manifest files in `/etc/kubernetes/manifests` you can use:
 -->
 
 要编写新证书，你可以使用：
@@ -179,6 +180,9 @@ To write new manifest files in `/etc/kubernetes/manifests` you can use:
 kubeadm init phase certs <component-name> --config <config-file>
 ```
 
+<!--
+To write new manifest files in `/etc/kubernetes/manifests` you can use:
+-->
 要在 `/etc/kubernetes/manifests` 中编写新的清单文件，你可以使用：
 
 ```shell
@@ -212,7 +216,6 @@ in a ConfigMap called `kubelet-config` in the `kube-system` namespace.
 
 You can edit the ConfigMap with this command:
 
-The configuration is located under the `data.kubelet` key.
 -->
 ### 应用 kubelet 配置更改
 
@@ -227,6 +230,9 @@ The configuration is located under the `data.kubelet` key.
 kubectl edit cm -n kube-system kubelet-config
 ```
 
+<!--
+The configuration is located under the `data.kubelet` key.
+-->
 配置位于 `data.kubelet` 键下。
 
 <!--
@@ -284,7 +290,6 @@ This ConfigMap is used by the `kube-proxy` DaemonSet in the `kube-system` namesp
 
 To change a particular option in the `KubeProxyConfiguration`, you can edit the ConfigMap with this command:
 
-The configuration is located under the `data.config.conf` key.
 -->
 ### 应用 kube-proxy 配置更改
 
@@ -302,6 +307,9 @@ The configuration is located under the `data.config.conf` key.
 kubectl edit cm -n kube-system kube-proxy
 ```
 
+<!--
+The configuration is located under the `data.config.conf` key.
+-->
 配置位于 `data.config.conf` 键下。
 
 <!--
@@ -311,9 +319,6 @@ Once the `kube-proxy` ConfigMap is updated, you can restart all kube-proxy Pods:
 
 Obtain the Pod names:
 
-Delete a Pod with:
-
-New Pods that use the updated ConfigMap will be created.
 -->
 #### 反映 kube-proxy 的更改
 
@@ -325,12 +330,18 @@ New Pods that use the updated ConfigMap will be created.
 kubectl get po -n kube-system | grep kube-proxy
 ```
 
+<!--
+Delete a Pod with:
+-->
 使用以下命令删除 Pod：
 
 ```shell
 kubectl delete po -n kube-system <pod-name>
 ```
 
+<!--
+New Pods that use the updated ConfigMap will be created.
+-->
 将创建使用更新的 ConfigMap 的新 Pod。
 
 {{< note >}}
@@ -373,7 +384,6 @@ Once the CoreDNS changes are applied you can delete the CoreDNS Pods:
 
 Obtain the Pod names:
 
-Delete a Pod with:
 -->
 #### 反映 CoreDNS 的更改
 
@@ -385,6 +395,9 @@ Delete a Pod with:
 kubectl get po -n kube-system | grep coredns
 ```
 
+<!--
+Delete a Pod with:
+-->
 使用以下命令删除 Pod：
 
 ```shell
@@ -400,6 +413,7 @@ New Pods with the updated CoreDNS configuration will be created.
 <!--
 kubeadm does not allow CoreDNS configuration during cluster creation and upgrade.
 This means that if you execute `kubeadm upgrade apply`, your changes to the CoreDNS
+objects will be lost and must be reapplied.
 -->
 kubeadm 不允许在集群创建和升级期间配置 CoreDNS。
 这意味着如果执行了 `kubeadm upgrade apply`，你对