diff --git a/content/zh-cn/docs/contribute/new-content/open-a-pr.md b/content/zh-cn/docs/contribute/new-content/open-a-pr.md
index 00e0a41a18..169007ebd4 100644
--- a/content/zh-cn/docs/contribute/new-content/open-a-pr.md
+++ b/content/zh-cn/docs/contribute/new-content/open-a-pr.md
@@ -343,7 +343,7 @@ Figure 2. Working from a local fork to make your changes.
 <!--
 ### Create a branch
 
-1. Decide which branch base to your work on:
+1. Decide which branch to base your work on:
 
    - For improvements to existing content, use `upstream/main`.
    - For new content about existing features, use `upstream/main`.
diff --git a/content/zh-cn/docs/setup/best-practices/cluster-large.md b/content/zh-cn/docs/setup/best-practices/cluster-large.md
index 21c75c5b91..c38c2d688b 100644
--- a/content/zh-cn/docs/setup/best-practices/cluster-large.md
+++ b/content/zh-cn/docs/setup/best-practices/cluster-large.md
@@ -196,7 +196,7 @@ many nodes, consider the following:
   as you scale out your cluster.
 * Many addons scale horizontally - you add capacity by running more pods - but with
   a very large cluster you may also need to raise CPU or memory limits slightly.
-  The VerticalPodAutoscaler can run in _recommender_ mode to provide suggested
+  The [Vertical Pod Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme) can run in _recommender_ mode to provide suggested
   figures for requests and limits.
 * Some addons run as one copy per node, controlled by a {{< glossary_tooltip text="DaemonSet"
   term_id="daemonset" >}}: for example, a node-level log aggregator. Similar to
@@ -209,8 +209,8 @@ many nodes, consider the following:
   对于这些附加组件，请在扩大集群时加大资源请求和资源限制。
 * 许多水平扩展插件 —— 你可以通过运行更多的 Pod 来增加容量——但是在大规模集群下，
   可能还需要稍微提高 CPU 或内存限制。
-  VerticalPodAutoscaler 可以在 **recommender** 模式下运行，
-  以提供有关请求和限制的建议数字。
+  [Vertical Pod Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme)
+  可以在 **recommender** 模式下运行，以提供有关请求和限制的建议数字。
 * 一些插件在每个节点上运行一个副本，并由 DaemonSet 控制：
   例如，节点级日志聚合器。与水平扩展插件的情况类似，
   你可能还需要稍微提高 CPU 或内存限制。
diff --git a/content/zh-cn/docs/setup/best-practices/multiple-zones.md b/content/zh-cn/docs/setup/best-practices/multiple-zones.md
index 9636b38a93..9d78381363 100644
--- a/content/zh-cn/docs/setup/best-practices/multiple-zones.md
+++ b/content/zh-cn/docs/setup/best-practices/multiple-zones.md
@@ -47,13 +47,13 @@ Kubernetes 从设计上允许同一个 Kubernetes 集群跨多个失效区来运
 <!--
 ## Control plane behavior
 
-All [control plane components](/docs/concepts/overview/components/#control-plane-components)
+All [control plane components](/docs/concepts/architecture/#control-plane-components)
 support running as a pool of interchangeable resources, replicated per
 component.
 -->
 ## 控制面行为   {#control-plane-behavior}
 
-所有的[控制面组件](/zh-cn/docs/concepts/overview/components/#control-plane-components)
+所有的[控制面组件](/zh-cn/docs/concepts/architecture/#control-plane-components)
 都支持以一组可相互替换的资源池的形式来运行，每个组件都有多个副本。
 
 <!--