Merge pull request #42599 from mengjiao-liu/fix-maxSkew-desc

Fix topologySpreadConstraints maxSkew Chinese translation and resync page

content/zh-cn/docs/concepts/scheduling-eviction/topology-spread-constraints.md

@@ -145,7 +145,7 @@ your cluster. Those fields are:
   - if you select `whenUnsatisfiable: ScheduleAnyway`, the scheduler gives higher
     precedence to topologies that would help reduce the skew.
 -->
-- **maxSkew** 描述这些 Pod 可能被均匀分布的程度。你必须指定此字段且该数值必须大于零。
+- **maxSkew** 描述这些 Pod 可能被不均匀分布的程度。你必须指定此字段且该数值必须大于零。
   其语义将随着 `whenUnsatisfiable` 的值发生变化：
 
   - 如果你选择 `whenUnsatisfiable: DoNotSchedule`，则 `maxSkew` 定义目标拓扑中匹配 Pod 的数量与
@@ -468,7 +468,7 @@ can use a manifest similar to:
 -->
 如果你希望新来的 Pod 均匀分布在现有的可用区域，则可以按如下设置其清单：
 
-{{< codenew file="pods/topology-spread-constraints/one-constraint.yaml" >}}
+{{% code file="pods/topology-spread-constraints/one-constraint.yaml" %}}
 
 <!--
 From that manifest, `topologyKey: zone` implies the even distribution will only be applied
@@ -589,7 +589,7 @@ by node and by zone:
 -->
 可以组合使用 2 个拓扑分布约束来控制 Pod 在节点和可用区两个维度上的分布：
 
-{{< codenew file="pods/topology-spread-constraints/two-constraints.yaml" >}}
+{{% code file="pods/topology-spread-constraints/two-constraints.yaml" %}}
 
 <!--
 In this case, to match the first constraint, the incoming Pod can only be placed onto
@@ -714,7 +714,7 @@ Similarly, Kubernetes also respects `spec.nodeSelector`.
 以便将 Pod `mypod` 放置在可用区 `B` 上，而不是可用区 `C` 上。
 同样，Kubernetes 也会一样处理 `spec.nodeSelector`。
 
-{{< codenew file="pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml" >}}
+{{% code file="pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml" %}}
 
 <!--
 ## Implicit conventions