Update virtualization documentation

docs/core-functionality/virtualization.md

@@ -1,4 +1,4 @@
-# Virtual Machines and Clusters
+# Virtualization
 
 {!docs/models/virtualization/cluster.md!}
 {!docs/models/virtualization/clustertype.md!}

docs/models/virtualization/cluster.md

@@ -1,5 +1,5 @@
 # Clusters
 
-A cluster is a logical grouping of physical resources within which virtual machines run. A cluster must be assigned a type, and may optionally be assigned to a group and/or site.
+A cluster is a logical grouping of physical resources within which virtual machines run. A cluster must be assigned a type (technological classification), and may optionally be assigned to a cluster group, site, and/or tenant.
 
-Physical devices may be associated with clusters as hosts. This allows users to track on which host(s) a particular VM may reside. However, NetBox does not support pinning a specific VM within a cluster to a particular host device.
+Physical devices may be associated with clusters as hosts. This allows users to track on which host(s) a particular virtual machine may reside. However, NetBox does not support pinning a specific VM within a cluster to a particular host device.

docs/models/virtualization/clustergroup.md

@@ -1,3 +1,3 @@
 # Cluster Groups
 
-Cluster groups may be created for the purpose of organizing clusters. The assignment of clusters to groups is optional.
+Cluster groups may be created for the purpose of organizing clusters. The arrangement of clusters into groups is optional.

docs/models/virtualization/virtualmachine.md

@@ -1,11 +1,14 @@
 # Virtual Machines
 
-A virtual machine represents a virtual compute instance hosted within a cluster. Each VM must be associated with exactly one cluster.
+A virtual machine represents a virtual compute instance hosted within a cluster. Each VM must be assigned to exactly one cluster.
 
-Like devices, each VM can be assigned a platform and have interfaces created on it. VM interfaces behave similarly to device interfaces, and can be assigned IP addresses, VLANs, and services. However, given their virtual nature, they cannot be connected to other interfaces. Unlike physical devices, VMs cannot be assigned console or power ports, device bays, or inventory items.
+Like devices, each VM can be assigned a platform and/or functional role, and must have one of the following operational statuses assigned to it:
 
-The following resources can be defined for each VM:
+* Active
+* Offline
+* Planned
+* Staged
+* Failed
+* Decommissioning
 
-* vCPU count
-* Memory (MB)
-* Disk space (GB)
+Additional fields are available for annotating the vCPU count, memory (GB), and disk (GB) allocated to each VM. Each VM may optionally be assigned to a tenant. Virtual machines may have virtual interfaces assigned to them, but do not support any physical component.

docs/models/virtualization/vminterface.md

@@ -1,3 +1,3 @@
 ## Interfaces
 
-Virtual machine interfaces are similar to device interfaces, but lack properties pertaining to physical attributes. For example, VM interfaces do not have a physical type and cannot have cables attached to them. However, they can have IP address and VLANs (both tagged and untagged) associated with them, just as device interfaces do.
+Virtual machine interfaces behave similarly to device interfaces, and can be assigned IP addresses, VLANs, and services. However, given their virtual nature, they lack properties pertaining to physical attributes. For example, VM interfaces do not have a physical type and cannot have cables attached to them.