From 589f989c4cbf38e6ca013cca2cd412af5cc4f2de Mon Sep 17 00:00:00 2001
From: GroceryBoyJr <75502996+GroceryBoyJr@users.noreply.github.com>
Date: Fri, 28 Feb 2025 06:12:23 -0500
Subject: [PATCH] OCPBUGS-49694:oc events command needs to be updated

---
 modules/compliance-crd-advanced-compliance-scan.adoc | 4 ++--
 modules/compliance-crd-compliance-suite.adoc         | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/modules/compliance-crd-advanced-compliance-scan.adoc b/modules/compliance-crd-advanced-compliance-scan.adoc
index 20e41665c218..d58320611276 100644
--- a/modules/compliance-crd-advanced-compliance-scan.adoc
+++ b/modules/compliance-crd-advanced-compliance-scan.adoc
@@ -13,7 +13,7 @@ The Compliance Operator includes options for advanced users for debugging or int
 apiVersion: compliance.openshift.io/v1alpha1
 kind: ComplianceScan
 metadata:
-  name: <name of the scan>
+  name: <name_of_the_compliance_scan>
 spec:
   scanType: Node <1>
   profile: xccdf_org.ssgproject.content_profile_moderate <2>
@@ -55,5 +55,5 @@ You can programmatically fetch the `ComplianceScans` events. To generate events
 
 [source,terminal]
 ----
-oc get events --field-selector involvedObject.kind=ComplianceScan,involvedObject.name=<name of the suite>
+oc get events --field-selector involvedObject.kind=ComplianceScan,involvedObject.name=<name_of_the_compliance_scan>
 ----
diff --git a/modules/compliance-crd-compliance-suite.adoc b/modules/compliance-crd-compliance-suite.adoc
index 33c089441f84..0e736880b15a 100644
--- a/modules/compliance-crd-compliance-suite.adoc
+++ b/modules/compliance-crd-compliance-suite.adoc
@@ -15,7 +15,7 @@ For `Node` type scans, you should map the scan to the `MachineConfigPool`, since
 apiVersion: compliance.openshift.io/v1alpha1
 kind: ComplianceSuite
 metadata:
-  name: <name of the scan>
+  name: <name_of_the_suite>
 spec:
   autoApplyRemediations: false <1>
   schedule: "0 1 * * *" <2>