Merge pull request #25057 from tengqm/zh-sync-6

[zh] Sync changes from English site (6)

Author: k8s-ci-robot

content/zh/docs/concepts/workloads/controllers/_index.md

@@ -1,4 +1,4 @@
 ---
-title: "控制器"
+title: "工作负载资源"
 weight: 20
 ---

content/zh/docs/concepts/workloads/controllers/deployment.md

@@ -201,20 +201,20 @@ Follow the steps given below to create the above Deployment:
 3. 要查看 Deployment 上线状态，运行 `kubectl rollout status deployment.v1.apps/nginx-deployment`。
    输出类似于：
 
-    ```
-    Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
-    deployment "nginx-deployment" successfully rolled out
-    ```
+   ```
+   Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
+   deployment "nginx-deployment" successfully rolled out
+   ```
 
 <!--
 4. Run the `kubectl get deployments` again a few seconds later. The output is similar to this:
 -->
 4. 几秒钟后再次运行 `kubectl get deployments`。输出类似于：
 
-    ```
-    NAME               DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
-    nginx-deployment   3         3         3            3           18s
-    ```
+   ```
+   NAME               DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
+   nginx-deployment   3         3         3            3           18s
+   ```
 
    <!--
    Notice that the Deployment has created all three replicas, and all replicas are up-to-date (they contain the latest Pod template) and available.
@@ -1504,7 +1504,7 @@ deployment.apps/nginx-deployment patched
 Once the deadline has been exceeded, the Deployment controller adds a DeploymentCondition with the following
 attributes to the Deployment's `.status.conditions`:
 -->
-超过截止时间后， Deployment 控制器将添加具有以下属性的 DeploymentCondition 到
+超过截止时间后，Deployment 控制器将添加具有以下属性的 DeploymentCondition 到
 Deployment 的 `.status.conditions` 中：
 
 * Type=Progressing
@@ -1514,7 +1514,9 @@ Deployment 的 `.status.conditions` 中：
 <!--
 See the [Kubernetes API conventions](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties) for more information on status conditions.
 -->
-参考 [Kubernetes API 约定](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties) 获取更多状态状况相关的信息。
+参考
+[Kubernetes API 约定](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties)
+获取更多状态状况相关的信息。
 
 <!--
  Kubernetes takes no action on a stalled Deployment other than to report a status condition with

content/zh/docs/concepts/workloads/controllers/garbage-collection.md

@@ -1,13 +1,13 @@
 ---
 title: 垃圾收集
 content_type: concept
-weight: 70
+weight: 60
 ---
 
 <!--
 title: Garbage Collection
 content_type: concept
-weight: 70
+weight: 60
 -->
 
 <!-- overview -->

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

@@ -5,7 +5,7 @@ feature:
   title: 批量执行
   description: >
     除了服务之外，Kubernetes 还可以管理你的批处理和 CI 工作负载，在期望时替换掉失效的容器。
-weight: 60
+weight: 50
 ---
 <!--
 reviewers:
@@ -17,7 +17,7 @@ feature:
   title: Batch execution
   description: >
     In addition to services, Kubernetes can manage your batch and CI workloads, replacing containers that fail, if desired.
-weight: 60
+weight: 50
 -->
 
 <!-- overview -->