diff --git a/content/zh-cn/docs/reference/glossary/node.md b/content/zh-cn/docs/reference/glossary/node.md
index be28602cac..5e6f73663f 100644
--- a/content/zh-cn/docs/reference/glossary/node.md
+++ b/content/zh-cn/docs/reference/glossary/node.md
@@ -38,13 +38,11 @@ In early Kubernetes versions, Nodes were called "Minions".
 -->
 工作机器可以是虚拟机也可以是物理机，取决于集群的配置。
 其上部署了运行 {{< glossary_tooltip text="Pods" term_id="pod" >}}
-所必需的本地守护进程或服务，
-并由主控组件来管理。
-节点上的的守护进程包括 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}、
+所必需的本地守护进程或服务，并由主控组件来管理。
+节点上的守护进程包括 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}、
 {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}
 以及一个 {{< glossary_tooltip term_id="docker" >}} 这种
 实现了 {{< glossary_tooltip text="CRI" term_id="cri" >}}
 的容器运行时。
 
 在早期的 Kubernetes 版本中，节点也称作 "Minions"。
-
diff --git a/content/zh-cn/docs/reference/glossary/pod-lifecycle.md b/content/zh-cn/docs/reference/glossary/pod-lifecycle.md
index 8eff328c4d..d5f592c886 100644
--- a/content/zh-cn/docs/reference/glossary/pod-lifecycle.md
+++ b/content/zh-cn/docs/reference/glossary/pod-lifecycle.md
@@ -37,6 +37,6 @@ A high-level summary of what phase the Pod is in within its lifecyle.
 The [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/) is defined by the states or phases of a Pod. There are five possible Pod phases: Pending, Running, Succeeded, Failed, and Unknown. A high-level description of the Pod state is summarized in the [PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core) `phase` field.
 -->
 [Pod 生命周期](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/) 是关于 Pod
-处于哪个阶段的概述。包含了下面5种可能的的阶段: Running、Pending、Succeeded、
+处于哪个阶段的概述。包含了下面 5 种可能的阶段: Running、Pending、Succeeded、
 Failed、Unknown。关于 Pod 的阶段的更高级描述请查阅
 [PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core) `phase` 字段。
diff --git a/content/zh-cn/docs/reference/glossary/service-catalog.md b/content/zh-cn/docs/reference/glossary/service-catalog.md
index a50e6e4778..969dc425ce 100644
--- a/content/zh-cn/docs/reference/glossary/service-catalog.md
+++ b/content/zh-cn/docs/reference/glossary/service-catalog.md
@@ -12,7 +12,6 @@ tags:
 ---
 
 <!--
----
 title: Service Catalog
 id: service-catalog
 date: 2018-04-12
@@ -23,22 +22,17 @@ short_description: >
 aka: 
 tags:
 - extension
----
 -->
 
-
 <!--
  A former extension API that enables applications running in Kubernetes clusters to easily use external managed software offerings, such as a datastore service offered by a cloud provider.
 -->
-
-服务目录是一种过去曾经存在的扩展 API，它能让 Kubernetes 集群中运行的应用易于使用外部托管的的软件服务，例如云供应商提供的数据仓库服务。
+服务目录是一种过去曾经存在的扩展 API，它能让 Kubernetes 集群中运行的应用易于使用外部托管的软件服务，例如云供应商提供的数据仓库服务。
 
 <!--more--> 
 
 <!--
 It provided a way to list, provision, and bind with external {{< glossary_tooltip text="Managed Services" term_id="managed-service" >}} without needing detailed knowledge about how those services would be created or managed.
 -->
-
-服务目录可以检索、供应、和绑定外部{{< glossary_tooltip text="托管服务（Managed Services）" term_id="managed-service" >}}，
+服务目录可以检索、供应并绑定外部{{< glossary_tooltip text="托管服务（Managed Services）" term_id="managed-service" >}}，
 而无需知道那些服务具体是怎样创建和托管的。
-
diff --git a/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_delete.md b/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_delete.md
index 58d56ac399..5ffa750d5d 100644
--- a/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_delete.md
+++ b/content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_delete.md
@@ -29,7 +29,7 @@ Token ID of the form "[a-z0-9]{6}" to delete.
 
 这个命令将为你删除指定的引导令牌列表。
 
-`[token-value]` 是要删除的 "[a-z0-9]{6}.[a-z0-9]{16}" 形式的完整令牌或者是 "[a-z0-9]{6}" 形式的的令牌 ID。
+`[token-value]` 是要删除的 "[a-z0-9]{6}.[a-z0-9]{16}" 形式的完整令牌或者是 "[a-z0-9]{6}" 形式的令牌 ID。
 
 ```
 kubeadm token delete [token-value] ...