diff --git a/modules/installation-osp-creating-image.adoc b/modules/installation-osp-creating-image.adoc
index 36419f63ab54..53aea4f7dd68 100644
--- a/modules/installation-osp-creating-image.adoc
+++ b/modules/installation-osp-creating-image.adoc
@@ -6,8 +6,11 @@
 [id="installation-osp-creating-image_{context}"]
 = Creating the {op-system-first} image
 
+[role="_abstract"]
 The {product-title} installation program requires that a {op-system-first} image be present in the {rh-openstack-first} cluster. Retrieve the latest {op-system} image, then upload it using the {rh-openstack} CLI.
 
+After you upload the image to {rh-openstack}, it is usable in the installation process.
+
 .Prerequisites
 
 * The {rh-openstack} CLI is installed.
@@ -53,5 +56,17 @@ Depending on your {rh-openstack} environment, you might be able to upload the im
 +
 [WARNING]
 If the installation program finds multiple images with the same name, it chooses one of them at random. To avoid this behavior, create unique names for resources in {rh-openstack}.
++
+[NOTE]
+====
+The {op-system} ISO image supports booting in both UEFI and legacy BIOS modes. Instances that boot from the image use legacy BIOS firmware by default.
+====
 
-After you upload the image to {rh-openstack}, it is usable in the installation process.
+. Optional: If you use UEFI boot in your {rh-openstack} environment, you can set the `hw_firmware_type` property on the image by running the following command:
++
+[source,terminal]
+----
+$ openstack image set --property hw_firmware_type=uefi rhcos
+----
++
+Replace `rhcos` with your image name if it differs from the example.