Merge pull request #52025 from my-git9/npa-24953

[zh-cn]sync event limitrange resource-quota group-version-resource spec

Author: k8s-ci-robot

content/zh-cn/docs/reference/glossary/event.md

@@ -4,7 +4,7 @@ id: event
 date: 2022-01-16
 full_link: /zh-cn/docs/reference/kubernetes-api/cluster-resources/event-v1/
 short_description: >
-  事件（Event）是描述系统中某些状态变化的 Kubernetes 对象。 
+  描述集群中某些状态变化的 Kubernetes 对象。
 aka: 
 tags:
 - core-object
@@ -16,24 +16,25 @@ id: event
 date: 2022-01-16
 full_link: /docs/reference/kubernetes-api/cluster-resources/event-v1/
 short_description: >
-   Events are Kubernetes objects that describe some state change in the system.
+   Kubernetes objects that describe some state change in the cluster.
 aka: 
 tags:
 - core-object
 - fundamental
 -->
 
 <!--
-Event is a Kubernetes object that describes state change/notable occurrences in the system.
+A Kubernetes {{< glossary_tooltip text="object" term_id="object" >}} that describes state changes
+or notable occurrences in the cluster.
 -->
-事件（Event）是描述系统状态变化以及需要注意的事情的 Kubernetes 对象。
-
+一个 Kubernetes {{< glossary_tooltip text="对象" term_id="object" >}}，
+描述集群中的状态状态变化或需要注意的事件。
 <!--more-->
 
 <!--
-Events have a limited retention time and triggers and messages may evolve with time. 
-Event consumers should not rely on the timing of an event with a given reason reflecting a consistent underlying trigger, 
-or the continued existence of events with that reason. 
+Events have a limited retention time and triggers and messages may evolve with time.
+Event consumers should not rely on the timing of an event with a given reason reflecting a consistent underlying trigger,
+or the continued existence of events with that reason.
 -->
 事件的保留时间有限，随着时间推进，其触发方式和消息都可能发生变化。
 事件用户不应该对带有给定原因（反映下层触发源）的时间特征有任何依赖，

content/zh-cn/docs/reference/glossary/group-version-resource.md

@@ -4,37 +4,42 @@ id: gvr
 date: 2023-07-24
 short_description: >
   Kubernetes API 的 API 组、API 版本和名称。
-
 aka: ["GVR"]
 tags:
 - architecture
 ---
-
 <!--
 title: Group Version Resource
 id: gvr
 date: 2023-07-24
 short_description: >
-  The API group, API version and name of a Kubernetes API. 
+  The API group, API version and name of a Kubernetes API.
 
 aka: ["GVR"]
 tags:
 - architecture
 -->
 
 <!--
-Means of representing unique Kubernetes API resource.
+Means of representing specific Kubernetes APIs uniquely.
 -->
-表示唯一的 Kubernetes API 资源的方法。
+表示特定的 Kubernetes API 的唯一方法。
 
 <!--more-->
 
 <!--
-Group Version Resources (GVRs) specify the API group, API version, and resource (name for the object kind as it appears in the URI) associated with accessing a particular id of object in Kubernetes.
+Group Version Resources (GVRs) specify the API group, API version, and _resource_
+(name for the object kind as it appears in the URI) associated with accessing a particular id of object in Kubernetes.
 GVRs let you define and distinguish different Kubernetes objects, and to specify a way of accessing
 objects that is stable even as APIs change.
 -->
-组版本资源（Group Version Resource, GVR）指定了与访问 Kubernetes 中对象的特定 id 相关联的 API 组、API
-版本和资源（URI 中显示的对象类别的名称）。GVR 允许你定义和区分不同的 Kubernetes 对象，
+组版本资源（Group Version Resource，GVR）指定了与访问 Kubernetes 中对象的特定 id 相关联的 API 组、API
+版本和**资源**（URI 中显示的对象类别的名称）。GVR 允许你定义和区分不同的 Kubernetes 对象，
 并指定了一种访问对象的方式，即使在 API 发生变化时这也是一种稳定的访问方式。
 
