sync service topology-aware-routing custom-resource-definition-versioning

Author: asa3311

content/zh-cn/docs/concepts/services-networking/service.md

@@ -499,13 +499,13 @@ the EndpointSlice manifest: a TCP connection to 10.1.2.3 or 10.4.5.6, on port 93
 {{< note >}}
 <!--
 The Kubernetes API server does not allow proxying to endpoints that are not mapped to
-pods. Actions such as `kubectl proxy <service-name>` where the service has no
+pods. Actions such as `kubectl port-forward service/<service-name> forwardedPort:servicePort` where the service has no
 selector will fail due to this constraint. This prevents the Kubernetes API server
 from being used as a proxy to endpoints the caller may not be authorized to access.
 -->
 Kubernetes API 服务器不允许将流量代理到未被映射至 Pod 上的端点。由于此约束，当 Service
-没有选择算符时，诸如 `kubectl proxy <service-name>` 之类的操作将会失败。这可以防止
-Kubernetes API 服务器被用作调用者可能无权访问的端点的代理。
+没有选择算符时，诸如 `kubectl port-forward service/<service-name> forwardedPort:servicePort` 之类的操作将会失败。
+这可以防止 Kubernetes API 服务器被用作调用者可能无权访问的端点的代理。
 {{< /note >}}
 
 <!--

content/zh-cn/docs/concepts/services-networking/topology-aware-routing.md

@@ -348,11 +348,11 @@ Kubernetes 的部署方式有很多种，没有一种按区域分配端点的启
 <!--
 * Follow the [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) tutorial
 * Learn about the
-  [trafficDistribution](/docs/concepts/services-networking/service/#trafic-distribution)
+  [trafficDistribution](/docs/concepts/services-networking/service/#traffic-distribution)
   field, which is closely related to the `service.kubernetes.io/topology-mode`
   annotation and provides flexible options for traffic routing within
   Kubernetes.
 -->
 * 参阅[使用 Service 连接到应用](/zh-cn/docs/tutorials/services/connect-applications-service/)教程。
-* 进一步了解 [trafficDistribution](/zh-cn/docs/concepts/services-networking/service/#trafic-distribution)字段，
+* 进一步了解 [trafficDistribution](/zh-cn/docs/concepts/services-networking/service/#traffic-distribution)字段，
   该字段与 `service.kubernetes.io/topology-mode` 注解密切相关，并为 Kubernetes 中的流量路由提供灵活的配置选项。

content/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning.md

@@ -1168,7 +1168,7 @@ with the `response` stanza populated, serialized to JSON.
 If conversion succeeds, a webhook should return a `response` stanza containing the following fields:
 * `uid`, copied from the `request.uid` sent to the webhook
 * `result`, set to `{"status":"Success"}`
-* `convertedObjects`, containing all of the objects from `request.objects`, converted to `request.desiredVersion`
+* `convertedObjects`, containing all of the objects from `request.objects`, converted to `request.desiredAPIVersion`
 
 Example of a minimal successful response from a webhook:
 -->
@@ -1183,7 +1183,7 @@ Webhook 响应包含 200 HTTP 状态代码、`Content-Type: application/json`，
 * `uid`，从发送到 webhook 的 `request.uid` 复制而来
 * `result`，设置为 `{"status":"Success"}}`
 * `convertedObjects`，包含来自 `request.objects` 的所有对象，均已转换为
-  `request.desiredVersion`
+  `request.desiredAPIVersion`
 
 Webhook 的最简单成功响应示例：