BZ2110179: Update UI procedures for top-level Virt

modules/virt-about-vm-templates.adoc

@@ -6,9 +6,9 @@
 [id="virt-understanding-vm-templates-web_{context}"]
 = About virtual machine templates
 
-Preconfigured Red Hat virtual machine templates are listed in the *Templates* tab within the *Virtualization* page. These templates are available for different versions of Red Hat Enterprise Linux, Fedora, Microsoft Windows 10, and Microsoft Windows Servers. Each Red Hat virtual machine template is preconfigured with the operating system image, default settings for the operating system, flavor (CPU and memory), and workload type (server).
+Preconfigured Red Hat virtual machine templates are listed in the *Virtualization* -> *Templates* page. These templates are available for different versions of Red Hat Enterprise Linux, Fedora, Microsoft Windows 10, and Microsoft Windows Servers. Each Red Hat virtual machine template is preconfigured with the operating system image, default settings for the operating system, flavor (CPU and memory), and workload type (server).
 
-The *Templates* tab displays four types of virtual machine templates:
+The *Templates* page displays four types of virtual machine templates:
 
 * *Red Hat Supported* templates are fully supported by Red Hat.
 * *User Supported* templates are *Red Hat Supported* templates that were cloned and created by users.
@@ -19,7 +19,7 @@ You can use the filters in the template *Catalog* to sort the templates by attri
 
 [NOTE]
 ====
-In the *Templates* tab, you cannot edit or delete *Red Hat Supported* or *Red Hat Provided* templates. You can only edit or delete custom virtual machine templates that were created by users.
+You cannot edit or delete *Red Hat Supported* or *Red Hat Provided* templates. You can only edit or delete custom virtual machine templates that were created by users.
 ====
 
 Using a Red Hat template is convenient because the template is already preconfigured. When you select a Red Hat template to create your own custom template, the *Create Virtual Machine Template* wizard prompts you to add a boot source if a boot source was not added previously. Then, you can either save your custom template or continue to customize it and save it.

modules/virt-add-boot-order-web.adoc

@@ -11,11 +11,9 @@ Add items to a boot order list by using the web console.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
-
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
 . Click the *Details* tab.
 

modules/virt-add-disk-to-vm.adoc

@@ -9,15 +9,15 @@
 ifeval::["{context}" == "virt-edit-vms"]
 :virt-vm:
 :object: virtual machine
-:object-gui: Virtual Machines
-:object-vm-overview: Virtual Machine Overview
+:object-gui: VirtualMachines
+:object-vm-overview: VirtualMachine details
 endif::[]
 
 ifeval::["{context}" == "virt-editing-vm-template"]
 :virt-vm-template:
 :object: virtual machine template
 :object-gui: Templates
-:object-vm-overview: VM Template Details
+:object-vm-overview: Template details
 endif::[]
 
 :_content-type: PROCEDURE
@@ -29,19 +29,17 @@ Use this procedure to add a virtual disk to a {object}.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *{object-gui}* tab.
+. Click *Virtualization* -> *{object-gui}* from the side menu.
 
 . Select a {object} to open the *{object-vm-overview}* screen.
 
-. Click the *Disks* tab.
+. Click the *Disks* tab and then click *Add disk*.
 
-. In the *Add Disk* window, specify the *Source*, *Name*, *Size*, *Type*, *Interface*, and *Storage Class*.
+. In the *Add disk* window, specify the *Source*, *Name*, *Size*, *Type*, *Interface*, and *Storage Class*.
 
-.. Advanced: You can enable preallocation if you use a blank disk source and require maximum write performance when creating data volumes. To do so, select the *Enable preallocation* checkbox.
+.. Optional: You can enable preallocation if you use a blank disk source and require maximum write performance when creating data volumes. To do so, select the *Enable preallocation* checkbox.
 
-.. Optional: In the *Advanced* list, specify the *Volume Mode* and *Access Mode* for the virtual disk. If you do not specify these parameters, the system uses the default values from the `kubevirt-storage-class-defaults` config map.
+.. Optional: You can clear *Apply optimized StorageProfile settings* to change the *Volume Mode* and *Access Mode* for the virtual disk. If you do not specify these parameters, the system uses the default values from the `kubevirt-storage-class-defaults` config map.
 
 . Click *Add*.
 

modules/virt-add-nic-to-vm.adoc

@@ -6,15 +6,15 @@
 ifeval::["{context}" == "virt-edit-vms"]
 :virt-vm:
 :object: virtual machine
-:object-gui: Virtual Machines
-:object-vm-overview: Virtual Machine Overview
+:object-gui: VirtualMachines
+:object-vm-overview: VirtualMachine details
 endif::[]
 
 ifeval::["{context}" == "virt-editing-vm-template"]
 :virt-vm-template:
 :object: virtual machine template
 :object-gui: Templates
-:object-vm-overview: VM Template Details
+:object-vm-overview: Template details
 endif::[]
 
 :_content-type: PROCEDURE
@@ -26,9 +26,7 @@ Use this procedure to add a network interface to a {object}.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *{object-gui}* tab.
+. Click *Virtualization* -> *{object-gui}* from the side menu.
 
 . Select a {object} to open the *{object-vm-overview}* screen.
 

modules/virt-adding-a-boot-source-web.adoc

@@ -6,14 +6,14 @@
 [id="virt-adding-a-boot-source-web_{context}"]
 = Adding a boot source for a virtual machine template
 
-A boot source can be configured for any virtual machine template that you want to use for creating virtual machines or custom templates. When virtual machine templates are configured with a boot source, they are labeled *Available* in the *Templates* tab. After you add a boot source to a template, you can create a new virtual machine from the template.
+A boot source can be configured for any virtual machine template that you want to use for creating virtual machines or custom templates. When virtual machine templates are configured with a boot source, they are labeled *Available* on the *Templates* page. After you add a boot source to a template, you can create a new virtual machine from the template.
 
 There are four methods for selecting and adding a boot source in the web console:
 
 * *Upload local file (creates PVC)*
-* *Import via URL (creates PVC)*
-* *Clone existing PVC (creates PVC)*
-* *Import via Registry (creates PVC)*
+* *URL (creates PVC)*
+* *Clone (creates PVC)*
+* *Registry (creates PVC)*
 
 .Prerequisites
 * To add a boot source, you must be logged in as a user with the `os-images.kubevirt.io:edit` RBAC role or as an administrator. You do not need special privileges to create a virtual machine from a template with a boot source added.
@@ -28,19 +28,17 @@ There are four methods for selecting and adding a boot source in the web console
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
+. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
 
-. Click the *Templates* tab.
+. Click *Add source* for the template that you want to configure.
 
