sync container-runtimes security-context reconfigure-default-service-ip-ranges

Author: asa3311

content/zh-cn/docs/setup/production-environment/container-runtimes.md

@@ -363,11 +363,17 @@ On Windows the default CRI endpoint is `npipe://./pipe/containerd-containerd`.
 <!--
 #### Configuring the `systemd` cgroup driver {#containerd-systemd}
 
-To use the `systemd` cgroup driver in `/etc/containerd/config.toml` with `runc`, set
+To use the `systemd` cgroup driver in `/etc/containerd/config.toml` with `runc`,
+set the following config based on your Containerd version
+
+Containerd versions 1.x:
 -->
 #### 配置 `systemd` cgroup 驱动 {#containerd-systemd}
 
-结合 `runc` 使用 `systemd` cgroup 驱动，在 `/etc/containerd/config.toml` 中设置：
+要在 `/etc/containerd/config.toml` 中将 `runc` 配置为使用 `systemd` cgroup 驱动，
+请根据你使用的 Containerd 版本设置以下配置：
+
+Containerd 1.x 版本：
 
 ```
 [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
@@ -376,6 +382,19 @@ To use the `systemd` cgroup driver in `/etc/containerd/config.toml` with `runc`,
  SystemdCgroup = true
 ```
 
+<!--
+Containerd versions 2.x:
+-->
+Containerd versions 2.x 版本：
+
+```
+[plugins.'io.containerd.cri.v1.runtime'.containerd.runtimes.runc]
+ ...
+ [plugins.'io.containerd.cri.v1.runtime'.containerd.runtimes.runc.options]
+ SystemdCgroup = true
+```
+
+
 <!--
 The `systemd` cgroup driver is recommended if you use [cgroup v2](/docs/concepts/architecture/cgroups).
 -->

content/zh-cn/docs/tasks/configure-pod-container/security-context.md

@@ -633,12 +633,12 @@ securityContext:
 This field has no effect on ephemeral volume types such as
 [`secret`](/docs/concepts/storage/volumes/#secret),
 [`configMap`](/docs/concepts/storage/volumes/#configmap),
-and [`emptydir`](/docs/concepts/storage/volumes/#emptydir).
+and [`emptyDir`](/docs/concepts/storage/volumes/#emptydir).
 -->
 {{< note >}}
 此字段对于 [`secret`](/zh-cn/docs/concepts/storage/volumes/#secret)、
 [`configMap`](/zh-cn/docs/concepts/storage/volumes/#configmap)
-和 [`emptydir`](/zh-cn/docs/concepts/storage/volumes/#emptydir)
+和 [`emptyDir`](/zh-cn/docs/concepts/storage/volumes/#emptydir)
 这类临时性存储无效。
 {{< /note >}}
 

content/zh-cn/docs/tasks/network/reconfigure-default-service-ip-ranges.md

@@ -113,7 +113,7 @@ We can categorize Service CIDR reconfiguration into the following scenarios:
  replacing the default ServiceCIDR is a complex operation. If the new
  ServiceCIDR does not overlap with the existing one, [it will require
  renumbering all existing Services and changing the `kubernetes.default`
- service](#Illustrative Reconfiguration Steps). The case where the primary IP
+ service](#illustrative-reconfiguration-steps). The case where the primary IP
  family also changes is even more complicated, and may require to change
  multiple cluster components (kubelet, network plugins, etc.) to match the new
  primary IP family.