Merge pull request openshift#10162 from kalexand-rh/pr9927

Don't advice to modify default SCCs: text edits

Author: kalexand-rh

admin_guide/manage_scc.adoc

@@ -428,9 +428,11 @@ To provide additional capabilities:
 [[modify-cluster-default-behavior]]
 === Modify Cluster Default Behavior
 
-To modify your cluster so that it does not pre-allocate UIDs, allows containers
-to run as any user, but prevents privileged containers, grant access to the
-*anyuid* SCC for everyone:
+When you grant access to the *anyuid* SCC for everyone, your cluster:
+
+* Does not pre-allocate UIDs
+* Allows containers to run as any user
+* Prevents privileged containers
 
 ----
  $ oc adm policy add-scc-to-group anyuid system:authenticated
@@ -452,7 +454,7 @@ affects Kubernetes and {product-title} components, including the web console
 and integrated docker registry. Changes made with these SCCs can cause these
 components to stop functioning.
 
-Always prefer creating a custom SCC and target it to only specific users or
+Instead, create a custom SCC and target it to only specific users or
 groups. This way potential issues are confined to the affected users or groups
 and do not impact critical cluster components.
 ====
@@ -463,7 +465,7 @@ and do not impact critical cluster components.
 
 To relax the security in your cluster so that pods are allowed to use the
 `hostPath` volume plug-in without granting everyone access to more privileged
-SCCs such as *privileged*, *hostaccess*, or *hostmount-anyuid*, take the
+SCCs such as *privileged*, *hostaccess*, or *hostmount-anyuid*, perform the
 following actions:
 
 . xref:creating-new-security-context-constraints[Create a new SCC] named `hostpath`