diff --git a/modules/virt-creating-vm-instancetype.adoc b/modules/virt-creating-vm-instancetype.adoc
index 72122c1807..0ae7b2fcf0 100644
--- a/modules/virt-creating-vm-instancetype.adoc
+++ b/modules/virt-creating-vm-instancetype.adoc
@@ -22,7 +22,10 @@ endif::[]
 
 ifdef::virt-create-vms[]
 You can create a virtual machine (VM) from an instance type by using the {product-title} web console. You can also use the web console to create a VM by copying an existing snapshot or to clone a VM.
+
+You can create a VM from a list of available bootable volumes. You can add Linux- or Windows-based volumes to the list.
 endif::[]
+
 ifdef::static-key[]
 You can add a statically managed SSH key when you create a virtual machine (VM) from an instance type by using the {product-title} web console. The key is added to the VM as a cloud-init data source at first boot. This method does not affect cloud-init user data.
 endif::[]
@@ -42,6 +45,7 @@ endif::[]
 . In the web console, navigate to *Virtualization* -> *Catalog*.
 +
 The *InstanceTypes* tab opens by default.
+
 . Select either of the following options:
 * Select a suitable bootable volume from the list. If the list is truncated, click the *Show all* button to display the entire list.
 +
@@ -58,7 +62,7 @@ Logos of operating systems that are not available in the cluster are shown at th
 +
 In addition, there is a link to the *Create a Windows boot source* quick start. The same link appears in a popover if you hover the pointer over the question mark icon next to the _Select volume to boot from_ line.
 +
-Immediately after you install the environment or when the environment is disconnected, the list of volumes to boot from is empty. In that case, three operating system logos are displayed: Windows, {op-system-base}, and Linux. You can add a new volume that meets you requirements by clicking the *Add volume* button.
+Immediately after you install the environment or when the environment is disconnected, the list of volumes to boot from is empty. In that case, three operating system logos are displayed: Windows, {op-system-base}, and Linux. You can add a new volume that meets your requirements by clicking the *Add volume* button.
 
 ifdef::virt-create-vms[]
 . Click an instance type tile and select the resource size appropriate for your workload.
@@ -66,15 +70,37 @@ endif::[]
 ifdef::dynamic-key[]
 . Click the *Red Hat Enterprise Linux 9 VM* tile.
 endif::[]
-. If you have not already added a public SSH key to your project, click the edit icon beside *Authorized SSH key* in the *VirtualMachine details* section.
-. Select one of the following options:
+ifdef::virt-create-vms[]
+. Optional: Choose the virtual machine details, including the VM's name, that apply to the volume you are booting from:
+endif::[]
+ifdef::virt-create-vms[]
+** For a Linux-based volume, follow these steps to configure SSH:
+endif::[]
 
+.. If you have not already added a public SSH key to your project, click the edit icon beside *Authorized SSH key* in the *VirtualMachine details* section.
+.. Select one of the following options:
++
+--
 * *Use existing*: Select a secret from the secrets list.
-* *Add new*:
-.. Browse to the public SSH key file or paste the file in the key field.
-.. Enter the secret name.
-.. Optional: Select *Automatically apply this key to any new VirtualMachine you create in this project*.
+* *Add new*: Follow these steps:
+... Browse to the public SSH key file or paste the file in the key field.
+... Enter the secret name.
+... Optional: Select *Automatically apply this key to any new VirtualMachine you create in this project*.
+--
 .. Click *Save*.
+
+ifdef::virt-create-vms[]
+** For a Windows volume, follow either of these set of steps to configure sysprep options:
+*** If you have not already added sysprep options for the Windows volume, follow these steps:
+... Click the edit icon beside *Sysprep* in the *VirtualMachine details* section.
+... Add the *Autoattend.xml* answer file.
+... Add the *Unattend.xml* answer file.
+... Click *Save*.
+*** If you want to use existing sysprep options for the Windows volume, follow these steps:
+... Click *Attach existing sysprep*.
+... Enter the name of the existing sysprep *Unattend.xml* answer file.
+... Click *Save*.
+endif::[]
 ifdef::dynamic-key[]
 . Set *Dynamic SSH key injection* in the *VirtualMachine details* section to on.
 endif::[]