diff --git a/content/zh-cn/docs/concepts/architecture/leases.md b/content/zh-cn/docs/concepts/architecture/leases.md
index 43a94350a2..b8fa0ab1b4 100644
--- a/content/zh-cn/docs/concepts/architecture/leases.md
+++ b/content/zh-cn/docs/concepts/architecture/leases.md
@@ -41,7 +41,7 @@ namespace. Under the hood, every kubelet heartbeat is an **update** request to t
 the `spec.renewTime` field for the Lease. The Kubernetes control plane uses the time stamp of this field
 to determine the availability of this `Node`.
 
-See [Node Lease objects](/docs/concepts/architecture/nodes/#heartbeats) for more details.
+See [Node Lease objects](/docs/concepts/architecture/nodes/#node-heartbeats) for more details.
 -->
 ## 节点心跳  {#node-heart-beats}
 
@@ -50,7 +50,7 @@ Kubernetes 使用 Lease API 将 kubelet 节点心跳传递到 Kubernetes API 服
 在此基础上，每个 kubelet 心跳都是对该 `Lease` 对象的 **update** 请求，更新该 Lease 的 `spec.renewTime` 字段。
 Kubernetes 控制平面使用此字段的时间戳来确定此 `Node` 的可用性。
 
-更多细节请参阅 [Node Lease 对象](/zh-cn/docs/concepts/architecture/nodes/#heartbeats)。
+更多细节请参阅 [Node Lease 对象](/zh-cn/docs/concepts/architecture/nodes/#node-heartbeats)。
 
 <!--
 ## Leader election
diff --git a/content/zh-cn/docs/concepts/services-networking/topology-aware-routing.md b/content/zh-cn/docs/concepts/services-networking/topology-aware-routing.md
index 4736e7d8b5..1a887cb1b6 100644
--- a/content/zh-cn/docs/concepts/services-networking/topology-aware-routing.md
+++ b/content/zh-cn/docs/concepts/services-networking/topology-aware-routing.md
@@ -347,5 +347,12 @@ 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)
+  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/)教程
+* 参阅[使用 Service 连接到应用](/zh-cn/docs/tutorials/services/connect-applications-service/)教程。
+* 进一步了解 [trafficDistribution](/zh-cn/docs/concepts/services-networking/service/#trafic-distribution)字段，
+  该字段与 `service.kubernetes.io/topology-mode` 注解密切相关，并为 Kubernetes 中的流量路由提供灵活的配置选项。
diff --git a/content/zh-cn/docs/concepts/workloads/pods/downward-api.md b/content/zh-cn/docs/concepts/workloads/pods/downward-api.md
index 2d8e34f9c6..01d5ef87dc 100644
--- a/content/zh-cn/docs/concepts/workloads/pods/downward-api.md
+++ b/content/zh-cn/docs/concepts/workloads/pods/downward-api.md
@@ -155,11 +155,9 @@ The following information is available through environment variables
 <!--
 `status.hostIPs`
 : the IP addresses is a dual-stack version of `status.hostIP`, the first is always the same as `status.hostIP`.
-  The field is available if you enable the `PodHostIPs` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
 -->
 `status.hostIPs`
 : 这组 IP 地址是 `status.hostIP` 的双协议栈版本，第一个 IP 始终与 `status.hostIP` 相同。
-  该字段在启用了 `PodHostIPs` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)后可用。
 
 <!--
 `status.podIP`