Merge pull request #47663 from sabrinajess/CNV18317

CNV-18317: Document VM filtering

Author: ousleyp

modules/virt-about-vm-templates.adoc

@@ -6,7 +6,7 @@
 [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 *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).
 
 The *Templates* tab displays four types of virtual machine templates:
 
@@ -15,9 +15,11 @@ The *Templates* tab displays four types of virtual machine templates:
 * *Red Hat Provided* templates have limited support from Red Hat.
 * *User Provided* templates are *Red Hat Provided* templates that were cloned and created by users.
 
+You can use the filters in the template *Catalog* to sort the templates by attributes such as boot source availability, operating system, and workload.
+
 [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.
+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.
 ====
 
 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-editing-vm-web.adoc

@@ -32,14 +32,16 @@ endif::[]
 
 Edit select values of a {object} in the web console by clicking the pencil icon next to the relevant field. Other values can be edited using the CLI.
 
-Labels and annotations are editable for both preconfigured Red Hat templates and your custom virtual machine templates. All other values are editable only for custom virtual machine templates that users have created using the Red Hat templates or the *Create Virtual Machine Template* wizard.
+You can edit labels and annotations for any templates, including those provided by Red Hat. Other fields are editable for user-customized templates only.
 
 .Procedure
 
 . Click *Workloads* -> *Virtualization* from the side menu.
 
 . Click the *{object-gui}* tab.
 
+. 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.

modules/virt-filtering-vm-templates.adoc

@@ -11,7 +11,6 @@ include::modules/virt-about-vms-and-boot-sources.adoc[leveloffset=+1]
 include::modules/virt-adding-a-boot-source-web.adoc[leveloffset=+1]
 include::modules/virt-template-fields-for-boot-source.adoc[leveloffset=+2]
 include::modules/virt-marking-vm-templates-favorites.adoc[leveloffset=+1]
-include::modules/virt-filtering-vm-templates.adoc[leveloffset=+1]
 include::modules/virt-creating-template-wizard-web.adoc[leveloffset=+1]
 
 [id="virt-template-wizard-fields"]