-. Identify the virtual machine template for which you want to configure a boot source and click *Add source*.
-
-. In the *Add boot source to template* window, click *Select boot source*, select a method for creating a persistent volume claim (PVC): *Upload local file*, *Import via URL*, *Clone existing PVC*, or *Import via Registry*.
+. In the *Add boot source to template* window, click *Select boot source*, select a method for creating a persistent volume claim (PVC): *Upload local file*, *URL*, *Clone*, or *Registry*.
 
 . Optional: Click *This is a CD-ROM boot source* to mount a CD-ROM and use it to install the operating system on to an empty disk. The additional empty disk is automatically created and mounted by {VirtProductName}. If the additional disk is not needed, you can remove it when you create the virtual machine.
 
 . Enter a value for *Persistent Volume Claim size* to specify the PVC size that is adequate for the uncompressed image and any additional space that is required.
 
-.. Optional: Enter a name for *Source provider* to associate the name with this template.
+.. Optional: Enter a name for *Boot source* to associate the name with this template.
 
 .. Optional: *Advanced Storage settings*: Click *Storage class* and select the storage class that is used to create the disk. Typically, this storage class is the default storage class that is created for use by all PVCs.
 +
@@ -65,4 +63,4 @@ Provided boot sources are updated automatically to the latest version of the ope
 
 .. Click *Save and clone* if you cloned an existing PVC.
 
-Your custom virtual machine template with a boot source is listed in the *Templates* tab, and you can create virtual machines by using this template.
+Your custom virtual machine template with a boot source is listed in the *Templates* page, and you can create virtual machines by using this template.

modules/virt-adding-secret-configmap-service-account-to-vm.adoc

@@ -7,7 +7,11 @@
 
 = Adding a secret, config map, or service account to a virtual machine
 
-Add a secret, config map, or service account to a virtual machine by using the {product-title} web console.
+You add a secret, config map, or service account to a virtual machine by using the {product-title} web console.
+
+These resources are added to the virtual machine as disks. You then mount the secret, config map, or service account as you would mount any other disk.
+
+If the virtual machine is running, changes will not take effect until you restart the virtual machine. The newly added resources are marked as pending changes for both the *Environment* and *Disks* tab in the *Pending Changes* banner at the top of the page.
 
 .Prerequisites
 
