From b5f8e418d9f9704e9100295ed91510aa0bf91968 Mon Sep 17 00:00:00 2001
From: Hu Shuai <hus.fnst@fujitsu.com>
Date: Tue, 9 Aug 2022 08:39:34 +0800
Subject: [PATCH] [zh-cn] resync: proxies.md

Signed-off-by: Hu Shuai <hus.fnst@fujitsu.com>
---
 .../zh-cn/docs/concepts/cluster-administration/proxies.md   | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/zh-cn/docs/concepts/cluster-administration/proxies.md b/content/zh-cn/docs/concepts/cluster-administration/proxies.md
index 350295c4f9..287d534d8f 100644
--- a/content/zh-cn/docs/concepts/cluster-administration/proxies.md
+++ b/content/zh-cn/docs/concepts/cluster-administration/proxies.md
@@ -46,7 +46,7 @@ There are several different proxies you may encounter when using Kubernetes:
     - 添加认证头信息
 
 <!--
-1.  The [apiserver proxy](/docs/tasks/access-application-cluster/access-cluster/#discovering-builtin-services):
+1.  The [apiserver proxy](/docs/tasks/access-application-cluster/access-cluster-services/#discovering-builtin-services):
 
     - is a bastion built into the apiserver
     - connects a user outside of the cluster to cluster IPs which otherwise might not be reachable
@@ -56,7 +56,7 @@ There are several different proxies you may encounter when using Kubernetes:
     - can be used to reach a Node, Pod, or Service
     - does load balancing when used to reach a Service
 -->
-2. [apiserver proxy](/zh-cn/docs/tasks/access-application-cluster/access-cluster/#discovering-builtin-services)：
+2. [apiserver proxy](/zh-cn/docs/tasks/access-application-cluster/access-cluster-services/#discovering-builtin-services)：
 
     - 是一个建立在 apiserver 内部的“堡垒”
     - 将集群外部的用户与集群 IP 相连接，这些IP是无法通过其他方式访问的
@@ -115,7 +115,7 @@ There are several different proxies you may encounter when using Kubernetes:
 
 <!--
 Kubernetes users will typically not need to worry about anything other than the first two types.  The cluster admin
-will typically ensure that the latter types are setup correctly.
+will typically ensure that the latter types are set up correctly.
 -->
 
 Kubernetes 用户通常只需要关心前两种类型的代理，集群管理员通常需要确保后面几种类型的代理设置正确。