Merge pull request #25244 from jialaijun/update_glossary

update the markdown file in the glossary directory for Chinese version.

Author: k8s-ci-robot

content/zh/docs/reference/glossary/addons.md

@@ -1,5 +1,5 @@
 ---
-title: 附加组件
+title: 附加组件（Add-ons）
 id: addons
 date: 2019-12-15
 full_link: /zh/docs/concepts/cluster-administration/addons/
@@ -10,28 +10,31 @@ aka:
 tags:
 - tool
 ---
-  扩展 Kubernetes 功能的资源。
-
 <!--
 ---
 title: Add-ons
 id: addons
 date: 2019-12-15
-full_link: /zh/docs/concepts/cluster-administration/addons/
+full_link: /docs/concepts/cluster-administration/addons/
 short_description: >
   Resources that extend the functionality of Kubernetes.
 
 aka:
 tags:
 - tool
 ---
+-->
+
+
+<!--
   Resources that extend the functionality of Kubernetes.
 -->
+  扩展 Kubernetes 功能的资源。
 
 
 <!--more-->
 
 <!-- 
-[Installing addons](/docs/concepts/cluster-administration/addons/) explains more about using add-ons with your cluster, and lists some popular add-ons. 
+[Installing addons](/docs/concepts/cluster-administration/addons/) explains more about using add-ons with your cluster, and lists some popular add-ons.
 -->
-[安装附加组件](/docs/concepts/cluster-administration/addons/) 阐释了更多关于如何在集群内使用附加组件，并列出了一些流行的附加组件。
+[安装附加组件](/zh/docs/concepts/cluster-administration/addons/) 阐释了更多关于如何在集群内使用附加组件，并列出了一些流行的附加组件。

content/zh/docs/reference/glossary/admission-controller.md

@@ -1,5 +1,5 @@
 ---
-title: 准入控制器
+title: 准入控制器（Admission Controller）
 id: admission-controller
 date: 2019-06-28
 full_link: /zh/docs/reference/access-authn-authz/admission-controllers/
@@ -11,25 +11,31 @@ tags:
 - security
 ---
 
+
 <!--
 ---
 title: Admission Controller
 id: admission-controller
 date: 2019-06-28
-full_link: /zh/docs/reference/access-authn-authz/admission-controllers/
+full_link: /docs/reference/access-authn-authz/admission-controllers/
 short_description: >
   A piece of code that intercepts requests to the Kubernetes API server prior to persistence of the object.
 
 aka:
 tags:
 - extension
 - security
----
+---																										 
 -->
 
+
+<!--
+A piece of code that intercepts requests to the Kubernetes API server prior to persistence of the object.
+-->
 在对象持久化之前拦截 Kubernetes Api 服务器请求的一段代码
 
 <!--more-->
+
 <!--
 Admission controllers are configurable for the Kubernetes API server and may be “validating”, “mutating”, or
 both. Any admission controller may reject the request. Mutating controllers may modify the objects they admit;
@@ -41,4 +47,4 @@ validating controllers may not.
 准入控制器可针对 Kubernetes Api 服务器进行配置，可以执行验证，变更或两者都执行。任何准入控制器都可以拒绝访问请求。
 变更（mutating）控制器可以修改其允许的对象，验证（validating）控制器则不可以。
 
-* [Kubernetes 文档中的准入控制器](/docs/reference/access-authn-authz/admission-controllers/)
+* [Kubernetes 文档中的准入控制器](/zh/docs/reference/access-authn-authz/admission-controllers/)

content/zh/docs/reference/glossary/aggregation-layer.md

@@ -1,5 +1,5 @@
 ---
-title: 聚合层
+title: 聚合层（Aggregation Layer）
 id: aggregation-layer
 date: 2018-10-08
 full_link: /zh/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
@@ -12,13 +12,12 @@ tags:
 - extension
 - operation
 ---
-
 <!--
 ---
 title: Aggregation Layer
 id: aggregation-layer
 date: 2018-10-08
-full_link: /zh/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
+full_link: /docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
 short_description: >
   The aggregation layer lets you install additional Kubernetes-style APIs in your cluster.
 
@@ -30,16 +29,20 @@ tags:
 ---
 -->
 
+
+
+
 <!--
  The aggregation layer lets you install additional Kubernetes-style APIs in your cluster.
 -->
 
 聚合层允许您在自己的集群上安装额外的 Kubernetes 风格的 API。
 
-<!--more--> 
+<!--more-->
+ 
 
 <!--
