[zh-cn] sync task files of task-9

Signed-off-by: Guangwen Feng <fenggw-fnst@fujitsu.com>

Author: fenggw-fnst

content/zh-cn/docs/tasks/administer-cluster/manage-resources/_index.md

@@ -1,9 +1,9 @@
 ---
 title: 管理内存、CPU 和 API 资源
-weight: 20
+weight: 40
 ---
 
 <!--
 title: Manage Memory, CPU, and API Resources
-weight: 20
+weight: 40
 -->

content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd.md

@@ -1,12 +1,12 @@
 ---
 title: 将节点上的容器运行时从 Docker Engine 改为 containerd
-weight: 8
+weight: 10
 content_type: task 
 ---
 
 <!--
 title: "Changing the Container Runtime on a Node from Docker Engine to containerd"
-weight: 8
+weight: 10
 content_type: task 
 -->
 

content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-removal-affects-you.md

@@ -14,7 +14,7 @@ weight: 50
 <!-- overview -->
 
 <!-- 
-The `dockershim` component of Kubernetes allows to use Docker as a Kubernetes's
+The `dockershim` component of Kubernetes allows the use of Docker as a Kubernetes's
 {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}.
 Kubernetes' built-in `dockershim` component was removed in release v1.24.
 -->
@@ -80,11 +80,11 @@ dependency on Docker:
 1. Third-party tools that perform above mentioned privileged operations. See
  [Migrating telemetry and security agents from dockershim](/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents)
  for more information.
-1. Make sure there is no indirect dependencies on dockershim behavior.
+1. Make sure there are no indirect dependencies on dockershim behavior.
  This is an edge case and unlikely to affect your application. Some tooling may be configured
  to react to Docker-specific behaviors, for example, raise alert on specific metrics or search for
  a specific log message as part of troubleshooting instructions.
- If you have such tooling configured, test the behavior on test
+ If you have such tooling configured, test the behavior on a test
  cluster before migration.
 -->
 4. 检查执行上述特权操作的第三方工具。
@@ -151,7 +151,7 @@ before to check on these containers is no longer available.
 <!-- 
 You cannot get container information using `docker ps` or `docker inspect`
 commands. As you cannot list containers, you cannot get logs, stop containers,
-or execute something inside container using `docker exec`.
+or execute something inside a container using `docker exec`.
 -->
 你不能再使用 `docker ps` 或 `docker inspect` 命令来获取容器信息。
 由于你不能列出容器，因此你不能获取日志、停止容器，甚至不能通过 `docker exec` 在容器中执行命令。

content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd.md

@@ -1,12 +1,12 @@
 ---
 title: 将 Docker Engine 节点从 dockershim 迁移到 cri-dockerd
-weight: 9
+weight: 20
 content_type: task 
 ---
 
 <!--
 title: "Migrate Docker Engine nodes from dockershim to cri-dockerd"
-weight: 9
+weight: 20
 content_type: task 
 -->
 

content/zh-cn/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md

@@ -1,15 +1,15 @@
 ---
 title: 排查 CNI 插件相关的错误
 content_type: task
-weight: 10
+weight: 40
 ---
 <!--
 title: Troubleshooting CNI plugin-related errors
 content_type: task
 reviewers:
 - mikebrow
 - divya-mohan0209
-weight: 10
+weight: 40
 -->
 
 <!-- overview -->
@@ -33,6 +33,7 @@ Kubernetes.
 Service issues exist for pod CNI network setup and tear down in containerd
 v1.6.0-v1.6.3 when the CNI plugins have not been upgraded and/or the CNI config
 version is not declared in the CNI config files. The containerd team reports, "these issues are resolved in containerd v1.6.4."
+
 With containerd v1.6.0-v1.6.3, if you do not upgrade the CNI plugins and/or
 declare the CNI config version, you might encounter the following "Incompatible
 CNI versions" or "Failed to destroy network for sandbox" error conditions.
@@ -169,6 +170,7 @@ and kubelet. Uncordon the node (`kubectl uncordon <nodename>`).
 <!--
 The following example shows a configuration for `containerd` runtime v1.6.x,
 which supports a recent version of the CNI specification (v1.0.0).
+
 Please see the documentation from your plugin and networking provider for
 further instructions on configuring your system.
 -->