Merge pull request #35726 from hs0210/sync-commented-en-txt

[zh-cn] resync: some file's commented English texts and indentation

Author: k8s-ci-robot

content/zh-cn/docs/concepts/scheduling-eviction/node-pressure-eviction.md

@@ -411,7 +411,7 @@ kubelet 按以下顺序释放磁盘空间：
 If the kubelet's attempts to reclaim node-level resources don't bring the eviction
 signal below the threshold, the kubelet begins to evict end-user pods. 
 
-The kubelet uses the following parameters to determine pod eviction order:
+The kubelet uses the following parameters to determine the pod eviction order:
 
 1. Whether the pod's resource usage exceeds requests
 1. [Pod Priority](/docs/concepts/scheduling-eviction/pod-priority-preemption/)
@@ -598,7 +598,7 @@ kubelet 根据 Pod 的服务质量（QoS）为每个容器设置一个 `oom_scor
 {{<note>}}
 <!-- 
 The kubelet also sets an `oom_score_adj` value of `-997` for containers in Pods that have
-`system-node-critical` {{<glossary_tooltip text="Priority" term_id="pod-priority">}}
+`system-node-critical` {{<glossary_tooltip text="Priority" term_id="pod-priority">}}.
 -->
 kubelet 还将具有 `system-node-critical`
 {{<glossary_tooltip text="优先级" term_id="pod-priority">}}
@@ -762,7 +762,7 @@ kubelet 将 `active_file` 内存区域视为不可回收。
 kubelet 很容易将其视为资源用量过量并为节点设置内存压力污点，从而触发 Pod 驱逐。
 
 <!-- 
-For more more details, see [https://github.com/kubernetes/kubernetes/issues/43916](https://github.com/kubernetes/kubernetes/issues/43916)
+For more details, see [https://github.com/kubernetes/kubernetes/issues/43916](https://github.com/kubernetes/kubernetes/issues/43916)
 
 You can work around that behavior by setting the memory limit and memory request
 the same for containers likely to perform intensive I/O activity. You will need 

content/zh-cn/docs/concepts/workloads/controllers/job.md

@@ -365,7 +365,7 @@ Jobs with _fixed completion count_ - that is, jobs that have non null
     When you use an Indexed Job in combination with a
     {{< glossary_tooltip term_id="Service" >}}, Pods within the Job can use
     the deterministic hostnames to address each other via DNS.
-  - From the containarized task, in the environment variable `JOB_COMPLETION_INDEX`.
+  - From the containerized task, in the environment variable `JOB_COMPLETION_INDEX`.
 
   The Job is considered complete when there is one successfully completed Pod
   for each index. For more information about how to use this mode, see

content/zh-cn/docs/reference/access-authn-authz/psp-to-pod-security-standards.md

@@ -17,7 +17,7 @@ weight: 95
 
 <!--
 The tables below enumerate the configuration parameters on
-[PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/) objects, whether the field mutates
+[PodSecurityPolicy](/docs/concepts/security/pod-security-policy/) objects, whether the field mutates
 and/or validates pods, and how the configuration values map to the
 [Pod Security Standards](/docs/concepts/security/pod-security-standards/).
 -->
@@ -289,9 +289,9 @@ table can be specified under `.metadata.annotations` on the PodSecurityPolicy ob
 `.metadata.annotations` 设置到 PodSecurityPolicy 对象之上。
 
 <table class="no-word-break">
-    <caption style="display:none"><!-- Mapping PodSecurityPolicy annotations to Pod Security Standards-->将 PodSecurityPolicy 注解映射到 Pod 安全性标准</caption>
-    <tbody>
-        <tr>
+  <caption style="display:none"><!-- Mapping PodSecurityPolicy annotations to Pod Security Standards-->将 PodSecurityPolicy 注解映射到 Pod 安全性标准</caption>
+  <tbody>
+    <tr>
       <th><code><!--PSP Annotation-->PSP 注解</code></th>
       <th><!-- Type -->类型</th>
       <th><!-- Pod Security Standards Equivalent-->Pod 安全性标准中对应设置</th>

content/zh-cn/docs/tutorials/security/ns-level-pss.md

@@ -25,7 +25,7 @@ one namespace at a time.
 
 You can also apply Pod Security Standards to multiple namespaces at once at the cluster
 level. For instructions, refer to 
-[Apply Pod Security Standards at the cluster level](/docs/tutorials/security/cluster-level-pss).
+[Apply Pod Security Standards at the cluster level](/docs/tutorials/security/cluster-level-pss/).
 -->
 Pod 安全准入（PSA）在 v1.23 及更高版本默认启用，
 因为它[升级到测试版（beta）](/blog/2021/12/09/pod-security-admission-beta/)。
@@ -34,7 +34,7 @@ Pod 安全准入是在创建 Pod 时应用
 在本教程中，你将应用 `baseline` Pod 安全标准，每次一个名字空间。
 
 你还可以在集群级别一次将 Pod 安全标准应用于多个名称空间。
-有关说明，请参阅[在集群级别应用 Pod 安全标准](/zh-cn/docs/tutorials/security/cluster-level-pss)。
+有关说明，请参阅[在集群级别应用 Pod 安全标准](/zh-cn/docs/tutorials/security/cluster-level-pss/)。
 
 ## {{% heading "prerequisites" %}}