From ad50091bb983e3617f5667381e39c9927a91a483 Mon Sep 17 00:00:00 2001
From: zhuzhenghao <zhenghao.zhu@daocloud.io>
Date: Wed, 8 Feb 2023 10:34:12 +0800
Subject: [PATCH] [zh] Cleanup  page disruption

---
 .../concepts/workloads/pods/disruptions.md    | 31 ++++++++++---------
 1 file changed, 16 insertions(+), 15 deletions(-)

diff --git a/content/zh-cn/docs/concepts/workloads/pods/disruptions.md b/content/zh-cn/docs/concepts/workloads/pods/disruptions.md
index 5480288961..9290801a52 100644
--- a/content/zh-cn/docs/concepts/workloads/pods/disruptions.md
+++ b/content/zh-cn/docs/concepts/workloads/pods/disruptions.md
@@ -212,7 +212,8 @@ For example, the `kubectl drain` subcommand lets you mark a node as going out of
 service. When you run `kubectl drain`, the tool tries to evict all of the Pods on
 the Node you're taking out of service. The eviction request that `kubectl` submits on
 your behalf may be temporarily rejected, so the tool periodically retries all failed
-requests until all Pods on the target node are terminated, or until a configurable timeout is reached.
+requests until all Pods on the target node are terminated, or until a configurable timeout
+is reached.
 -->
 例如，`kubectl drain` 命令可以用来标记某个节点即将停止服务。
 运行 `kubectl drain` 命令时，工具会尝试驱逐你所停服的节点上的所有 Pod。
@@ -426,7 +427,7 @@ can happen, according to:
 - 控制器的类型
 - 集群的资源能力
 
-<!-- 
+<!--
 ## Pod disruption conditions {#pod-disruption-conditions}
 -->
 ## Pod 干扰状况 {#pod-disruption-conditions}
@@ -451,7 +452,7 @@ enabled in your cluster.
 [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)。
 {{< /note >}}
 
-<!-- 
+<!--
 When enabled, a dedicated Pod `DisruptionTarget` [condition](/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions) is added to indicate
 that the Pod is about to be deleted due to a {{<glossary_tooltip term_id="disruption" text="disruption">}}.
 The `reason` field of the condition additionally
@@ -462,18 +463,18 @@ indicates one of the following reasons for the Pod termination:
 用来表明该 Pod 因为发生{{<glossary_tooltip term_id="disruption" text="干扰">}}而被删除。
 状况中的 `reason` 字段进一步给出 Pod 终止的原因，如下：
 
-<!-- 
+<!--
 `PreemptionByKubeScheduler`
-: Pod is due to be {{<glossary_tooltip term_id="preemption" text="preempted">}} by a scheduler in order to accommodate a new Pod with a higher priority. For more information, see [Pod priority preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/). 
+: Pod is due to be {{<glossary_tooltip term_id="preemption" text="preempted">}} by a scheduler in order to accommodate a new Pod with a higher priority. For more information, see [Pod priority preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/).
 -->
 `PreemptionByKubeScheduler`
 : Pod 将被调度器{{<glossary_tooltip term_id="preemption" text="抢占">}}，
 目的是接受优先级更高的新 Pod。
 要了解更多的相关信息，请参阅 [Pod 优先级和抢占](/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption/)。
 
-<!-- 
+<!--
 `DeletionByTaintManager`
-: Pod is due to be deleted by Taint Manager (which is part of the node lifecycle controller within `kube-controller-manager`) due to a `NoExecute` taint that the Pod does not tolerate; see {{<glossary_tooltip term_id="taint" text="taint">}}-based evictions. 
+: Pod is due to be deleted by Taint Manager (which is part of the node lifecycle controller within `kube-controller-manager`) due to a `NoExecute` taint that the Pod does not tolerate; see {{<glossary_tooltip term_id="taint" text="taint">}}-based evictions.
 -->
 `DeletionByTaintManager`
 : 由于 Pod 不能容忍 `NoExecute` 污点，Pod 将被
@@ -482,14 +483,14 @@ Taint Manager（`kube-controller-manager` 中节点生命周期控制器的一
 
 <!--
 `EvictionByEvictionAPI`
-: Pod has been marked for {{<glossary_tooltip term_id="api-eviction" text="eviction using the Kubernetes API">}} . 
+: Pod has been marked for {{<glossary_tooltip term_id="api-eviction" text="eviction using the Kubernetes API">}}.
 -->
 `EvictionByEvictionAPI`
 : Pod 已被标记为{{<glossary_tooltip term_id="api-eviction" text="通过 Kubernetes API 驱逐">}}。
 
-<!-- 
+<!--
 `DeletionByPodGC`
-: Pod, that is bound to a no longer existing Node, is due to be deleted by [Pod garbage collection](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection). 
+: Pod, that is bound to a no longer existing Node, is due to be deleted by [Pod garbage collection](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection).
 -->
 `DeletionByPodGC`
 : 绑定到一个不再存在的 Node 上的 Pod 将被
@@ -501,8 +502,8 @@ Taint Manager（`kube-controller-manager` 中节点生命周期控制器的一
 -->
 `TerminationByKubelet`
 : Pod
-  由于{{<glossary_tooltip term_id="node-pressure-eviction" text="节点压力驱逐">}}或[节点体面关闭](/zh-cn/docs/concepts/architecture/nodes/#graceful-node-shutdown)而被
-  kubelet 终止。
+由于{{<glossary_tooltip term_id="node-pressure-eviction" text="节点压力驱逐">}}或[节点体面关闭](/zh-cn/docs/concepts/architecture/nodes/#graceful-node-shutdown)而被
+kubelet 终止。
 
 {{< note >}}
 <!-- 
@@ -510,7 +511,7 @@ A Pod disruption might be interrupted. The control plane might re-attempt to
 continue the disruption of the same Pod, but it is not guaranteed. As a result,
 the `DisruptionTarget` condition might be added to a Pod, but that Pod might then not actually be
 deleted. In such a situation, after some time, the
-Pod disruption condition will be cleared. 
+Pod disruption condition will be cleared.
 -->
 Pod 的干扰可能会被中断。控制平面可能会重新尝试继续干扰同一个 Pod，但这没办法保证。
 因此，`DisruptionTarget` 条件可能会添被加到 Pod 上，
@@ -527,9 +528,9 @@ phase (see also [Pod garbage collection](/docs/concepts/workloads/pods/pod-lifec
 则 Pod 垃圾回收器 (PodGC) 也会将这些 Pod 标记为失效
 （另见 [Pod 垃圾回收](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection)）。
 
-<!-- 
+<!--
 When using a Job (or CronJob), you may want to use these Pod disruption conditions as part of your Job's
-[Pod failure policy](/docs/concepts/workloads/controllers/job#pod-failure-policy). 
+[Pod failure policy](/docs/concepts/workloads/controllers/job#pod-failure-policy).
 -->
 使用 Job（或 CronJob）时，你可能希望将这些 Pod 干扰状况作为 Job
 [Pod 失效策略](/zh-cn/docs/concepts/workloads/controllers/job#pod-failure-policy)的一部分。