Merge pull request #41418 from asa3311/sync-controller-manager-leader-migration-reserve-compute-resources-cpu-default-namespace

[zh-cn] sync cpu-default-namespace reserve-compute-resources controller-manager-leader-migration

Author: k8s-ci-robot

content/zh-cn/docs/tasks/administer-cluster/controller-manager-leader-migration.md

@@ -274,7 +274,7 @@ The migrated controllers, as specified in the configuration, are running under e
 version N or `cloud-controller-manager` of version N + 1 depending on which controller manager holds the migration lease.
 No controller will ever be running under both controller managers at any time.
 
-In a rolling manner, create a new control plane node of version N + 1 and bring down one of version N + 1 until the control plane contains only nodes of version N + 1.
+In a rolling manner, create a new control plane node of version N + 1 and bring down one of version N until the control plane contains only nodes of version N + 1.
 If a rollback from version N + 1 to N is required, add nodes of version N with Leader Migration enabled for `kube-controller-manager` back to the control plane, replacing one of version N + 1 each time until there are only nodes of version N.
 -->
 ### 升级控制平面

content/zh-cn/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace.md

@@ -168,10 +168,10 @@ kubectl apply -f https://k8s.io/examples/admin/resource/cpu-defaults-pod-2.yaml
 ```
 
 <!--
-View the [specification](/docs/concepts/overview/working-with-objects/kubernetes-objects/#object-spec-and-status)
+View the [specification](/docs/concepts/overview/working-with-objects/#object-spec-and-status)
 of the Pod that you created:
 -->
-查看你所创建的 Pod 的[规约](/zh-cn/docs/concepts/overview/working-with-objects/kubernetes-objects/#object-spec-and-status)：
+查看你所创建的 Pod 的[规约](/zh-cn/docs/concepts/overview/working-with-objects/#object-spec-and-status)：
 
 ```
 kubectl get pod default-cpu-demo-2 --output=yaml --namespace=default-cpu-example
@@ -213,10 +213,9 @@ kubectl apply -f https://k8s.io/examples/admin/resource/cpu-defaults-pod-3.yaml
 ```
 
 <!--
-View the [specification](/docs/concepts/overview/working-with-objects/kubernetes-objects/#object-spec-and-status)
-of the Pod that you created:
+View the specification of the Pod that you created:
 -->
-查看你所创建的 Pod 的[规约](/zh-cn/docs/concepts/overview/working-with-objects/kubernetes-objects/#object-spec-and-status)：
+查看你所创建的 Pod 的规约：
 
 ```
 kubectl get pod default-cpu-demo-3 --output=yaml --namespace=default-cpu-example

content/zh-cn/docs/tasks/administer-cluster/reserve-compute-resources.md

@@ -437,7 +437,7 @@ Under this scenario, 'Allocatable' will be 14.5 CPUs, 28.5Gi of memory and
 Scheduler ensures that the total memory `requests` across all pods on this node does
 not exceed 28.5Gi and storage doesn't exceed 88Gi.
 Kubelet evicts pods whenever the overall memory usage across pods exceeds 28.5Gi,
-or if overall disk usage exceeds 88Gi If all processes on the node consume as
+or if overall disk usage exceeds 88Gi. If all processes on the node consume as
 much CPU as they can, pods together cannot consume more than 14.5 CPUs.
 -->
 在这个场景下，'Allocatable' 将会是 14.5 CPUs、28.5Gi 内存以及 `88Gi` 本地存储。