Merge pull request #45122 from stevsmit/GH-Issue-Fix

Fixes minor issues in the security pod scanning CSO file

Author: stevsmit

modules/security-pod-scan-cso.adoc

@@ -26,8 +26,8 @@ to go to the Create Operator Subscription page.
 
 . Select *Install*. The *Container Security* Operator appears after a few moments on the *Installed Operators* screen.
 
-. Optional: You can add custom certificates to the CSO. In this example, create a certificate
-named `quay.crt` in the current directory. Then run the following command to add the cert to the CSO:
+. Optional: You can add custom certificates to the {rhq-cso}. In this example, create a certificate
+named `quay.crt` in the current directory. Then run the following command to add the cert to the {rhq-cso}:
 +
 [source,terminal]
 ----
@@ -49,7 +49,7 @@ registry that the container came
 from, where you can see information about the vulnerability. The following
 figure shows an example of detected vulnerabilities from a Quay.io registry:
 +
-image:cso-registry-vulnerable.png[The CSO points you to a registry containing the vulnerable image]
+image:cso-registry-vulnerable.png[The {rhq-cso} points you to a registry containing the vulnerable image]
 +
 * Select the namespaces link to go to the *ImageManifestVuln* screen,
 where you can see the name of the selected image

security/pod-vulnerability-scan.adoc

@@ -8,7 +8,7 @@ toc::[]
 
 Using the {rhq-cso}, you can access vulnerability
 scan results from the {product-title} web console for container images
-used in active pods on the cluster. The CSO:
+used in active pods on the cluster. The {rhq-cso}:
 
 * Watches containers associated with pods on all or specified namespaces
 * Queries the container registry where the containers came from for
@@ -18,7 +18,7 @@ link:https://quay.io[Quay.io] or a
 link:https://access.redhat.com/products/red-hat-quay[Red Hat Quay] registry with Clair scanning)
 * Exposes vulnerabilities via the `ImageManifestVuln` object in the Kubernetes API
 
-Using the instructions here, the CSO is installed in the `openshift-operators`
+Using the instructions here, the {rhq-cso} is installed in the `openshift-operators`
 namespace, so it is available to all namespaces on your {product-title} cluster.
 
 //