Merge pull request #39271 from Zhuzhenghao/en/resource-bin-package

Tweak page style for resource-bin-packing.md

Author: k8s-ci-robot

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

@@ -10,7 +10,7 @@ weight: 80
 
 <!-- overview -->
 
-In the [scheduling-plugin](/docs/reference/scheduling/config/#scheduling-plugins)  `NodeResourcesFit` of kube-scheduler, there are two 
+In the [scheduling-plugin](/docs/reference/scheduling/config/#scheduling-plugins) `NodeResourcesFit` of kube-scheduler, there are two
 scoring strategies that support the bin packing of resources: `MostAllocated` and `RequestedToCapacityRatio`.
 
 <!-- body -->
@@ -42,7 +42,7 @@ profiles:
     name: NodeResourcesFit
 ```
 
-To learn more about other parameters and their default configuration, see the API documentation for 
+To learn more about other parameters and their default configuration, see the API documentation for
 [`NodeResourcesFitArgs`](/docs/reference/config-api/kube-scheduler-config.v1beta3/#kubescheduler-config-k8s-io-v1beta3-NodeResourcesFitArgs).
 
 ## Enabling bin packing using RequestedToCapacityRatio
@@ -55,10 +55,10 @@ configured function of the allocated resources. The behavior of the `RequestedTo
 the `NodeResourcesFit` score function can be controlled by the
 [scoringStrategy](/docs/reference/config-api/kube-scheduler-config.v1beta3/#kubescheduler-config-k8s-io-v1beta3-ScoringStrategy) field.
 Within the `scoringStrategy` field, you can configure two parameters: `requestedToCapacityRatio` and
-`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` 
+`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.
 
 Below is an example configuration that sets
@@ -87,11 +87,11 @@ profiles:
     name: NodeResourcesFit
 ```
 
-Referencing the `KubeSchedulerConfiguration` file with the kube-scheduler 
-flag `--config=/path/to/config/file` will pass the configuration to the 
+Referencing the `KubeSchedulerConfiguration` file with the kube-scheduler
+flag `--config=/path/to/config/file` will pass the configuration to the
 scheduler.
 
-To learn more about other parameters and their default configuration, see the API documentation for 
+To learn more about other parameters and their default configuration, see the API documentation for
 [`NodeResourcesFitArgs`](/docs/reference/config-api/kube-scheduler-config.v1beta3/#kubescheduler-config-k8s-io-v1beta3-NodeResourcesFitArgs).
 
 ### Tuning the score function
@@ -100,10 +100,10 @@ To learn more about other parameters and their default configuration, see the AP
 
 ```yaml
 shape:
- - utilization: 0
-   score: 0
- - utilization: 100
-   score: 10
+  - utilization: 0
+    score: 0
+  - utilization: 100
+    score: 10
 ```
 
 The above arguments give the node a `score` of 0 if `utilization` is 0% and 10 for
@@ -120,15 +120,15 @@ shape:
 
 `resources` is an optional parameter which defaults to:
 
-``` yaml
+```yaml
 resources:
   - name: cpu
     weight: 1
   - name: memory
     weight: 1
 ```
 
-It can be used to add extended resources as follows: 
+It can be used to add extended resources as follows:
 
 ```yaml
 resources:
@@ -188,8 +188,8 @@ intel.com/foo  = resourceScoringFunction((2+1),4)
                = (100 - ((4-3)*100/4)
                = (100 - 25)
                = 75                       # requested + used = 75% * available
-               = rawScoringFunction(75) 
-               = 7                        # floor(75/10) 
+               = rawScoringFunction(75)
+               = 7                        # floor(75/10)
 
 memory         = resourceScoringFunction((256+256),1024)
                = (100 -((1024-512)*100/1024))
@@ -251,4 +251,3 @@ NodeScore   =  (5 * 5) + (7 * 1) + (10 * 3) / (5 + 1 + 3)
 
 - Read more about the [scheduling framework](/docs/concepts/scheduling-eviction/scheduling-framework/)
 - Read more about [scheduler configuration](/docs/reference/scheduling/config/)
-