@@ -15,42 +19,22 @@ Add a secret, config map, or service account to a virtual machine by using the {
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
+. In the *Environment* tab, click *Add Config Map, Secret or Service Account*.
 
-. Click the *Environment* tab.
+. Click *Select a resource* and select a resource from the list. A six character serial number is automatically generated for the selected resource.
 
-. Click *Select a resource* and select a secret, config map, or service account from the list. A six character serial number is automatically
-generated for the selected resource.
+. Optional: Click *Reload* to revert the environment to its last saved state.
 
 . Click *Save*.
 
-. Optional. Add another object by clicking *Add Config Map, Secret or Service Account*.
-
-[NOTE]
-====
-.. You can reset the form to the last saved state by clicking *Reload*.
-
-.. The *Environment* resources are added to the virtual machine as disks. You can mount the secret, config map, or service account as you would mount any other disk.
-
-.. If the virtual machine is running, changes will not take effect until you restart the virtual machine. The newly added resources are marked as pending changes
-for both the *Environment* and *Disks* tab in the *Pending Changes* banner at the top of the page.
-
-====
-
 .Verification
 
-. From the *Virtual Machine Overview* page, click the *Disks* tab.
+. On the *VirtualMachine details* page, click the *Disks* tab and verify that the secret, config map, or service account is included in the list of disks.
 
-. Check to ensure that the secret, config map, or service account is included in the list of disks.
-
-. Optional. Choose the appropriate method to apply your changes:
-
-.. If the virtual machine is running, restart the virtual machine by clicking *Actions* -> *Restart Virtual Machine*.
-
-.. If the virtual machine is stopped, start the virtual machine by clicking *Actions* -> *Start Virtual Machine*.
+. Restart the virtual machine by clicking *Actions* -> *Restart*.
 
 You can now mount the secret, config map, or service account as you would mount any other disk.

modules/virt-cancelling-vm-migration-web.adoc

@@ -6,21 +6,16 @@
 [id="virt-cancelling-vm-migration-web_{context}"]
 = Cancelling live migration of a virtual machine instance in the web console
 
-You can cancel a live migration of the virtual machine instance using the
-Options menu {kebab} found on each virtual machine in the
-*Virtualization* -> *Virtual Machines* tab, or from the *Actions* menu
-available on all tabs in the *Virtual Machine Overview* screen.
+You can cancel a live migration of the virtual machine instance using the Options menu {kebab} found on each virtual machine on the *VirtualMachines* page or from the *Actions* menu on the *VirtualMachine details* page.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. You can cancel the migration from this screen, which makes it easier to
-perform actions on multiple virtual machines, or from the
-*Virtual Machine Overview* screen where you can view comprehensive details
-of the selected virtual machine:
-** Click the Options menu {kebab} at the end of virtual machine and select
-*Cancel Virtual Machine Migration*.
-** Select a virtual machine name to open the *Virtual Machine Overview*
-screen and click *Actions* -> *Cancel Virtual Machine Migration*.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
+
+. You can cancel the migration from this screen, which makes it easier to perform actions on multiple virtual machines, or from the
+*VirtualMachine details* page where you can view comprehensive details of the selected virtual machine:
+
+* Click the Options menu {kebab} at the end of virtual machine and select *Cancel Virtual Machine Migration*.
+* Select a virtual machine name to open the *VirtualMachine details* page and click *Actions* -> *Cancel Virtual Machine Migration*.
+
 . Click *Cancel Migration* to cancel the virtual machine live migration.

modules/virt-connecting-vnc-console.adoc

@@ -7,13 +7,12 @@
 = Connecting to the VNC console
 
 Connect to the VNC console of a running virtual machine from the *Console* tab
-in the *Virtual Machine Overview* screen of the web console.
+on the *VirtualMachine details* page of the web console.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Select a virtual machine to open the *Virtual Machine Overview* page.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
+. Select a virtual machine to open the *VirtualMachine details* page.
 . Click the *Console* tab. The VNC console opens by default.
 . Optional: Open the VNC console in a separate window by clicking *Open Console in New Window*.
 . Optional: Send key combinations to the virtual machine by clicking *Send Key*.

modules/virt-creating-a-custom-image-boot-source-web.adoc

@@ -15,9 +15,9 @@ Use this procedure to complete the following tasks:
 * Attaching the boot source to a custom template
 
 .Procedure
-. In the {VirtProductName} console, click *Workloads* > *Virtualization* from the side menu.
-. Click the *Templates* tab.
-. Click the link in the *Source provider* column for the template you want to customize. A window displays, indicating that the template currently has a *defined* source.
+
+. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
+. Click the link in the *Boot source* column for the template you want to customize. A window displays, indicating that the template currently has a *defined* source.
 . In the window, click the *Customize source* link.
 . Click *Continue* in the *About boot source customization* window to proceed with customization after reading the information provided about the boot source customization process.
 . On the *Prepare boot source customization* page, in the *Define new template* section:

modules/virt-creating-a-vm-from-a-template-with-an-attached-boot-source.adoc

@@ -10,8 +10,8 @@ After you add a boot source to a template, you can create a new virtual machine
 
 .Procedure
 
-. In the {product-title} web console, click *Workloads > Virtualization* in the side menu.
-. From the *Virtual Machines* tab or the *Templates* tab, click *Create* and select *Virtual Machine with Wizard*.
+. In the {product-title} web console, click *Virtualization* -> *VirtualMachines* in the side menu.
+. Click *Create* and select *Virtual Machine with Wizard*.
 . In the *Select a template* step, select an OS from the Operating System list that has the *(Source available)* label next to the OS and version name. The *(Source available)* label indicates that a boot source is available for this OS.
 . Click *Review and Confirm*.
 . Review your virtual machine settings and edit them, if required.

modules/virt-creating-template-wizard-web.adoc

@@ -15,9 +15,7 @@ The wizard guides you to create a custom virtual machine template where you spec
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *Templates* tab.
+. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
 
 . Click *Create* and select *Template with Wizard*.
 
@@ -31,7 +29,7 @@ The wizard guides you to create a custom virtual machine template where you spec
 
 . Click *Next* to progress to the *Storage* step.
 
-. Click *Add Disk* to add a disk, and complete your selections for the fields in the *Add Disk* screen.
+. Click *Add disk* to add a disk, and complete your selections for the fields in the *Add disk* screen.
 +
 [NOTE]
 ====
@@ -56,4 +54,4 @@ Statically inject an SSH key by using the custom script in cloud-init or in the
 
 . Click *See virtual machine template details* to view details about the virtual machine template.
 
-The template is also listed in the *Templates* tab.
+The template is also listed on the *Templates* page.

modules/virt-creating-vm-quick-start-web.adoc

@@ -11,6 +11,7 @@ The web console provides Quick Starts with instructional guided tours for creati
 Tasks in a Quick Start begin with selecting a Red Hat template. Then, you can add a boot source and import the operating system image. Finally, you can save the custom template and use it to create a virtual machine.
 
 .Prerequisites
+
 * Access to the website where you can download the URL link for the operating system image.
 
 .Procedure
@@ -19,4 +20,4 @@ Tasks in a Quick Start begin with selecting a Red Hat template. Then, you can ad
 
 . Click on a tile in the Quick Starts catalog. For example: *Creating a Red Hat Linux Enterprise Linux virtual machine*.
 
-. Follow the instructions in the guided tour and complete the tasks for importing an operating system image and creating a virtual machine. The *Virtual Machines* tab displays the virtual machine.
+. Follow the instructions in the guided tour and complete the tasks for importing an operating system image and creating a virtual machine. The *Virtualization* -> *VirtualMachines* page displays the virtual machine.

modules/virt-creating-vm-snapshot-web.adoc

@@ -15,23 +15,18 @@ To create snapshots of an online (Running state) VM with the highest integrity,
 The QEMU guest agent takes a consistent snapshot by attempting to quiesce the VM’s file system as much as possible, depending on the system workload. This ensures that in-flight I/O is written to the disk before the snapshot is taken. If the guest agent is not present, quiescing is not possible and a best-effort snapshot is taken. The conditions under which the snapshot was taken are reflected in the snapshot indications that are displayed in the web console or CLI.
 ====
 
-[NOTE]
-====
 The VM snapshot only includes disks that meet the following requirements:
 
 * Must be either a data volume or persistent volume claim
 * Belong to a storage class that supports Container Storage Interface (CSI) volume snapshots
-====
 
 .Procedure
 
-. Click *Workloads* → *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
-
-. If the virtual machine is running, click *Actions* → *Stop Virtual Machine* to power it down.
+. If the virtual machine is running, click *Actions* → *Stop* to power it down.
 
 . Click the *Snapshots* tab and then click *Take Snapshot*.
 

modules/virt-creating-vm-wizard-web.adoc

@@ -14,9 +14,9 @@ Create network interface controllers (NICs) and storage disks later and attach t
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. From the *Virtual Machines* tab or the *Templates* tab, click *Create* and select *Virtual Machine with Wizard*.
+. Click *Create* and select *Virtual Machine with Wizard*.
 
 . Select a template that is configured with a boot source.
 
@@ -26,7 +26,7 @@ Create network interface controllers (NICs) and storage disks later and attach t
 
 . Click *Create virtual machine* and exit the wizard or continue with the wizard to customize the virtual machine.
 
-.  Click *Customize virtual machine* to go to the *General* step.
+. Click *Customize virtual machine* to go to the *General* step.
 
 .. Optional: Edit the *Name* field to specify a custom name for the virtual machine.
 
@@ -40,7 +40,7 @@ Create network interface controllers (NICs) and storage disks later and attach t
 
 . Click *Next* to go to the *Storage* step.
 
-.. Optional: Click *Add Disk* to create additional disks. These disks can be removed by clicking the Options menu {kebab} and selecting *Delete*.
+.. Optional: Click *Add disk* to create additional disks. These disks can be removed by clicking the Options menu {kebab} and selecting *Delete*.
 
 .. Optional: Click the Options menu {kebab} to edit the disk and save your changes.
 
@@ -61,4 +61,4 @@ Statically inject an SSH key by using the custom script in cloud-init or in the
 
 . Click *See virtual machine details* to view the *Overview* for this virtual machine.
 +
-The virtual machine is listed in the *Virtual Machines* tab.
+The virtual machine is listed on the *VirtualMachines* page.

modules/virt-creating-vm-yaml-web.adoc

@@ -17,12 +17,11 @@ Navigating away from the YAML screen while editing cancels any changes to the co
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Click *Create* and select *Virtual Machine With YAML*.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
+. Click *Create* and select *With YAML*.
 . Write or paste your virtual machine configuration in the editable window.
 .. Alternatively, use the `example` virtual machine provided by default in the YAML screen.
 . Optional: Click *Download* to download the YAML configuration file in its present state.
 . Click *Create* to create the virtual machine.
 
-The virtual machine is listed in the *Virtual Machines* tab.
+The virtual machine is listed on the *VirtualMachines* page.

modules/virt-delete-vm-web.adoc

@@ -15,12 +15,10 @@ When you delete a virtual machine, the data volume it uses is automatically dele
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
+. Click the Options menu {kebab} of the virtual machine that you want to delete and select *Delete*.
 
-. Click the Options menu {kebab} of the virtual machine that you want to delete and select *Delete Virtual Machine*.
-
-** Alternatively, click the virtual machine name to open the *Virtual Machine Overview* screen and click *Actions* -> *Delete Virtual Machine*.
+** Alternatively, click the virtual machine name to open the *VirtualMachine details* page and click *Actions* -> *Delete*.
 
 . In the confirmation pop-up window, click *Delete* to permanently delete the virtual machine.

modules/virt-deleting-template-web.adoc

@@ -15,12 +15,12 @@ You can delete virtual machine templates that were created by using a Red Hat te
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
+. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
 
-. Click the *Templates* tab. Select the appropriate method to delete a virtual machine template:
+. Select the appropriate method to delete a virtual machine template:
 
-** Click the Options menu {kebab} of the template to delete and select *Delete Template*.
+* Click the Options menu {kebab} of the template to delete and select *Delete Template*.
 
-** Click the template name to open the *Virtual Machine Template Details* screen and click *Actions* -> *Delete Template*.
+* Click the template name to open the *Details* page and then click *Actions* -> *Delete Template*.
 
 . In the confirmation pop-up window, click *Delete* to permanently delete the template.

modules/virt-deleting-vm-snapshot-web.adoc

@@ -10,18 +10,12 @@ You can delete an existing virtual machine snapshot by using the web console.
 
 .Procedure
 
-. Click *Workloads* → *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
-
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
 . Click the *Snapshots* tab. The page displays a list of snapshots associated with the virtual machine.
 
-. Choose one of the following methods to delete a virtual machine snapshot:
-
-.. Click the Options menu {kebab} of the virtual machine snapshot that you want to delete and select *Delete Virtual Machine Snapshot*.
-
-.. Select a snapshot to open the *Snapshot Details* screen and click *Actions* → *Delete Virtual Machine Snapshot*.
+. Click the Options menu {kebab} of the virtual machine snapshot that you want to delete and select *Delete VirtualMachineSnapshot*.
 
 . In the confirmation pop-up window, click *Delete* to delete the snapshot.

modules/virt-deleting-vmis-web.adoc

@@ -10,12 +10,8 @@ Delete a standalone virtual machine instance (VMI) from the web console.
 
 .Procedure
 
-. In the {product-title} web console, click *Workloads* -> *Virtualization* from the side menu.
+. In the {product-title} web console, click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the ⋮ button of the standalone virtual machine instance (VMI) that you want to delete and select *Delete Virtual Machine Instance*.
-
-** Alternatively, click the name of the standalone VMI. The *Virtual Machine Instance Overview* page displays.
-
-. Select *Actions* -> *Delete Virtual Machine Instance*.
+. Click *Actions* -> *Delete VirtualMachineInstance*.
 
 . In the confirmation pop-up window, click *Delete* to permanently delete the standalone VMI.

modules/virt-edit-boot-order-web.adoc

@@ -10,11 +10,9 @@ Edit the boot order list in the web console.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
-
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
 . Click the *Details* tab.
 

modules/virt-edit-cdrom-vm.adoc

@@ -8,14 +8,14 @@
 
 ifeval::["{context}" == "virt-edit-vms"]
 :object: virtual machine
-:object-gui: Virtual Machines
-:object-overview: Virtual Machine Overview
+:object-gui: VirtualMachines
+:object-overview: VirtualMachine details
 endif::[]
 
 ifeval::["{context}" == "virt-editing-vm-template"]
 :object: virtual machine template
 :object-gui: Templates
-:object-overview: VM Template Details
+:object-overview: Template details
 endif::[]
 
 :_content-type: PROCEDURE
@@ -26,9 +26,7 @@ Use the following procedure to edit CD-ROMs for {object}s.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *{object-gui}* tab.
+. Click *Virtualization* ->  *{object-gui}* from the side menu.
 
 . Select a {object} to open the *{object-overview}* screen.
 

modules/virt-editing-template-yaml-web.adoc

@@ -17,11 +17,9 @@ Navigating away from the YAML screen while editing cancels any changes to the co
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
+. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
 
-. Click the *Templates* tab.
-
-. Select a template to open the *VM Template Details* screen.
+. Click a template to open the *Template details* page.
 
 . Click the *YAML* tab to display the editable configuration.
 

modules/virt-editing-vm-web.adoc

@@ -15,14 +15,14 @@ ifeval::["{context}" == "virt-editing-vm-template"]
 :virt-vm-template:
 :object: virtual machine template
 :object-gui: Templates
-:object-vm-details: VM Template Details
+:object-vm-details: Template details
 endif::[]
 
 ifeval::["{context}" == "virt-edit-vms"]
 :virt-vm:
 :object: virtual machine
-:object-gui: Virtual Machines
-:object-vm-details: Details
+:object-gui: VirtualMachines
+:object-vm-details: VirtualMachine details
 endif::[]
 
 :_content-type: PROCEDURE
@@ -36,15 +36,11 @@ You can edit labels and annotations for any templates, including those provided
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *{object-gui}* tab.
+. Click *Virtualization* -> *{object-gui}* from the side menu.
 
 . Optional: Use the *Filter* drop-down menu to sort the list of {object}s by attributes such as status, template, node, or operating system (OS).
 
-. Select a {object}.
-
-. Click the *{object-vm-details}* tab.
+. Select a {object} to open the *{object-vm-details}* page.
 
 . Click any field that has the pencil icon, which indicates that the field is editable. For example, click the current *Boot mode* setting, such as BIOS or UEFI, to open the *Boot mode* window and select an option from the list.
 

modules/virt-editing-vm-yaml-web.adoc

@@ -5,10 +5,12 @@
 //
 ifeval::["{context}" == "virt-edit-vms"]
 :object: virtual machine
+:object-gui: VirtualMachines
 endif::[]
 
 ifeval::["{context}" == "virt-editing-vm-template"]
 :object: virtual machine template
+:object-gui: Templates
 endif::[]
 
 :_content-type: PROCEDURE
@@ -27,7 +29,7 @@ Navigating away from the YAML screen while editing cancels any changes to the co
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
+. Click *Virtualization* -> *{object-gui}* from the side menu.
 
 . Select a {object}.
 

modules/virt-editing-vmis-web.adoc

@@ -10,7 +10,7 @@ You can edit annotations and labels for a standalone virtual machine instance (V
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu. A list of virtual machines (VMs) and standalone VMIs displays.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
 . Click the name of a standalone VMI to open the *Virtual Machine Instance Overview* screen.
 

modules/virt-enabling-dedicated-resources.adoc

@@ -26,9 +26,9 @@ You can enable dedicated resources for a {object} in the *Details* tab. Virtual
 
 .Procedure
 
-. Click *Workloads* -> *{object-gui}s* from the side menu.
+. Click *Virtualization* -> *{object-gui}s* from the side menu.
 . Select a {object} to open the *{object-gui}* tab.
-. Click the *Details* tab.
+. Click the *Scheduling* tab.
 . Click the pencil icon to the right of the *Dedicated Resources* field to open the *Dedicated Resources* window.
 . Select *Schedule this workload with dedicated resources (guaranteed policy)*.
 . Click *Save*.

modules/virt-generalizing-windows-sysprep.adoc

@@ -6,17 +6,17 @@
 [id="virt-generalizing-windows-sysprep_{context}"]
 = Generalizing a Windows VM using sysprep
 
-Generalizing an image allows that image to remove all system-specific configuration data when the image is deployed on a virtual machine.
+Generalizing an image allows that image to remove all system-specific configuration data when the image is deployed on a virtual machine (VM).
 
 Before generalizing the VM, you must ensure the `sysprep` tool cannot detect an answer file after the unattended Windows installation.
 
 .Procedure
 
-. Remove the `sysprep` disk.
-.. In the web console, select *Virtualization* -> *Virtual Machines*, and select the relevant VM.
-.. Click *Disks*.
-.. Click the Options menu {kebab} for the `sysprep` disk, then click *Delete*.
-.. Click *Detach* in the *Detach sysprep disk* dialog.
+. In the web console, click *Virtualization* -> *VirtualMachines*.
+. Select a Windows VM to open the *VirtualMachine details* page.
+. Click the *Disks* tab.
+. Click the Options menu {kebab} for the `sysprep` disk and select *Detach*.
+. Click *Detach*.
 . Rename `C:\Windows\Panther\unattend.xml` to avoid detection by the `sysprep` tool.
 
 . Start the `sysprep` program by running the following command:

modules/virt-hot-plugging-a-virtual-disk-using-the-web-console.adoc

@@ -13,12 +13,12 @@ Hot-plug virtual disks that you want to attach to a virtual machine instance (VM
 
 .Procedure
 
-. Click *Workloads* → *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. On the *Virtual Machines* tab, select the running virtual machine select the running virtual machine to which you want to hot-plug a virtual disk.
+. Select a running virtual machine to open the *VirtualMachine details* page.
 
-. On the *Disks* tab, click *Add Disk*.
+. On the *Disks* tab, click *Add disk*.
 
-. In the *Add Disk* window, fill in the information for the virtual disk that you want to hot-plug.
+. In the *Add disk* window, fill in the information for the virtual disk that you want to hot-plug.
 
 . Click *Add*.

modules/virt-hot-unplugging-a-virtual-disk-using-the-web-console.adoc

@@ -13,9 +13,9 @@ Hot-unplug virtual disks that you want to attach to a virtual machine instance (
 
 .Procedure
 
-. Click *Workloads* → *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. On the *Virtual Machines* tab, select the running virtual machine with the disk you want to hot-unplug.
+. Select the running virtual machine with the disk you want to hot-unplug to open the *VirtualMachine details* page.
 
 . On the *Disks* tab, click the Options menu {kebab} of the virtual disk that you want to hot-unplug.
 

modules/virt-importing-rhel-image-boot-source-web.adoc

@@ -4,35 +4,30 @@
 
 :_content-type: PROCEDURE
 [id="virt-importing-rhel-image-boot-source-web_{context}"]
-= Importing a Red Hat Enterprise Linux image as a boot source
+= Importing a {op-system-base} image as a boot source
 
-You can import a Red Hat Enterprise Linux (RHEL) image as a boot source by specifying the URL address for the image.
+You can import a {op-system-base-full} image as a boot source by specifying a URL for the image.
 
 .Prerequisites
-* You must have access to the web server with the operating system image. For example: Red Hat Enterprise Linux web page with images.
+
+* You must have access to a web page with the operating system image. For example: Download Red Hat Enterprise Linux web page with images.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *Templates* tab.
+. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
 
 . Identify the RHEL template for which you want to configure a boot source and click *Add source*.
 
-. In the *Add boot source to template* window, select *Import via URL (creates PVC)*  from the *Boot source type* list.
+. In the *Add boot source to template* window, select *URL (creates PVC)* from the *Boot source type* list.
 
 . Click *RHEL download page* to access the Red Hat Customer Portal. A list of available installers and images is displayed on the Download Red Hat Enterprise Linux page.
 
 . Identify the Red Hat Enterprise Linux KVM guest image that you want to download. Right-click *Download Now*, and copy the URL for the image.
 
-. In the *Add boot source to template* window, paste the copied URL of the guest image into the *Import URL* field, and click *Save and import*.
+. In the *Add boot source to template* window, paste the URL into the *Import URL* field, and click *Save and import*.
 
 .Verification
 
-To verify that a boot source was added to the template:
+. Verify that the template displays a green checkmark in the *Boot source* column on the *Templates* page.
 
-. Click the *Templates* tab.
-
-. Confirm that the tile for this template displays a green checkmark.
-
-You can now use this template to create RHEL virtual machines.
+You can now use this template to create {op-system-base} virtual machines.

modules/virt-initiating-vm-migration-web.adoc

@@ -10,20 +10,16 @@ Migrate a running virtual machine instance to a different node in the cluster.
 
 [NOTE]
 ====
-The *Migrate Virtual Machine* action is visible to all users but only admin users
-can initiate a virtual machine migration.
+The *Migrate* action is visible to all users but only admin users can initiate a virtual machine migration.
 ====
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. You can initiate the migration from this screen, which makes it easier to
-perform actions on multiple virtual machines in the one screen, or from the
-*Virtual Machine Overview* screen where you can view comprehensive details of the
-selected virtual machine:
-** Click the Options menu {kebab} at the end of virtual machine and select
-*Migrate Virtual Machine*.
-** Click the virtual machine name to open the *Virtual Machine Overview*
-screen and click *Actions* -> *Migrate Virtual Machine*.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
+
+. You can initiate the migration from this page, which makes it easier to perform actions on multiple virtual machines on the same page, or from the *VirtualMachine details* page where you can view comprehensive details of the selected virtual machine:
+
+* Click the Options menu {kebab} next to the virtual machine and select *Migrate*.
+* Click the virtual machine name to open the *VirtualMachine details* page and click *Actions* -> *Migrate*.
+
 . Click *Migrate* to migrate the virtual machine to another node.

modules/virt-marking-vm-templates-favorites.adoc

@@ -6,11 +6,12 @@
 [id="virt-marking-vm-templates-favorites_{context}"]
 = Marking virtual machine templates as favorites
 
-For easier access to virtual machine templates that are used frequently, you can mark those templates as favorites.
+You can mark frequently used templates as favorites.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Templates* tab.
-. Identify the Red Hat template that you want to mark as a favorite.
-. Click the Options menu {kebab} and select *Favorite template*. The template moves up higher in the list of displayed templates.
+. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
+
+. Click the star icon next to a template to mark it as a favorite.
++
+Favorite templates are displayed at the top of the template list.

modules/virt-monitoring-vm-migration-web.adoc

@@ -6,12 +6,10 @@
 [id="virt-monitoring-vm-migration-web_{context}"]
 = Monitoring live migration of a virtual machine instance in the web console
 
-For the duration of the migration, the virtual machine has a status of
-*Migrating*. This status is displayed in the *Virtual Machines* tab or in the
-*Virtual Machine Overview* screen for the migrating virtual machine.
+For the duration of the migration, the virtual machine has a status of *Migrating*. This status is displayed on the *VirtualMachines* page or on the *VirtualMachine details* page of the migrating virtual machine.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
+
+. Select a virtual machine to open the *VirtualMachine details* page.

modules/virt-remove-boot-order-item-web.adoc

@@ -12,11 +12,9 @@ Remove items from a boot order list by using the web console.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
-
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
 . Click the *Details* tab.
 
@@ -28,6 +26,5 @@ Remove items from a boot order list by using the web console.
 ====
 If the virtual machine is running, changes to *Boot Order* will not take effect until you restart the virtual machine.
 
-You can view pending changes by clicking *View Pending Changes* on the right side of the *Boot Order* field. The *Pending Changes* banner at the
-top of the page displays a list of all changes that will be applied when the virtual machine restarts.
+You can view pending changes by clicking *View Pending Changes* on the right side of the *Boot Order* field. The *Pending Changes* banner at the top of the page displays a list of all changes that will be applied when the virtual machine restarts.
 ====

modules/virt-removing-secret-configmap-service-account-vm.adoc

@@ -11,16 +11,13 @@ Remove a secret, config map, or service account from a virtual machine by using
 
 .Prerequisites
 
-* You must have at least one secret, config map, or service account
-that is attached to a virtual machine.
+* You must have at least one secret, config map, or service account that is attached to a virtual machine.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
-
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
 . Click the *Environment* tab.
 
@@ -36,6 +33,6 @@ You can reset the form to the last saved state by clicking *Reload*.
 
 .Verification
 
-. From the *Virtual Machine Overview* page, click the *Disks* tab.
+. On the *VirtualMachine details* page, click the *Disks* tab.
 
 . Check to ensure that the secret, config map, or service account that you removed is no longer included in the list of disks.

modules/virt-restarting-vm-web.adoc

@@ -15,9 +15,7 @@ To avoid errors, do not restart a virtual machine while it has a status of *Impo
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *Virtual Machines* tab.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
 . Find the row that contains the virtual machine that you want to restart.
 
@@ -30,11 +28,9 @@ To avoid errors, do not restart a virtual machine while it has a status of *Impo
 * To view comprehensive information about the selected virtual machine before
 you restart it:
 
-.. Access the *Virtual Machine Overview* screen by clicking the name of the virtual
+.. Access the *VirtualMachine details* page by clicking the name of the virtual
 machine.
 
-.. Click *Actions*.
-
-. Select *Restart Virtual Machine*.
+.. Click *Actions* -> *Restart*.
 
 . In the confirmation window, click *Restart* to restart the virtual machine.

modules/virt-restoring-vm-from-snapshot-web.adoc

@@ -10,13 +10,11 @@ You can restore a virtual machine (VM) to a previous configuration represented b
 
 .Procedure
 
-. Click *Workloads* → *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
-
-. If the virtual machine is running, click *Actions* → *Stop Virtual Machine* to power it down.
+. If the virtual machine is running, click *Actions* → *Stop* to power it down.
 
 . Click the *Snapshots* tab. The page displays a list of snapshots associated with the virtual machine.
 
@@ -24,6 +22,6 @@ You can restore a virtual machine (VM) to a previous configuration represented b
 
 .. For the snapshot that you want to use as the source to restore the VM, click *Restore*.
 
-.. Select a snapshot to open the *Snapshot Details* screen and click *Actions* → *Restore Virtual Machine Snapshot*.
+.. Select a snapshot to open the *Snapshot Details* screen and click *Actions* → *Restore VirtualMachineSnapshot*.
 
 . In the confirmation pop-up window, click *Restore* to restore the VM to its previous configuration represented by the snapshot.

modules/virt-resuming-node-maintenance-web.adoc

@@ -12,7 +12,7 @@ of the *Node Details* screen.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Compute* -> *Nodes*.
+. In the {product-title} console, click *Compute* -> *Nodes*.
 . You can resume the node from this screen, which makes it easier to perform 
 actions on multiple nodes in the one screen, or from the *Node Details* screen 
 where you can view comprehensive details of the selected node:

modules/virt-setting-node-maintenance-web.adoc

@@ -12,7 +12,7 @@ screen.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Compute* -> *Nodes*.
+. In the {product-title} console, click *Compute* -> *Nodes*.
 . You can set the node to maintenance from this screen, which makes it easier to perform 
 actions on multiple nodes in the one screen or from the *Node Details* screen
 where you can view comprehensive details of the selected node:

modules/virt-starting-vm-web.adoc

@@ -10,9 +10,7 @@ You can start a virtual machine from the web console.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *Virtual Machines* tab.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
 . Find the row that contains the virtual machine that you want to start.
 
@@ -22,22 +20,17 @@ You can start a virtual machine from the web console.
 
 .. Click the Options menu {kebab} located at the far right end of the row.
 
-* To view comprehensive information about the selected virtual machine before
-you start it:
+* To view comprehensive information about the selected virtual machine before you start it:
 
-.. Access the *Virtual Machine Overview* screen by clicking the name of the virtual
-machine.
+.. Access the *VirtualMachine details* page by clicking the name of the virtual machine.
 
 .. Click *Actions*.
 
-. Select *Start Virtual Machine*.
+. Select *Restart*.
 
 . In the confirmation window, click *Start* to start the virtual machine.
 
 [NOTE]
 ====
-When you start virtual machine that is provisioned from a `URL` source for the
-first time, the virtual machine has a status of *Importing* while {VirtProductName}
-imports the container from the URL endpoint. Depending on the size of the image,
-this process might take several minutes.
+When you start virtual machine that is provisioned from a `URL` source for the first time, the virtual machine has a status of *Importing* while {VirtProductName} imports the container from the URL endpoint. Depending on the size of the image, this process might take several minutes.
 ====

modules/virt-stopping-vm-web.adoc

@@ -10,9 +10,7 @@ You can stop a virtual machine from the web console.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *Virtual Machines* tab.
+. Click *Virtualization* ->  *VirtualMachines* from the side menu.
 
 . Find the row that contains the virtual machine that you want to stop.
 
@@ -22,14 +20,10 @@ You can stop a virtual machine from the web console.
 
 .. Click the Options menu {kebab} located at the far right end of the row.
 
-* To view comprehensive information about the selected virtual machine before
-you stop it:
+* To view comprehensive information about the selected virtual machine before you stop it:
 
-.. Access the *Virtual Machine Overview* screen by clicking the name of the virtual
-machine.
+.. Access the *VirtualMachine details* page by clicking the name of the virtual machine.
 
-.. Click *Actions*.
-
-. Select *Stop Virtual Machine*.
+.. Click *Actions* → *Stop*.
 
 . In the confirmation window, click *Stop* to stop the virtual machine.

modules/virt-switching-displays.adoc

@@ -15,7 +15,7 @@ If your Windows virtual machine (VM) has a vGPU attached, you can switch between
 
 .Procedure
 
-. In the {VirtProductName} console, click *Virtualization* -> *VirtualMachines*
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines*
 . Select a Windows virtual machine to open the *Overview* screen.
 . Click the *Console* tab.
 . From the list of consoles, select *VNC console*.

modules/virt-template-fields-for-boot-source.adoc

@@ -5,7 +5,8 @@
 [id="virt-template-fields-for-boot-source_{context}"]
 = Virtual machine template fields for adding a boot source
 
-The following table describes the fields for *Add boot source to template* window. This window displays when you click *Add Source* for a virtual machine template in the *Templates* tab.
+The following table describes the fields for *Add boot source to template* window. This window displays when you click *Add source* for a virtual machine template on the *Virtualization* -> *Templates* page.
+
 [cols="2a,3a,5a"]
 |===
 |Name | Parameter |  Description
@@ -14,21 +15,21 @@ The following table describes the fields for *Add boot source to template* windo
 |Upload local file (creates PVC)
 |Upload a file from your local device. Supported file types include gz, xz, tar, and qcow2.
 
-|Import via URL (creates PVC)
-|Import content from an image available from an HTTP or HTTPS endpoint. Obtain the download link URL from the web page where the image download is available and enter that URL link in the *Import via URL (creates PVC)* field. Example: For a Red Hat Enterprise Linux image, log on to the Red Hat Customer Portal, access the image download page, and copy the download link URL for the KVM guest image.
+|URL (creates PVC)
+|Import content from an image available from an HTTP or HTTPS endpoint. Obtain the download link URL from the web page where the image download is available and enter that URL link in the *Import URL* field. Example: For a Red Hat Enterprise Linux image, log on to the Red Hat Customer Portal, access the image download page, and copy the download link URL for the KVM guest image.
 
-|Clone existing PVC (creates PVC)
+|PVC (creates PVC)
 |Use a PVC that is already available in the cluster and clone it.
 
-|Import via Registry (creates PVC)
+|Registry (creates PVC)
 |Specify the bootable operating system container that is located in a registry and accessible from the cluster. Example: kubevirt/cirros-registry-dis-demo.
 
 |Source provider
 |
 |Optional field. Add descriptive text about the source for the template or the name of the user who created the template. Example: Red Hat.
 
-.3+|Advanced
-|Storage class
+.3+|Advanced Storage settings
+|StorageClass
 |The storage class that is used to create the disk.
 
 |Access mode

modules/virt-unpausing-vm-web.adoc

@@ -19,9 +19,7 @@ You can pause virtual machines by using the `virtctl` client.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *Virtual Machines* tab.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
 . Find the row that contains the virtual machine that you want to unpause.
 
@@ -34,7 +32,7 @@ You can pause virtual machines by using the `virtctl` client.
 * To view comprehensive information about the selected virtual machine before
 you unpause it:
 
-.. Access the *Virtual Machine Overview* screen by clicking the name of the virtual
+.. Access the *VirtualMachine details* page by clicking the name of the virtual
 machine.
 
 .. Click the pencil icon that is located on the right side of *Status*.

modules/virt-viewing-qemu-guest-agent-information-web.adoc

@@ -10,12 +10,10 @@ You can use the web console to view information for virtual machines that is pas
 
 .Procedure
 
-. Click *Workloads* -> *Virtual Machines* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
+. Select a virtual machine name to open the *VirtualMachine details* page.
 
-. Select a virtual machine name to open the *Virtual Machine Overview* screen and view the *Details* pane.
-
-. Click *Logged in users* to view the *Details* tab that shows information for users.
+. Click the *Details* tab to view active users.
 
 . Click the *Disks* tab to view information about the file systems.

modules/virt-viewing-virtual-machine-logs-web.adoc

@@ -10,9 +10,12 @@ Get virtual machine logs from the associated virtual machine launcher pod.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
-. In the *Details* tab, click the `virt-launcher-<name>` pod in the *Pod*
-section.
-. Click *Logs*.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
+
+. Select a virtual machine to open the *VirtualMachine details* page.
+
+. Click the *Details* tab.
+
+. Click the `virt-launcher-<name>` pod in the *Pod* section to open the *Pod details* page.
+
+. Click the *Logs* tab to view the pod logs.

modules/virt-viewing-vm-events-web.adoc

@@ -6,15 +6,13 @@
 [id="virt-viewing-vm-events-web_{context}"]
 = Viewing the events for a virtual machine in the web console
 
-You can view the stream events for a running a virtual machine from the
-*Virtual Machine Overview* panel of the web console.
-
-The ▮▮ button pauses the events stream. +
-The ▶ button continues a paused events stream.
+You can view streaming events for a running virtual machine on the *VirtualMachine details* page of the web console.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
-. Click *Events* to view all events for the virtual machine.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
+. Select a virtual machine to open the *VirtualMachine details* page.
+. Click the *Events* tab to view streaming events for the virtual machine.
+
+* The ▮▮ button pauses the events stream.
+* The ▶ button resumes a paused events stream.

modules/virt-viewing-vmi-ip-web.adoc

@@ -6,12 +6,12 @@
 [id="virt-viewing-vmi-ip-web_{context}"]
 = Viewing the IP address of a virtual machine interface in the web console
 
-The IP information displays in the *Virtual Machine Overview* screen for the virtual machine.
+The IP information is displayed on the *VirtualMachine details* page for the virtual machine.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Select a virtual machine name to open the *Virtual Machine Overview* screen.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
 
-The information for each attached NIC is displayed under *IP Address*.
+. Select a virtual machine name to open the *VirtualMachine details* page.
+
+The information for each attached NIC is displayed under *IP Address* on the *Details* tab.

modules/virt-vm-creating-nic-web.adoc

@@ -8,13 +8,16 @@
 
 Create and attach additional NICs to a virtual machine from the web console.
 
+.Prerequisites
+
+* A network attachment definition must be available.
+
 .Procedure
 
-. In the correct project in the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
-. Click *Network Interfaces* to display the NICs already attached to the virtual machine.
+. In the correct project in the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
+. Select a virtual machine to open the *VirtualMachine details* page.
+. Click the *Network Interfaces* tab to view the NICs already attached to the virtual machine.
 . Click *Add Network Interface* to create a new slot in the list.
-. Use the *Network* drop-down list to select the network attachment definition for the additional network.
+. Select a network attachment definition from the *Network* list for the additional network.
 . Fill in the *Name*, *Model*, *Type*, and *MAC Address* for the new NIC.
-. Click *Add* to save and attach the NIC to the virtual machine.
+. Click *Save* to save and attach the NIC to the virtual machine.

modules/virt-vm-rdp-console-web.adoc

@@ -9,24 +9,18 @@
 The desktop viewer console, which utilizes the Remote Desktop Protocol (RDP),
 provides a better console experience for connecting to Windows virtual machines.
 
-To connect to a Windows virtual machine with RDP, download the `console.rdp`
-file for the virtual machine from the *Consoles* tab in the
-*Virtual Machine Details* screen of the web console and supply it to your
-preferred RDP client.
+To connect to a Windows virtual machine with RDP, download the `console.rdp` file for the virtual machine from the *Consoles* tab on the *VirtualMachine Details* page of the web console and supply it to your preferred RDP client.
 
 .Prerequisites
 
-* A running Windows virtual machine with the QEMU guest agent installed. The
-`qemu-guest-agent` is included in the VirtIO drivers.
+* A running Windows virtual machine with the QEMU guest agent installed. The `qemu-guest-agent` is included in the VirtIO drivers.
 * A layer-2 NIC attached to the virtual machine.
-* An RDP client installed on a machine on the same network as the
-Windows virtual machine.
+* An RDP client installed on a machine on the same network as the Windows virtual machine.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Select a Windows virtual machine to open the *Virtual Machine Overview* screen.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
+. Click a Windows virtual machine to open the *VirtualMachine details* page.
 . Click the *Console* tab.
 . In the *Console* list, select *Desktop Viewer*.
 . In the *Network Interface* list, select the layer-2 NIC.

modules/virt-vm-serial-console-web.adoc

@@ -7,15 +7,14 @@
 = Connecting to the serial console
 
 Connect to the serial console of a running virtual machine from the *Console*
-tab in the *Virtual Machine Overview* screen of the web console.
+tab on the *VirtualMachine details* page of the web console.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Select a virtual machine to open the *Virtual Machine Overview* page.
-. Click *Console*. The VNC console opens by default.
-. Select *Disconnect before switching* to ensure that only one console session is open at a time. Otherwise, the VNC console session remains active in the background.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
+. Select a virtual machine to open the *VirtualMachine details* page.
+. Click the *Console* tab. The VNC console opens by default.
+. Click *Disconnect* to ensure that only one console session is open at a time. Otherwise, the VNC console session remains active in the background.
 . Click the *VNC Console* drop-down list and select *Serial Console*.
 . Click *Disconnect* to end the console session.
 . Optional: Open the serial console in a separate window by clicking *Open Console in New Window*.

modules/virt-vm-wizard-fields-web.adoc

@@ -56,13 +56,13 @@ ifdef::vmtemplate[]
 endif::[]
 
 .4+|Boot Source
-|Import via URL (creates PVC)
+|URL (creates PVC)
 |Import content from an image available from an HTTP or HTTPS endpoint. Example: Obtaining a URL link from the web page with the operating system image.
 
-|Clone existing PVC (creates PVC)
+|Clone (creates PVC)
 |Select an existent persistent volume claim available on the cluster and clone it.
 
-|Import via Registry (creates PVC)
+|Registry (creates PVC)
 |Provision virtual machine from a bootable operating system container located in a registry accessible from the cluster. Example: `_kubevirt/cirros-registry-disk-demo_`.
 
 |PXE (network boot - adds network interface)
@@ -84,7 +84,7 @@ endif::[]
 |Tiny, Small, Medium, Large, Custom
 |Presets the amount of CPU and memory in a virtual machine template with predefined values that are allocated to the virtual machine, depending on the operating system associated with that template.
 
-If you choose a default template, you can override the `cpus` and `memsize` values in the template using custom values to create a custom template. Alternatively, you can create a custom template by modifying the `cpus` and `memsize` values in the *Details* tab on the *Workloads* -> *Virtualization* page.
+If you choose a default template, you can override the `cpus` and `memsize` values in the template using custom values to create a custom template. Alternatively, you can create a custom template by modifying the `cpus` and `memsize` values in the *General* tab on the *Template details* page.
 
 .3+a|Workload Type
 

virt/vm_templates/virt-deploying-vm-template-to-custom-namespace.adoc

@@ -5,10 +5,12 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-Red Hat provides preconfigured virtual machine templates that are installed in the `openshift` namespace. The `ssp-operator` deploys virtual machine templates to the `openshift` namespace by default. Templates in the `openshift` namespace are publicly available to all users. These templates are listed in the *Templates* tab within the *Virtualization* page for different operating systems.
+Red Hat provides preconfigured virtual machine templates that are installed in the `openshift` namespace. The `ssp-operator` deploys virtual machine templates to the `openshift` namespace by default. Templates in the `openshift` namespace are publicly available to all users. These templates are listed on the *Virtualization* -> *Templates* page for different operating systems.
 
 include::modules/virt-creating-custom-namespace-for-templates.adoc[leveloffset=+1]
+
 include::modules/virt-adding-templates-to-custom-namespace.adoc[leveloffset=+1]
+
 include::modules/virt-deleting-templates-from-custom-namespace.adoc[leveloffset=+1]
 
 [id="additional-resources_deploying-vm-templates-to-custom-namespace"]

virt/vm_templates/virt-editing-vm-template.adoc

@@ -6,11 +6,14 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-You can update a virtual machine template in the web console, either by editing
-the full configuration in the YAML editor or by selecting a custom template in the *Templates* tab and modifying the editable items.
+You can update a virtual machine template in the web console, either by editing the full configuration in the YAML editor or by selecting a custom template on the *Virtualization* -> *Templates* page and modifying the editable items.
 
 include::modules/virt-editing-vm-web.adoc[leveloffset=+1]
+
 include::modules/virt-editing-template-yaml-web.adoc[leveloffset=+1]
+
 include::modules/virt-add-disk-to-vm.adoc[leveloffset=+1]
+
 include::modules/virt-add-nic-to-vm.adoc[leveloffset=+1]
+
 include::modules/virt-edit-cdrom-vm.adoc[leveloffset=+1]