squash commit

content/zh-cn/docs/concepts/services-networking/endpoint-slices.md

@@ -176,7 +176,7 @@ the pod is also terminating.
 
 {{< note >}}
 <!--
-Although `serving` is almost identical to `ready`, it was added to prevent break the existing meaning
+Although `serving` is almost identical to `ready`, it was added to prevent breaking the existing meaning
 of `ready`. It may be unexpected for existing clients if `ready` could be `true` for terminating
 endpoints, since historically terminating endpoints were never included in the Endpoints or
 EndpointSlice API to begin with. For this reason, `ready` is _always_ `false` for terminating
@@ -433,13 +433,13 @@ at different times.
 <!--
 Clients of the EndpointSlice API must iterate through all the existing EndpointSlices
 associated to a Service and build a complete list of unique network endpoints. It is
-important to mention that endpoints may be duplicated in different EndointSlices.
+important to mention that endpoints may be duplicated in different EndpointSlices.
 
 You can find a reference implementation for how to perform this endpoint aggregation
 and deduplication as part of the `EndpointSliceCache` code within `kube-proxy`.
 -->
 EndpointSlice API 的客户端必须遍历与 Service 关联的所有现有 EndpointSlices，
-并构建唯一网络端点的完整列表。值得一提的是端点可能在不同的 EndointSlices 中重复。
+并构建唯一网络端点的完整列表。值得一提的是端点可能在不同的 EndpointSlices 中重复。
 
 你可以在 `kube-proxy` 中的 `EndpointSliceCache` 代码中找到有关如何执行此端点聚合和重复数据删除的参考实现。
 {{< /note >}}

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

@@ -218,11 +218,11 @@ Kubernetes 控制平面和每个节点上的 kube-proxy，在使用拓扑感知
 <!-- 
 5. **A zone is not represented in hints:** If the kube-proxy is unable to find
    at least one endpoint with a hint targeting the zone it is running in, it falls
-   to using endpoints from all zones. This is most likely to happen as you add
+   back to using endpoints from all zones. This is most likely to happen as you add
    a new zone into your existing cluster.
 -->
 5. **不在提示中的区域：** 如果 kube-proxy 不能根据一个指示在它所在的区域中发现一个端点，
-   它回撤为使用所有节点的端点。当你的集群新增一个新的区域时，这种情况发生概率很高。
+   它将回退到使用来自所有区域的端点。当你的集群新增一个新的区域时，这种情况发生概率很高。
 
 <!-- 
 ## Constraints

content/zh-cn/docs/concepts/storage/persistent-volumes.md

@@ -150,7 +150,7 @@ needs to enable the `DefaultStorageClass`
 on the API server. This can be done, for example, by ensuring that `DefaultStorageClass` is
 among the comma-delimited, ordered list of values for the `--enable-admission-plugins` flag of
 the API server component. For more information on API server command-line flags,
-check [kube-apiserver](/docs/admin/kube-apiserver/) documentation.
+check [kube-apiserver](/docs/reference/command-line-tools-reference/kube-apiserver/) documentation.
 -->
 为了基于存储类完成动态的存储制备，集群管理员需要在 API 服务器上启用 `DefaultStorageClass`
 [准入控制器](/zh-cn/docs/reference/access-authn-authz/admission-controllers/#defaultstorageclass)。
@@ -1897,7 +1897,7 @@ and `CrossNamespaceVolumeDataSource`
 the kube-apiserver, kube-controller-manager.
 Also, you must enable the `CrossNamespaceVolumeDataSource` feature gate for the csi-provisioner.
 
-Enabling the `CrossNamespaceVolumeDataSource` feature gate allow you to specify
+Enabling the `CrossNamespaceVolumeDataSource` feature gate allows you to specify
 a namespace in the dataSourceRef field.
 -->
 Kubernetes 支持跨名字空间卷数据源。
@@ -1927,7 +1927,7 @@ ReferenceGrant 是 `gateway.networking.k8s.io` 扩展 API 的一部分。更多
 <!--
 ## Data source references
 
-The `dataSourceRef` field behaves almost the same as the `dataSource` field. If either one is
+The `dataSourceRef` field behaves almost the same as the `dataSource` field. If one is
 specified while the other is not, the API server will give both fields the same value. Neither
 field can be changed after creation, and attempting to specify different values for the two
 fields will result in a validation error. Therefore the two fields will always have the same