Merge pull request #23845 from baiyutang/patch-2

Update access-cluster.md

content/zh/docs/tasks/access-application-cluster/access-cluster.md

@@ -540,7 +540,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
 -->
-1.  [apiserver 代理](#discovering-builtin-services)：
+2.  [apiserver 代理](#discovering-builtin-services)：
 
     - 内置于 apiserver 中
     - 将集群外部的用户连接到集群 IP，否则这些 IP 可能无法访问
@@ -559,7 +559,7 @@ There are several different proxies you may encounter when using Kubernetes:
     - provides load balancing
     - is just used to reach services
 -->
-1.  [kube proxy](/docs/concepts/services-networking/service/#ips-and-vips)：
+3.  [kube proxy](/docs/concepts/services-networking/service/#ips-and-vips)：
 
     - 运行在每个节点上
     - 代理 UDP 和 TCP
@@ -574,7 +574,7 @@ There are several different proxies you may encounter when using Kubernetes:
     - sits between all clients and one or more apiservers
     - acts as load balancer if there are several apiservers.
 -->
-1.  位于 apiserver 之前的 Proxy/Load-balancer：
+4.  位于 apiserver 之前的 Proxy/Load-balancer：
 
     - 存在和实现因集群而异（例如 nginx）
     - 位于所有客户和一个或多个 apiserver 之间
@@ -591,7 +591,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.
 -->
-1.  外部服务上的云负载均衡器：
+5.  外部服务上的云负载均衡器：
 
     - 由一些云提供商提供（例如 AWS ELB，Google Cloud Load Balancer）
     - 当 Kubernetes 服务类型为 `LoadBalancer` 时自动创建