sync pid-limiting multi-tenancy job

asa3311 · asa3311 · commit 10a8a4abdf02 · 2023-11-20T19:15:38.000+08:00
diff --git a/content/zh-cn/docs/concepts/policy/pid-limiting.md b/content/zh-cn/docs/concepts/policy/pid-limiting.md
@@ -181,7 +181,7 @@ Eviction signal value is calculated periodically and does NOT enforce the limit.
 PID limiting - per Pod and per Node sets the hard limit.
 Once the limit is hit, workload will start experiencing failures when trying to get a new PID.
 It may or may not lead to rescheduling of a Pod,
-depending on how workload reacts on these failures and how liveleness and readiness
+depending on how workload reacts on these failures and how liveness and readiness
 probes are configured for the Pod. However, if limits were set correctly,
 you can guarantee that other Pods workload and system processes will not run out of PIDs
 when one Pod is misbehaving.
diff --git a/content/zh-cn/docs/concepts/security/multi-tenancy.md b/content/zh-cn/docs/concepts/security/multi-tenancy.md
@@ -918,7 +918,7 @@ The two options are discussed in more detail in the following sections.
 <!--
 As previously mentioned, you should consider isolating each workload in its own namespace, even if
 you are using dedicated clusters or virtualized control planes. This ensures that each workload
-only has access to its own resources, such as Config Maps and Secrets, and allows you to tailor
+only has access to its own resources, such as ConfigMaps and Secrets, and allows you to tailor
 dedicated security policies for each workload. In addition, it is a best practice to give each
 namespace names that are unique across your entire fleet (that is, even if they are in separate
 clusters), as this gives you the flexibility to switch between dedicated and shared clusters in
diff --git a/content/zh-cn/docs/concepts/workloads/controllers/job.md b/content/zh-cn/docs/concepts/workloads/controllers/job.md
@@ -1613,7 +1613,7 @@ the Job status, allowing the Pod to be removed by other controllers or users.
 
 {{< note >}}
 <!--
-See [My pod stays terminating](/docs/tasks/debug-application/debug-pods) if you
+See [My pod stays terminating](/docs/tasks/debug/debug-application/debug-pods/) if you
 observe that pods from a Job are stucked with the tracking finalizer.
 -->
 &#22914;&#26524;&#20320;&#21457;&#29616;&#26469;&#33258; Job &#30340;&#26576;&#20123; Pod &#22240;&#23384;&#22312;&#36127;&#36131;&#36319;&#36394;&#30340; Finalizer &#32780;&#26080;&#27861;&#27491;&#24120;&#32456;&#27490;&#65292;
