Merge pull request #47352 from my-git9/pp-13274

[zh-cn] sync network-plugins labels

content/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md

@@ -16,12 +16,15 @@ weight: 10
 <!-- overview -->
 
 <!-- 
-Kubernetes {{< skew currentVersion >}} supports [Container Network Interface](https://github.com/containernetworking/cni)
+Kubernetes (version 1.3 through to the latest {{< skew latestVersion >}}, and likely onwards) lets you use
+[Container Network Interface](https://github.com/containernetworking/cni)
 (CNI) plugins for cluster networking. You must use a CNI plugin that is compatible with your
 cluster and that suits your needs. Different plugins are available (both open- and closed- source)
 in the wider Kubernetes ecosystem.
 -->
-Kubernetes {{< skew currentVersion >}} 支持用于集群联网的[容器网络接口](https://github.com/containernetworking/cni)（CNI）插件。
+Kubernetes（1.3 版本至最新 {{< skew latestVersion >}}，并可能包括未来版本）
+允许你使用[容器网络接口](https://github.com/containernetworking/cni)（CNI）
+插件来完成集群联网。
 你必须使用和你的集群相兼容并且满足你的需求的 CNI 插件。
 在更广泛的 Kubernetes 生态系统中你可以使用不同的插件（开源和闭源）。
 

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

@@ -244,11 +244,11 @@ excluding `frontend` using the comma operator: `environment=production,tier!=fro
 
 <!--
 One usage scenario for equality-based label requirement is for Pods to specify
-node selection criteria. For example, the sample Pod below selects nodes with
-the label "`accelerator=nvidia-tesla-p100`".
+node selection criteria. For example, the sample Pod below selects nodes where
+the  `accelerator` label exists and is set to `nvidia-tesla-p100`.
 -->
 基于等值的标签要求的一种使用场景是 Pod 要指定节点选择标准。
-例如，下面的示例 Pod 选择带有标签 "`accelerator=nvidia-tesla-p100`"。
+例如，下面的示例 Pod 选择存在 `accelerator` 标签且值为 `nvidia-tesla-p100` 的节点。
 
 ```yaml
 apiVersion: v1