+<!--
+In this usage, _resource_ refers to an HTTP resource. Because some APIs are namespaced, a GVR may
+not refer to a specific {{< glossary_tooltip text="API resource" term_id="api-resource" >}}.
+-->
+在本用法中，**资源**指的是 HTTP 资源。因为某些 API 是命名空间化的，因此
+GVR 可能不会引用特定的

content/zh-cn/docs/reference/glossary/limitrange.md

@@ -2,10 +2,9 @@
 title: LimitRange
 id: limitrange
 date: 2019-04-15
-full_link:  /docs/concepts/policy/limit-range/
+full_link:  /zh-cn/docs/concepts/policy/limit-range/
 short_description: >
   提供约束来限制命名空间中每个容器或 Pod 的资源消耗。
-
 aka: 
 tags:
 - core-object
@@ -14,11 +13,8 @@ tags:
 related:
  - pod
  - container
-
 ---
-
 <!--
----
 title: LimitRange
 id: limitrange
 date: 2019-04-15
@@ -34,18 +30,27 @@ tags:
 related:
  - pod
  - container
-
----
 -->
 
 <!--
- Provides constraints to limit resource consumption per {{< glossary_tooltip text="Containers" term_id="container" >}} or {{< glossary_tooltip text="Pods" term_id="pod" >}} in a namespace.
+Constraints resource consumption per {{< glossary_tooltip text="container" term_id="container" >}}
+or {{< glossary_tooltip text="Pod" term_id="pod" >}},
+specified for a particular {{< glossary_tooltip text="namespace" term_id="namespace" >}}.
 -->
