Merge pull request #45554 from asa3311/sync-zh-106

[zh] sync dynamic-resource-allocation resource-bin-packing scheduler-perf-tuning

Author: k8s-ci-robot

content/zh-cn/docs/concepts/scheduling-eviction/dynamic-resource-allocation.md

@@ -63,14 +63,14 @@ ResourceClass
   driver.
 
 ResourceClaim
-: Defines a particular resource instances that is required by a
+: Defines a particular resource instance that is required by a
   workload. Created by a user (lifecycle managed manually, can be shared
   between different Pods) or for individual Pods by the control plane based on
   a ResourceClaimTemplate (automatic lifecycle, typically used by just one
   Pod).
 
 ResourceClaimTemplate
-: Defines the spec and some meta data for creating
+: Defines the spec and some metadata for creating
   ResourceClaims. Created by a user when deploying a workload.
 
 PodSchedulingContext

content/zh-cn/docs/concepts/scheduling-eviction/resource-bin-packing.md

@@ -84,8 +84,8 @@ Within the `scoringStrategy` field, you can configure two parameters: `requested
 `resources`. The `shape` in the `requestedToCapacityRatio`
 parameter allows the user to tune the function as least requested or most
 requested based on `utilization` and `score` values. The `resources` parameter
-consists of `name` of the resource to be considered during scoring and `weight`
-specify the weight of each resource.
+comprises both the `name` of the resource to be considered during scoring and
+its corresponding `weight`, which specifies the weight of each resource.
 -->
 ## 使用 RequestedToCapacityRatio 策略来启用资源装箱 {#enabling-bin-packing-using-requestedtocapacityratio}
 
@@ -97,7 +97,8 @@ specify the weight of each resource.
 字段来控制。在 `scoringStrategy` 字段中，你可以配置两个参数：
 `requestedToCapacityRatio` 和 `resources`。`requestedToCapacityRatio` 参数中的 `shape`
 设置使得用户能够调整函数的算法，基于 `utilization` 和 `score` 值计算最少请求或最多请求。
-`resources` 参数中包含计分过程中需要考虑的资源的 `name`，以及用来设置每种资源权重的 `weight`。
+`resources` 参数中包含计分过程中需要考虑的资源的 `name`，以及对应的 `weight`，
+后者指定了每个资源的权重。
 
 <!--
 Below is an example configuration that sets

content/zh-cn/docs/concepts/scheduling-eviction/scheduler-perf-tuning.md

@@ -150,7 +150,7 @@ for a 5000-node cluster. The lower bound for the automatic value is 5%.
 下取 50%，在 5000-节点的集群下取 10%。这个自动设置的参数的最低值是 5%。
 
 <!--
-This means that, the kube-scheduler always scores at least 5% of your cluster no
+This means that the kube-scheduler always scores at least 5% of your cluster no
 matter how large the cluster is, unless you have explicitly set
 `percentageOfNodesToScore` to be smaller than 5.
 -->