Unified the web console name in virt docs

Author: jhradilek

modules/virt-about-auto-bootsource-updates.adoc

@@ -15,4 +15,4 @@ When the `enableCommonBootImageImport` feature gate is disabled, `DataSource` ob
 
 _Custom_ boot sources that are not provided by {VirtProductName} are not controlled by the feature gate. You must manage them individually by editing the `HyperConverged` custom resource (CR). You can also use this method to manage individual system-defined boot sources.
 
-Cluster administrators can enable automatic subscription for {op-system-base-full} virtual machines in the {VirtProductName} web console.
+Cluster administrators can enable automatic subscription for {op-system-base-full} virtual machines in the {product-title} web console.

modules/virt-defining-apps-for-dr.adoc

@@ -33,14 +33,14 @@ Use the pod `pullMethod: node` when creating a data volume from a registry sourc
 [id="best-practices-{rh-rhacm}-discovered-vm_{context}"]
 == Best practices when defining an {rh-rhacm}-discovered VM
 
-You can configure any VM in the cluster that is not an {rh-rhacm}-managed application as an {rh-rhacm}-discovered application. This includes VMs imported by using the Migration Toolkit for Virtualization (MTV), VMs created by using the {VirtProductName} web console, or VMs created by any other means, such as the CLI.
+You can configure any VM in the cluster that is not an {rh-rhacm}-managed application as an {rh-rhacm}-discovered application. This includes VMs imported by using the Migration Toolkit for Virtualization (MTV), VMs created by using the {product-title} web console, or VMs created by any other means, such as the CLI.
 
 There are several actions you can take to improve your experience and chance of success when defining an {rh-rhacm}-discovered VM.
 
 [discrete]
 [id="protect-the-vm_{context}"]
-=== Protect the VM when using MTV, the {VirtProductName} web console, or a custom VM
-Because automatic labeling is not currently available, the application owner must manually label the components of the VM application when using MTV, the {VirtProductName} web console, or a custom VM.
+=== Protect the VM when using MTV, the {product-title} web console, or a custom VM
+Because automatic labeling is not currently available, the application owner must manually label the components of the VM application when using MTV, the {product-title} web console, or a custom VM.
 
 After creating the VM, apply a common label to the following resources associated with the VM: `VirtualMachine`, `DataVolume`, `PersistentVolumeClaim`, `Service`, `Route`, `Secret`, `ConfigMap`, `VirtualMachinePreference`, and `VirtualMachineInstancetype`. Do not label virtual machine instances (VMIs) or pods; {VirtProductName} creates and manages these automatically.
 

virt/live_migration/virt-about-live-migration.adoc

@@ -42,7 +42,7 @@ You can perform the following live migration tasks:
 * xref:../../virt/live_migration/virt-configuring-live-migration.adoc#virt-configuring-live-migration[Configure live migration settings]
 * xref:../../virt/live_migration/virt-configuring-live-migration.adoc#virt-configuring-live-migration-heavy_virt-configuring-live-migration[Configure live migration for heavy workloads]
 * xref:../../virt/live_migration/virt-initiating-live-migration.adoc#virt-initiating-live-migration[Initiate and cancel live migration]
-* Monitor the progress of all live migrations in the *Migration* tab of the {virtproductname} web console.
+* Monitor the progress of all live migrations in the *Migration* tab of the {product-title} web console.
 * View VM migration metrics in the *Metrics* tab of the web console.
 
 

virt/live_migration/virt-configuring-live-migration.adoc

@@ -26,7 +26,7 @@ You can create live migration policies to apply different migration configuratio
 
 [TIP]
 ====
-You can create live migration policies by using the {VirtProductName} web console.
+You can create live migration policies by using the {product-title} web console.
 ====
 
 include::modules/virt-configuring-a-live-migration-policy.adoc[leveloffset=+2]

virt/nodes/virt-node-maintenance.adoc

@@ -38,7 +38,7 @@ VM eviction strategy::
 
 The VM `LiveMigrate` eviction strategy ensures that a virtual machine instance (VMI) is not interrupted if the node is placed into maintenance or drained. VMIs with this eviction strategy will be live migrated to another node.
 +
-You can configure eviction strategies for virtual machines (VMs) by using the {VirtProductName} web console or the xref:../../virt/live_migration/virt-configuring-live-migration.adoc#virt-configuring-a-live-migration-policy_virt-configuring-live-migration[command line].
+You can configure eviction strategies for virtual machines (VMs) by using the {product-title} web console or the xref:../../virt/live_migration/virt-configuring-live-migration.adoc#virt-configuring-a-live-migration-policy_virt-configuring-live-migration[command line].
 +
 [IMPORTANT]
 ====