Fix SB intro for Satellite

guides/common/modules/con_using-pxe-to-provision-hosts.adoc

@@ -47,11 +47,15 @@ In {Project} provisioning, the PXE loader option defines the DHCP `filename` opt
 SecureBoot PXE loaders enable a client to download the `shim.efi` bootstrap boot loader that then loads the signed `grubx64.efi`.
 Use the *Grub2 UEFI SecureBoot* PXE loader for PXE-boot provisioning or *Grub2 UEFI HTTPS SecureBoot* for HTTP-boot provisioning.
 
-By default, you can provision operating systems from the vendor of the operating system of your {ProjectServer} on Secure Boot enabled hosts.
-To provision operating systems on Secure Boot enabled hosts from different vendors, you have to provide signed shim and GRUB2 binaries provided by the vendor of your operating system.
 ifdef::satellite[]
+By default, you can provision the RHEL version of your {ProjectServer} on Secure Boot enabled hosts.
+To provision other versions of {RHEL}, you have to provide signed shim and GRUB2 binaries of those RHEL versions.
 For more information, see xref:configuring-{smart-proxy-context}-to-provision-rhel-on-Secure-Boot-enabled-hosts[].
 endif::[]
+ifndef::satellite[]
+By default, you can provision operating systems from the vendor of the operating system of your {ProjectServer} on Secure Boot enabled hosts.
+To provision operating systems on Secure Boot enabled hosts from different vendors, you have to provide signed shim and GRUB2 binaries provided by the vendor of your operating system.
+endif::[]
 ifndef::orcharhino,satellite[]
 For more information, see: