diff --git a/content/zh-cn/docs/concepts/scheduling-eviction/kube-scheduler.md b/content/zh-cn/docs/concepts/scheduling-eviction/kube-scheduler.md
index ac721e535fa..58096b6a439 100644
--- a/content/zh-cn/docs/concepts/scheduling-eviction/kube-scheduler.md
+++ b/content/zh-cn/docs/concepts/scheduling-eviction/kube-scheduler.md
@@ -64,16 +64,16 @@ write your own scheduling component and use that instead.
 在设计上允许你自己编写一个调度组件并替换原有的 kube-scheduler。
 
 <!--
-For every newly created pods or other unscheduled pods, kube-scheduler
-selects a optimal node for them to run on.  However, every container in
-pods has different requirements for resources and every pod also has
-different requirements. Therefore, existing nodes need to be filtered
-according to the specific scheduling requirements.
+Kube-scheduler selects an optimal node to run newly created or not yet
+scheduled (unscheduled) pods. Since containers in pods - and pods themselves -
+can have different requirements, the scheduler filters out any nodes that
+don't meet a Pod's specific scheduling needs. Alternatively, the API lets
+you specify a node for a Pod when you create it, but this is unusual
+and is only done in special cases.
 -->
-对每一个新创建的 Pod 或者是未被调度的 Pod，kube-scheduler 会选择一个最优的节点去运行这个 Pod。
-然而，Pod 内的每一个容器对资源都有不同的需求，
-而且 Pod 本身也有不同的需求。因此，Pod 在被调度到节点上之前，
-根据这些特定的调度需求，需要对集群中的节点进行一次过滤。
+Kube-scheduler 选择一个最佳节点来运行新创建的或尚未调度（unscheduled）的 Pod。
+由于 Pod 中的容器和 Pod 本身可能有不同的要求，调度程序会过滤掉任何不满足 Pod 特定调度需求的节点。
+或者，API 允许你在创建 Pod 时为它指定一个节点，但这并不常见，并且仅在特殊情况下才会这样做。
 
 <!--
 In a cluster, Nodes that meet the scheduling requirements for a Pod
diff --git a/content/zh-cn/docs/concepts/services-networking/service.md b/content/zh-cn/docs/concepts/services-networking/service.md
index e00babba3e6..db8907865d0 100644
--- a/content/zh-cn/docs/concepts/services-networking/service.md
+++ b/content/zh-cn/docs/concepts/services-networking/service.md
@@ -165,7 +165,7 @@ targets TCP port 9376 on any Pod with the `app.kubernetes.io/name=MyApp` label.
 
 Kubernetes assigns this Service an IP address (sometimes called the "cluster IP"),
 which is used by the Service proxies
-(see [Virtual IPs and service proxies](#virtual-ips-and-service-proxies) below).
+(see [Virtual IP addressing mechanism](#virtual-ip-addressing-mechanism) below).
 
 The controller for the Service selector continuously scans for Pods that
 match its selector, and then POSTs any updates to an Endpoint object
@@ -175,7 +175,7 @@ also named "my-service".
 TCP 端口 9376，并且具有标签 `app.kubernetes.io/name=MyApp` 的 Pod 上。
 
 Kubernetes 为该服务分配一个 IP 地址（有时称为 “集群 IP”），该 IP 地址由服务代理使用。
-(请参见下面的 [VIP 和 Service 代理](#virtual-ips-and-service-proxies)).
+(请参见下面的[虚拟 IP 寻址机制](#virtual-ip-addressing-mechanism)).
 
 服务选择算符的控制器不断扫描与其选择算符匹配的 Pod，然后将所有更新发布到也称为
 “my-service” 的 Endpoint 对象。