Merge pull request #35513 from mgarrellRH/CNV12576

CNV 12576: Updating text about EFI mode and Secure Boot

Author: bergerhoffer

modules/virt-about-efi-mode-for-vms.adoc

@@ -8,9 +8,3 @@
 Extensible Firmware Interface (EFI), like legacy BIOS, initializes hardware components and operating system image files when a computer starts. EFI supports more modern features and customization options than BIOS, enabling faster boot times.
 
 It stores all the information about initialization and startup in a file with a `.efi` extension, which is stored on a special partition called EFI System Partition (ESP). The ESP also contains the boot loader programs for the operating system that is installed on the computer.
-
-
-[NOTE]
-====
-{VirtProductName} only supports a virtual machine (VM) with Secure Boot when using EFI mode. If Secure Boot is not enabled, the VM crashes repeatedly. However, the VM might not support Secure Boot. Before you boot a VM, verify that it supports Secure Boot by checking the VM settings.
-====

modules/virt-booting-efi-mode.adoc

@@ -42,7 +42,7 @@ You can configure a virtual machine to boot in EFI mode by editing the VM or VMI
 ...
 ----
 <1> {VirtProductName} requires System Management Mode (`SMM`) to be enabled for Secure Boot in EFI mode to occur.
-<2> {VirtProductName} only supports a virtual machine (VM) with Secure Boot when using EFI mode. If Secure Boot is not enabled, the VM crashes repeatedly. However, the VM might not support Secure Boot. Before you boot a VM, verify that it supports Secure Boot by checking the VM settings.
+<2> {VirtProductName} supports a VM with or without Secure Boot when using EFI mode. If Secure Boot is enabled, then EFI mode is required. However, EFI mode can be enabled without using Secure Boot.
 
 . Apply the manifest to your cluster by running the following command:
 +