From 6bffe16fec2d5121c925098d4a8a79536d41ff0d Mon Sep 17 00:00:00 2001
From: Sabrina Jess <sjess@redhat.com>
Date: Wed, 8 Nov 2023 10:44:18 -0500
Subject: [PATCH] fix

---
 modules/virt-enabling-volume-snapshot-boot-source.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/virt-enabling-volume-snapshot-boot-source.adoc b/modules/virt-enabling-volume-snapshot-boot-source.adoc
index 722a047611..faa8e91e92 100644
--- a/modules/virt-enabling-volume-snapshot-boot-source.adoc
+++ b/modules/virt-enabling-volume-snapshot-boot-source.adoc
@@ -25,7 +25,7 @@ Use volume snapshots on a storage profile that is proven to scale better when cl
 +
 [source,terminal,subs="attributes+"]
 ----
-$ oc edit storageprofile <storage_class> -oyaml
+$ oc edit storageprofile <storage_class>
 ----
 
 . Review the `dataImportCronSourceFormat` specification of the `StorageProfile` to confirm whether or not the VM is using PVC or volume snapshot by default.
@@ -49,7 +49,7 @@ spec:
 +
 [source,terminal,subs="attributes+"]
 ----
-$ oc get storageprofile <storage_class>
+$ oc get storageprofile <storage_class>  -oyaml
 ----
 
 . Confirm that the `dataImportCronSourceFormat` specification of the `StorageProfile` is set to 'snapshot', and that any `DataSource` objects that the `DataImportCron` points to now reference volume snapshots.