- 提供约束来限制命名空间中每个 {{< glossary_tooltip text="容器（Containers）" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 的资源消耗。
+指定特定 {{< glossary_tooltip text="命名空间（Namespace）" term_id="namespace" >}}
+中每个 {{< glossary_tooltip text="容器（Containers）" term_id="container" >}}
+或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 的资源消耗限制。
 
 <!--more--> 
+
 <!--
-LimitRange limits the quantity of objects that can be created  by type, 
-as well as the amount of compute resources that may be requested/consumed by individual {{< glossary_tooltip text="Containers" term_id="container" >}} or {{< glossary_tooltip text="Pods" term_id="pod" >}} in a namespace.
+A [LimitRange](/docs/concepts/policy/limit-range/) either limits the quantity of
+{{< glossary_tooltip text="API resources" term_id="api-resource" >}}
+that can be created (for a particular resource type),
+or the amount of {{< glossary_tooltip text="infrastructure resources" term_id="infrastructure-resource" >}}
+that may be requested/consumed by individual containers or Pods within a namespace.
 -->
-LimitRange 按照类型来限制命名空间中对象能够创建的数量，以及单个 {{< glossary_tooltip text="容器（Containers）" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 可以请求/使用的计算资源量。
+[LimitRange](/zh-cn/docs/concepts/policy/limit-range/) 用来限制可以创建的
+{{< glossary_tooltip text="API 资源" term_id="api-resource" >}}的数量（针对特定资源类型），
+或者限制命名空间内单个容器或 Pod 可请求/消耗的
+{{< glossary_tooltip text="基础设施资源" term_id="infrastructure-resource" >}}的量。

content/zh-cn/docs/reference/glossary/resource-quota.md

@@ -1,19 +1,18 @@
 ---
-title: 资源配额（Resource Quotas）
+title: 资源配额（ResourceQuota）
 id: resource-quota
 date: 2018-04-12
 full_link: /zh-cn/docs/concepts/policy/resource-quotas/
 short_description: >
   资源配额提供了限制每个命名空间的资源消耗总和的约束。
-
 aka: 
 tags:
 - fundamental
 - operation
 - architecture
 ---
 <!--
-title: Resource Quotas
+title: ResourceQuota
 id: resource-quota
 date: 2018-04-12
 full_link: /docs/concepts/policy/resource-quotas/
@@ -28,13 +27,20 @@ tags:
 -->
 
 <!--
- Provides constraints that limit aggregate resource consumption per {{< glossary_tooltip term_id="namespace" >}}.
+Object that constrains aggregate resource
+consumption, per {{< glossary_tooltip term_id="namespace" >}}.
 -->
-资源配额提供了限制每个 {{< glossary_tooltip text="命名空间" term_id="namespace">}} 的资源消耗总和的约束。
+用于限制每个{{< glossary_tooltip text="命名空间" term_id="namespace" >}}的资源消耗总和的对象。
 
-<!--more--> 
+<!--more-->
 
 <!--
-Limits the quantity of objects that can be created in a namespace by type, as well as the total amount of compute resources that may be consumed by resources in that project.
+A ResourceQuota can either limits the quantity of {{< glossary_tooltip text="API resources" term_id="api-resource" >}}
+that can be created in a namespace by type, or it can set a limit on the total amount of
+{{< glossary_tooltip text="infrastructure resources" term_id="infrastructure-resource" >}}
+that may be consumed on behalf of the namespace (and the objects within it).
 -->
-限制了命名空间中每种对象可以创建的数量，也限制了项目中可被资源对象利用的计算资源总数。
+资源配额可以限制命名空间中按类型创建的
+{{< glossary_tooltip text="API 资源" term_id="api-resource" >}}的数量，
+或者它可以设置代表命名空间（及其内部的对象）可消耗的
+{{< glossary_tooltip text="基础设施资源" term_id="infrastructure-resource" >}}总量的限制。

content/zh-cn/docs/reference/glossary/spec.md

@@ -4,7 +4,7 @@ id: spec
 date: 2023-12-17
 full_link: /zh-cn/docs/concepts/overview/working-with-objects/#object-spec-and-status
 short_description: >
-  在 Kubernetes 清单中的此字段用来定义特定 Kubernetes 对象的预期状态或预期配置。
+  在 Kubernetes 清单中的此字段用来定义预期状态或预期配置。
 
 aka:
 tags:
@@ -17,7 +17,7 @@ id: spec
 date: 2023-12-17
 full_link: /docs/concepts/overview/working-with-objects/#object-spec-and-status
 short_description: >
-  This field in Kubernetes manifests defines the desired state or configuration for specific Kubernetes objects.
+  Field in Kubernetes manifests that defines the desired state or configuration.
 
 aka:
 tags:
@@ -33,15 +33,16 @@ Defines how each object, like Pods or Services, should be configured and its des
 <!--more-->
 
 <!--
-Almost every Kubernetes object includes two nested object fields that govern the object's configuration: the object spec and the object status. For objects that have a spec, you have to set this when you create the object, providing a description of the characteristics you want the resource to have: its desired state.
+Almost every Kubernetes object includes two nested object fields that govern the object's configuration: the object spec and the object status. For objects that have a spec, you have to set this when you create the object, providing a description of the characteristics you want the {{< glossary_tooltip text="resource" term_id="api-resource" >}} to have: its desired state.
 -->
 几乎每个 Kubernetes 对象都包含两个嵌套的对象字段，用于治理对象本身的配置：
 对象规约（spec）和对象状态（status）。
-对于具有规约的对象，你必须在创建对象时设置规约，并提供资源所需特征的描述：即其预期状态。
+对于具有规约的对象，你必须在创建对象时设置规约，并提供{{< glossary_tooltip text="资源" term_id="api-resource" >}}所需特征的描述：
+即其预期状态。
 
 <!--
-It varies for different objects like Pods, StatefulSets, and Services, detailing settings such as containers, volumes, replicas, ports,   
-and other specifications unique to each object type. This field encapsulates what state Kubernetes should maintain for the defined   
+It varies for different objects like Pods, StatefulSets, and Services, detailing settings such as containers, volumes, replicas, ports,
+and other specifications unique to each object type. This field encapsulates what state Kubernetes should maintain for the defined
 object.
 -->
 此字段对于 Pod、StatefulSet 和 Service 等不同对象会有所差异，