Merge pull request openshift#89207 from mburke5678/84687-follow-up

Created Cri-O default capabilities section follow up

Author: mburke5678

modules/create-crio-default-capabilities.adoc

@@ -6,7 +6,7 @@
 [id="create-crio-default-capabilities_{context}"]
 = Creating a drop-in file for the default CRI-O capabilities
 
-You can change some of the settings associated with the {product-title} CRI-O runtime for the nodes associated with a specific machine config pool (MCP). By using a controller custom resource (CR), you set the configuration values and add a label to match the MCP. The MCO then rebuilds the `crio.conf` and `default.conf` configuration files on the associated nodes with the updated values.
+You can change some of the settings associated with the {product-title} CRI-O runtime for the nodes associated with a specific machine config pool (MCP). By using a controller custom resource (CR), you set the configuration values and add a label to match the MCP. The Machine Config Operator (MCO) then rebuilds the `crio.conf` and `default.conf` configuration files on the associated nodes with the updated values.
 
 Earlier versions of {product-title} included specific machine configs by default. If you updated to a later version of {product-title}, those machine configs were retained to ensure that clusters running on the same {product-title} version have the same machine configs.
 
@@ -37,6 +37,10 @@ ctr-level    5m45s
 [source,terminal]
 ----
 $ cat /proc/1/status | grep Cap
+----
+
+[source,terminal]
+----
 $ capsh --decode=<decode_CapBnd_value> <1>
 ----
 <1> Replace `<decode_CapBnd_value>` with the specific value you want to decode.