Merge pull request #39896 from mburke5678/fix-requiredDropCapabilities-all

Fixed problems with `BZ-2025586:Documentation update to reflect changes for capabilities` PR

Author: mburke5678

modules/nodes-pods-autoscaling-about.adoc

@@ -65,7 +65,7 @@ and ensure that your application meets these requirements before using
 memory-based autoscaling.
 ====
 
-The following example shows autoscaling for the `image-registry` `Deployment` object. The initial deployment requires 3 pods. The HPA object increases the minimum to 5. If CPU usage on the pods reaches 75%, the pods will increase to 7:
+The following example shows autoscaling for the `image-registry` `Deployment` object. The initial deployment requires 3 pods. The HPA object increases the minimum to 5. If CPU usage on the pods reaches 75%, the pods increase to 7:
 
 [source,terminal]
 ----

modules/security-context-constraints-about.adoc

@@ -166,7 +166,7 @@ CRI-O has the following default list of capabilities that are allowed for each c
 * `NET_BIND_SERVICE`
 * `KILL`
 
-The containers use the capabilities from this default list, but pod manifest authors can alter the list by requesting additional capabilities or removing some of the default behaviors. Use the `allowedCapabilities`, `defaultAddCapabilities`, and `requiredDropCapabilities` parameters to control such requests from the pods and to specify which capabilities can be requested, which ones must be added to each container, and which ones must be forbidden, or dropped, from each container.
+The containers use the capabilities from this default list, but pod manifest authors can alter the list by requesting additional capabilities or removing some of the default behaviors. Use the `allowedCapabilities`, `defaultAddCapabilities`, and `requiredDropCapabilities` parameters to control such requests from the pods. With these parameters you can specify which capabilities can be requested, which ones must be added to each container, and which ones must be forbidden, or dropped, from each container.
 
 [NOTE]
 ====

modules/security-context-constraints-example.adoc

@@ -65,7 +65,8 @@ allows any capabilities.
 <3> The `FSGroup` strategy, which dictates the allowable values for the
 security context.
 <4> The groups that can access this SCC.
-<5> A list of capabilities to drop from a pod. Or, specify `ALL` 
+<5> A list of capabilities to drop from a pod. Or, specify `ALL` to drop all
+capabilities.
 <6> The `runAsUser` strategy type, which dictates the allowable values for the
 Security Context.
 //could use the available strategies