edits and coderabbit fixes

Author: Jenny-Anne

documentation/modules/ref_vmware-prerequisites.adoc

@@ -7,7 +7,7 @@
 = {vmw} prerequisites
 
 [role="_abstract"]
-Verify that your {vmw} vSphere environment meets the requirements for migrating virtual machines to {virt}. Understanding these prerequisites helps you prepare your source environment and avoid migration failures.
+Verify that your {vmw} vSphere environment meets the requirements for migrating virtual machines (VMs) to {virt}. Understanding these prerequisites helps you prepare your source environment and avoid migration failures.
 
 Create a VDDK image to accelerate migrations. For more information, see xref:proc_creating-vddk-image_mtv[Creating a VDDK image].
 
@@ -22,11 +22,15 @@ Prerequisites::
 * The target namespace must have network connectivity to the {vmw} source environment. NetworkPolicies that block egress connections from the target namespace prevent migration from succeeding.
 * The VM operating system must be certified and supported for use as a guest operating system with {virt} and for conversion to KVM with `virt-v2v`. For more information, see link:https://access.redhat.com/articles/973163#ocpvirt[Guest operating systems supported on {virt}] and link:https://access.redhat.com/articles/1351473[Supported virtual machine guest operating systems for conversions].
 * Disable hibernation on the source VMs. In case of a power outage, data might be lost for a VM with disabled hibernation.
-* To warm migrate a virtual machine, VMware Tools must be installed on the source virtual machine. For more information, see link:https://www.vmware.com/support/ws5/doc/new_guest_tools_ws.html[VMware Tools].
-* To access the virtual machine using a pre-migration hook, VMware Tools must be installed on the source virtual machine. For more information, see link:https://www.vmware.com/support/ws5/doc/new_guest_tools_ws.html[VMware Tools].
+* To warm migrate a VM, VMware Tools must be installed on the source VM. For more information, see link:https://www.vmware.com/support/ws5/doc/new_guest_tools_ws.html[VMware Tools].
+* To access the VM by using a pre-migration hook, VMware Tools must be installed on the source VM. For more information, see link:https://www.vmware.com/support/ws5/doc/new_guest_tools_ws.html[VMware Tools].
 * If you are running a warm migration, you must enable changed block tracking (CBT) on the VMs and on the VM disks. For more information, see link:https://kb.vmware.com/s/article/1020128[Changed Block Tracking (CBT) on virtual machines].
 * If you are migrating more than 10 VMs from an ESXi host in the same migration plan, you must increase the Network File Copy (NFC) service memory of the host.
 * A default `MigController` instance must be present. This instance is required for the Storage Migration option in the {ocp} web console in certain {ocp-name} versions. For steps to create the default `MigController` instance, see link:https://access.redhat.com/solutions/7136894[Storage Migration Option Missing for Virtual Machines in OpenShift 4.20 Despite Availability in 4.18].
 
 Considerations::
-* *Warm migrations of Microsoft Windows VMs:* For virtual machines (VMs) running Microsoft Windows, Volume Shadow Copy Service (VSS) inside the guest VM is used to quiesce the file system and applications. When performing a warm migration of a Microsoft Windows virtual machine from {vmw}, you must start VSS on the Windows guest operating system in order for the snapshot and `Quiesce guest file system` to succeed. If you do not start VSS, the snapshot creation during the warm migration fails with the following error: `An error occurred while taking a snapshot: Failed to restart the virtual machine.` If you set the VSS service to `Manual` and start a snapshot creation with `Quiesce guest file system = yes`, the {vmw} Snapshot provider service requests VSS to start the shadow copy in the background.
+* *Warm migrations of Microsoft Windows VMs:* For virtual machines (VMs) running Microsoft Windows, Volume Shadow Copy Service (VSS) inside the guest VM is used to quiesce the file system and applications. When performing a warm migration of a Microsoft Windows virtual machine from {vmw}, you must start VSS on the Windows guest operating system for the snapshot and `Quiesce guest file system` to succeed.
++
+If you do not start VSS, the snapshot creation during the warm migration fails with the following error: `An error occurred while taking a snapshot: Failed to restart the virtual machine.`
++
+If you set the VSS service to `Manual` and start a snapshot creation with `Quiesce guest file system = yes`, the {vmw} Snapshot provider service requests VSS to start the shadow copy in the background.

documentation/modules/ref_vmware-privileges.adoc

@@ -7,9 +7,9 @@
 = {vmw} privileges
 
 [role="_abstract"]
-Configure user permissions in {vmw} vSphere to allow {project-first} to access and migrate virtual machines. The minimal set of privileges ensures that {project-first} can read VM configurations, manage snapshots, and transfer disk data.
+Configure user permissions in {vmw} vSphere to allow {project-first} to access and migrate virtual machines (VMs). The minimal set of privileges ensures that {project-first} can read VM configurations, manage snapshots, and transfer disk data.
 
-The following minimal set of {vmw} privileges is required to migrate virtual machines to {virt} with the {project-first}. All `Virtual machine.Provisioning` privileges are required.
+The following minimal set of {vmw} privileges is required to migrate VMs to {virt} with the {project-first}. All `Virtual machine.Provisioning` privileges are required.
 
 [cols="2", options="header"]
 .`Virtual machine.Interaction` privileges