Merge pull request #39146 from my-git9/zhsync/patch-5

[zh-cn]sync some docs for little change

Author: k8s-ci-robot

content/zh-cn/docs/concepts/cluster-administration/system-traces.md

@@ -143,7 +143,7 @@ The kubelet CRI interface and authenticated http servers are instrumented to gen
 trace spans. As with the apiserver, the endpoint and sampling rate are configurable.
 Trace context propagation is also configured. A parent span's sampling decision is always respected.
 A provided tracing configuration sampling rate will apply to spans without a parent.
-Enabled without a configured endpoint, the default OpenTelemetry Collector reciever address of "localhost:4317" is set.
+Enabled without a configured endpoint, the default OpenTelemetry Collector receiver address of "localhost:4317" is set.
 -->
 kubelet CRI 接口和实施身份验证的 HTTP 服务器被插桩以生成追踪 span。
 与 API 服务器一样，端点和采样率是可配置的。

content/zh-cn/docs/concepts/overview/components.md

@@ -3,7 +3,7 @@ title: Kubernetes 组件
 content_type: concept
 description: >
   Kubernetes 集群由控制平面的组件和一组称为节点的机器组成。
-weight: 20
+weight: 30
 card:
   name: concepts
   weight: 20
@@ -16,7 +16,7 @@ content_type: concept
 description: >
   A Kubernetes cluster consists of the components that are a part of the control
   plane and a set of machines called nodes.
-weight: 20
+weight: 30
 card:
   name: concepts
   weight: 20

content/zh-cn/docs/concepts/overview/kubernetes-api.md

@@ -1,7 +1,7 @@
 ---
 title: Kubernetes API
 content_type: concept
-weight: 30
+weight: 40
 description: >
   Kubernetes API 使你可以查询和操纵 Kubernetes 中对象的状态。
   Kubernetes 控制平面的核心是 API 服务器和它暴露的 HTTP API。
@@ -15,7 +15,7 @@ reviewers:
 - chenopis
 title: The Kubernetes API
 content_type: concept
-weight: 30
+weight: 40
 description: >
   The Kubernetes API lets you query and manipulate the state of objects in Kubernetes.
   The core of Kubernetes' control plane is the API server and the HTTP API that it exposes. Users, the different parts of your cluster, and external components all communicate with one another through the API server.

content/zh-cn/docs/concepts/overview/working-with-objects/namespaces.md

@@ -268,7 +268,7 @@ kubectl api-resources --namespaced=false
 -->
 ## 自动打标签   {#automatic-labelling}
 
-{{< feature-state state="beta" for_k8s_version="1.21" >}}
+{{< feature-state state="beta" for_k8s_version="stable" >}}
 
 <!--
 The Kubernetes control plane sets an immutable {{< glossary_tooltip text="label" term_id="label" >}}

content/zh-cn/docs/concepts/policy/limit-range.md

@@ -91,7 +91,7 @@ LimitRange 的名称必须是合法的
 <!--
 ## LimitRange and admission checks for Pods
 
-A `LimitRange` does **not** check the consistency of the default values it applies. This means that a default value for the _limit_ that is set by `LimitRange` may be less than the _request_ value specified for the container in the spec that a client submits to the API server. If that happens, the final Pod will not be scheduleable.
+A `LimitRange` does **not** check the consistency of the default values it applies. This means that a default value for the _limit_ that is set by `LimitRange` may be less than the _request_ value specified for the container in the spec that a client submits to the API server. If that happens, the final Pod will not be schedulable.
 
 For example, you define a `LimitRange` with this manifest:
 -->