apply sembr lint

Signed-off-by: Heba Elayoty <heelayot@microsoft.com>

Author: helayoty

content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md

@@ -89,18 +89,23 @@ You can also use numeric comparison operators for threshold-based matching:
 * the `operator` is `Gt` (greater than) and the toleration value is greater than the taint value, or
 * the `operator` is `Lt` (less than) and the toleration value is less than the taint value.
 
-For numeric operators, both the toleration and taint values must be valid integers. If either value cannot be parsed as an integer, the toleration does not match.
+For numeric operators, both the toleration and taint values must be valid integers.
+If either value cannot be parsed as an integer, the toleration does not match.
 
 {{< note >}}
-When you create a Pod that uses `Gt` or `Lt` tolerations operators, the API server validates that the toleration values are valid integers. Taint values on nodes are not validated at node registration time. If a node has a non-numeric taint value (for example, `servicelevel.organization.example/agreed-service-level=high:NoSchedule`), pods with numeric comparison
-operators will not match that taint and cannot schedule on that node.
+When you create a Pod that uses `Gt` or `Lt` tolerations operators, the API server validates that
+the toleration values are valid integers. Taint values on nodes are not validated at node
+registration time. If a node has a non-numeric taint value (for example,
+`servicelevel.organization.example/agreed-service-level=high:NoSchedule`),
+pods with numeric comparison operators will not match that taint and cannot schedule on that node.
 {{< /note >}}
 
 {{< note >}}
 
 There are two special cases:
 
-If the `key` is empty, then the `operator` must be `Exists`, which matches all keys and values. Note that the `effect` still needs to be matched at the same time.
+If the `key` is empty, then the `operator` must be `Exists`, which matches all keys and values.
+Note that the `effect` still needs to be matched at the same time.
 
 An empty `effect` matches all effects with key `key1`.
 
@@ -192,7 +197,9 @@ taint is removed before that time, the pod will not be evicted.
 
 {{< feature-state feature_gate_name="TaintTolerationComparisonOperators" >}}
 
-In addition to the `Equal` and `Exists` operators, you can use numeric comparison operators (`Gt` and `Lt`) to match taints with integer values. This is useful for threshold-based scheduling scenarios, such as matching nodes based on reliability levels or SLA requirements.
+In addition to the `Equal` and `Exists` operators, you can use numeric comparison operators
+(`Gt` and `Lt`) to match taints with integer values. This is useful for threshold-based scheduling
+scenarios, such as matching nodes based on reliability levels or SLA requirements.
 
 For example, if nodes are tainted with a value representing a service level agreement (SLA):
 
@@ -204,9 +211,10 @@ A pod can tolerate nodes with SLA greater than 900:
 
 {{% code_sample file="pods/pod-with-numeric-toleration.yaml" %}}
 
-This toleration matches the taint on `node1` because `900 < 950` (the toleration value is less than the taint value for the `Gt` operator).
-
-Similarly, you can use the `Lt` operator to match taints where the toleration value is greater than the taint value:
+This toleration matches the taint on `node1` because `900 < 950` (the toleration value
+is less than the taint value for the `Gt` operator).
+Similarly, you can use the `Lt` operator to match taints where the toleration value is
+greater than the taint value:
 
 ```yaml
 tolerations:
@@ -219,7 +227,8 @@ tolerations:
 {{< note >}}
 When using numeric comparison operators:
 
-* Both the toleration and taint values must be valid signed 64-bit integers (zero leading numbers (e.g., "0550") are not allowed).
+* Both the toleration and taint values must be valid signed 64-bit integers
+  (zero leading numbers (e.g., "0550") are not allowed).
 * If a value cannot be parsed as an integer, the toleration does not match.
 * Numeric operators work with all taint effects: `NoSchedule`, `PreferNoSchedule`, and `NoExecute`.
 {{< /note >}}