Merge pull request #79793 from bergerhoffer/OSDOCS-11409

OSDOCS#11409: Adding more detail for creating custom SCCs

Author: bergerhoffer

modules/security-context-constraints-command-reference.adoc

@@ -2,10 +2,11 @@
 //
 // * authentication/managing-security-context-constraints.adoc
 
+:_mod-docs-content-type: REFERENCE
 [id="security-context-constraints-command-reference_{context}"]
 = Reference of security context constraints commands
 
-You can manage security context constraints (SCCs) in your instance as normal API objects using the OpenShift CLI (`oc`).
+You can manage security context constraints (SCCs) in your instance as normal API objects by using the OpenShift CLI (`oc`).
 
 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
 [NOTE]
@@ -103,35 +104,39 @@ the default SCCs.
 //other than priority, users, groups, labels, and annotations.
 ====
 
-[id="deleting-security-context-constraints_{context}"]
-== Deleting security context constraints
+[id="updating-security-context-constraints_{context}"]
+== Updating security context constraints
 
-To delete an SCC:
+If your custom SCC no longer satisfies your application workloads requirements, you can update your SCC by using the OpenShift CLI (`oc`).
+
+To update an existing SCC:
 
 [source,terminal]
 ----
-$ oc delete scc <scc_name>
+$ oc edit scc <scc_name>
 ----
 
-[NOTE]
+[IMPORTANT]
 ====
-If you delete a default SCC, it will regenerate when you restart the cluster.
+To preserve customized SCCs during upgrades, do not edit settings on
+the default SCCs.
+//other than priority, users, groups, labels, and annotations.
 ====
 
-[id="updating-security-context-constraints_{context}"]
-== Updating security context constraints
+[id="deleting-security-context-constraints_{context}"]
+== Deleting security context constraints
 
-To update an existing SCC:
+If you no longer require your custom SCC, you can delete the SCC by using the OpenShift CLI (`oc`).
+
+To delete an SCC:
 
 [source,terminal]
 ----
-$ oc edit scc <scc_name>
+$ oc delete scc <scc_name>
 ----
 
-[NOTE]
+[IMPORTANT]
 ====
-To preserve customized SCCs during upgrades, do not edit settings on
-the default SCCs.
-//other than priority, users, groups, labels, and annotations.
+Do not delete default SCCs. If you delete a default SCC, it is regenerated by the Cluster Version Operator.
 ====
 endif::openshift-enterprise,openshift-webscale,openshift-origin[]

modules/security-context-constraints-creating.adoc

@@ -11,7 +11,7 @@ ifdef::openshift-dedicated[]
 = Creating security context constraints for CCS clusters
 endif::[]
 
-You can create security context constraints (SCCs) by using the OpenShift CLI (`oc`).
+If the default security context constraints (SCCs) do not satisfy your application workload requirements, you can create a custom SCC by using the OpenShift CLI (`oc`).
 
 [IMPORTANT]
 ====