-When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
+When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](/docs/tasks/extend-kubernetes/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
 -->
 
-当您配置了 {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} 来 [支持额外的 API](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/)，您就可以在 Kubernetes API 中增加 `APIService` 对象来  "申领（Claim）" 一个 URL 路径。 
+当您配置了 {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} 来 [支持额外的 API](/zh/docs/tasks/extend-kubernetes/configure-aggregation-layer/)，您就可以在 Kubernetes API 中增加 `APIService` 对象来  "申领（Claim）" 一个 URL 路径。 

content/zh/docs/reference/glossary/annotation.md

@@ -1,5 +1,5 @@
 ---
-title: 注解
+title: 注解（Annotation）
 id: annotation
 date: 2018-04-12
 full_link: /zh/docs/concepts/overview/working-with-objects/annotations/
@@ -16,7 +16,7 @@ tags:
 title: Annotation
 id: annotation
 date: 2018-04-12
-full_link: /zh/docs/concepts/overview/working-with-objects/annotations/
+full_link: /docs/concepts/overview/working-with-objects/annotations
 short_description: >
   A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
 
@@ -26,6 +26,8 @@ tags:
 ---
 -->
 
+
+
 <!--
  A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
 -->
@@ -35,8 +37,10 @@ tags:
 <!--more--> 
 
 <!--
-The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by labels. Clients such as tools and libraries can retrieve this metadata.
+The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by {{< glossary_tooltip text="labels" term_id="label" >}}. Clients such as tools and libraries can retrieve this metadata.
 -->
 
-注解中的元数据可大可小，可以是结构化的也可以是非结构化的，并且能包含标签不允许使用的字符。像工具和软件库这样的客户端可以检索这些元数据。
+注解中的元数据可大可小，可以是结构化的也可以是非结构化的，
+并且能包含{{< glossary_tooltip text="标签" term_id="label" >}}不允许使用的字符。
+像工具和软件库这样的客户端可以检索这些元数据。
 

content/zh/docs/reference/glossary/api-group.md

@@ -11,35 +11,40 @@ tags:
 - fundamental
 - architecture
 ---
+
 <!-- 
 ---
 title: API Group
 id: api-group
 date: 2019-09-02
-full_link: /zh/docs/concepts/overview/kubernetes-api/#api-groups
+full_link: /docs/concepts/overview/kubernetes-api/#api-groups
 short_description: >
   A set of related paths in the Kubernetes API.
 
 aka:
 tags:
 - fundamental
 - architecture
----
+---										  
 -->
 
+
 <!-- 
 A set of related paths in Kubernetes API.  
 -->
 Kubernetes API 中的一组相关路径。
 
-<!--more-->
+<!--more-->																																																																											  
 
 <!-- 
 You can enable or disable each API group by changing the configuration of your API server. You can also disable or enable paths to specific resources. API group makes it easier to extend the Kubernetes API. The API group is specified in a REST path and in the `apiVersion` field of a serialized object. 
 -->
-通过更改 API server 的配置，可以启用或禁用每个 API Group。你还可以禁用或启用指向特定资源的路径。API group 使扩展 Kubernetes API 更加的容易。API group 在 REST 路径和序列化对象的 `apiVersion` 字段中指定。
+通过更改 API server 的配置，可以启用或禁用每个 API Group。
+你还可以禁用或启用指向特定资源的路径。
+API group 使扩展 Kubernetes API 更加的容易。
+API group 在 REST 路径和序列化对象的 `apiVersion` 字段中指定。
 
 <!-- 
 * Read [API Group](/docs/concepts/overview/kubernetes-api/#api-groups) for more information. 
 -->
-* 阅读 [API Group](/docs/concepts/overview/kubernetes-api/#api-groups) 了解更多信息。
+* 阅读 [API Group](/zh/docs/concepts/overview/kubernetes-api/#api-groups) 了解更多信息。

content/zh/docs/reference/glossary/app-container.md

@@ -1,5 +1,5 @@
 ---
-title: 应用程序容器
+title: 应用程序容器（App Container）
 id: app-container
 date: 2019-02-12
 full_link:
@@ -10,7 +10,6 @@ aka:
 tags:
 - workload
 ---
-  应用程序容器（或 app 容器）{{< glossary_tooltip text="容器" term_id="container" >}} 在 {{< glossary_tooltip text="pod" term_id="pod" >}} 中，在 {{< glossary_tooltip text="初始化容器" term_id="init-container" >}} 启动完毕后才开始启动。
 
 <!--
 ---
@@ -25,8 +24,14 @@ aka:
 tags:
 - workload
 ---
+-->
+
+<!--
  Application containers (or app containers) are the {{< glossary_tooltip text="containers" term_id="container" >}} in a {{< glossary_tooltip text="pod" term_id="pod" >}} that are started after any {{< glossary_tooltip text="init containers" term_id="init-container" >}} have completed.
 -->
+  应用程序 {{< glossary_tooltip text="容器" term_id="container" >}} （或 app 容器）在 {{< glossary_tooltip text="pod" term_id="pod" >}} 中，在 {{< glossary_tooltip text="初始化容器" term_id="init-container" >}} 启动完毕后才开始启动。
+
+
 
 <!--more-->
 
@@ -37,5 +42,6 @@ once the application container has started.
 If a pod doesn't have any init containers configured, all the containers in that pod are app containers.
 -->
 
-初始化容器使您可以分离对于 {{< glossary_tooltip text="工作负载" term_id="workload" >}} 整体而言很重要的初始化细节，并且一旦应用容器启动，它不需要继续运行。
+初始化容器使您可以分离对于{{< glossary_tooltip text="工作负载" term_id="workload" >}}
+整体而言很重要的初始化细节，并且一旦应用容器启动，它不需要继续运行。
 如果 pod 没有配置任何初始化容器，则该 pod 中的所有容器都是应用程序容器。

content/zh/docs/reference/glossary/application-architect.md

@@ -1,5 +1,5 @@
 ---
-title: 应用架构师
+title: 应用架构师（Application Architect）
 id: application-architect
 date: 2018-04-12
 full_link: 
@@ -10,7 +10,6 @@ aka:
 tags:
 - user-type
 ---
- 应用架构师是负责应用高级设计的人。
 
 <!--
 ---
@@ -25,13 +24,21 @@ aka:
 tags:
 - user-type
 ---
+-->
+
+<!--
  A person responsible for the high-level design of an application.
 -->
+ 应用架构师是负责应用高级设计的人。
+
+			
+
 
 <!--more--> 
 <!--
 An architect ensures that an app's implementation allows it to interact with its surrounding components in a scalable, maintainable way. Surrounding components include databases, logging infrastructure, and other microservices.
 -->
 
-应用架构师确保应用的实现允许它和周边组件进行可扩展的、可持续的交互。周边组件包括数据库、日志基础设施和其他微服务。
+应用架构师确保应用的实现允许它和周边组件进行可扩展的、可持续的交互。
+周边组件包括数据库、日志基础设施和其他微服务。
 

content/zh/docs/reference/glossary/application-developer.md

@@ -1,5 +1,5 @@
 ---
-title: 应用开发者
+title: 应用开发者（Application Developer）
 id: application-developer
 date: 2018-04-12
 full_link: 
@@ -26,8 +26,9 @@ tags:
 ---
 -->
 
+
 <!--
-A person who writes an application that runs in a Kubernetes cluster.
+ A person who writes an application that runs in a Kubernetes cluster.
 -->
 
 编写可以在 Kubernetes 集群上运行的应用的人。

content/zh/docs/reference/glossary/applications.md

@@ -1,5 +1,5 @@
 ---
-title: 应用
+title: 应用（Applications）
 id: applications
 date: 2019-05-12
 full_link:
@@ -24,4 +24,8 @@ tags:
 ---
 -->
 
+
+<!--
+ The layer where various containerized applications run.
+-->
  各种容器化应用运行所在的层。

content/zh/docs/reference/glossary/approver.md

@@ -1,5 +1,5 @@
 ---
-title: 批准者
+title: 批准者（Approver）
 id: approver
 date: 2018-04-12
 full_link: 
@@ -26,6 +26,9 @@ tags:
 ---
 -->
 
+<!--
+ A person who can review and approve Kubernetes code contributions.
+-->
  可以审核并批准 Kubernetes 代码贡献的人。
 
 <!--more--> 
@@ -36,5 +39,4 @@ While code review is focused on code quality and correctness, approval is focuse
 
 代码审核的重点是代码质量和正确性，而批准的重点是对贡献的整体接受。
 整体接受包括向后/向前兼容性、遵守 API 和参数约定、细微的性能和正确性问题、与系统其他部分的交互等。
-批准者状态的作用域是代码库的一部分。
-审批者以前被称为维护者。
+批准者状态的作用域是代码库的一部分。审批者以前被称为维护者。