[zh-cn] sync disruptions init-containers pod-qos

Signed-off-by: xin.li <xin.li@daocloud.io>

content/zh-cn/docs/concepts/workloads/pods/disruptions.md

@@ -1,7 +1,7 @@
 ---
 title: 干扰（Disruptions）
 content_type: concept
-weight: 60
+weight: 70
 ---
 
 <!--
@@ -11,7 +11,7 @@ reviewers:
 - davidopp
 title: Disruptions
 content_type: concept
-weight: 60
+weight: 70
 -->
 
 <!-- overview -->

content/zh-cn/docs/concepts/workloads/pods/init-containers.md

@@ -575,13 +575,18 @@ for resource usage apply:
 <!--
 Quota and limits are applied based on the effective Pod request and
 limit.
-
-Pod level control groups (cgroups) are based on the effective Pod request and
-limit, the same as the scheduler.
 -->
 配额和限制适用于有效 Pod 的请求和限制值。
 
-Pod 级别的控制组（Cgroup）是基于 Pod 的有效 request 和 limit，与调度器相同。
+<!--
+### Init containers and Linux cgroups {#cgroups}
+
+On Linux, resource allocations for Pod level control groups (cgroups) are based on the effective Pod
+request and limit, the same as the scheduler.
+-->
+### Init 容器和 Linux cgroup    {#cgroups}
+
+在 Linux 上，Pod 级别的 CGroup 资源分配基于 Pod 的有效请求和限制值，与调度程序相同。
 
 <!--
 ### Pod restart reasons

content/zh-cn/docs/concepts/workloads/pods/pod-qos.md

@@ -164,7 +164,7 @@ CPU request 时，Pod 才是 `BestEffort`。Pod 中的容器可以请求（除 C
 -->
 ## 使用 cgroup v2 的内存 QoS   {#memory-qos-with-cgroup-v2}
 
-{{< feature-state feature-gate-name="MemoryQoS" >}}
+{{< feature-state feature_gate_name="MemoryQoS" >}}
 
 <!--
 Memory QoS uses the memory controller of cgroup v2 to guarantee memory resources in Kubernetes.