After Nunzy

documentation/modules/adding-source-provider.adoc

@@ -15,7 +15,11 @@ EMS enforcement is disabled for migrations with VMware vSphere source providers
 
 .Prerequisites
 
-* It is strongly recommended to create a VMware Virtual Disk Development Kit (VDDK) image in a secure registry that is accessible to all clusters. A VDDK image accelerates migration and reduces the risk of a plan failing. If you are not using VDDK and a plan fails, then please retry with VDDK installed. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image].
+[TIP]
+====
+To accelerate migration and reduce the risk of a migration plan failing, create a VMware Virtual Disk Development Kit (VDDK) image in a secure registry that is accessible to all clusters. If you are not using VDDK and a plan fails, then retry with VDDK installed. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image].
+====
+
 endif::[]
 ifdef::rhv[]
 = Adding {a-rhv} source provider

documentation/modules/additional-auth-methods-ostack.adoc

@@ -6,4 +6,4 @@
 * Token authentication
 * Application credential authentication
 
-You can use these methods to migrate virtual machines with {osp} source providers using the CLI the same way you migrate other virtual machines, except for how you prepare the `Secret` manifest.
+You can use these methods to migrate virtual machines with {osp} source providers using the CLI the same way you migrate other virtual machines with one exception: You need to prepare the `Secret` manifest as described in xref:openstack-token-authentication_ostack[Using token authentication with an {osp} source provider] or xref:openstack-application-credential-authentication_ostack[Using application credential authentication with an {osp} source provider].

documentation/modules/file-system-overhead.adoc

@@ -11,11 +11,11 @@ endif::[]
 
 
 ifdef::ostack[]
-When you migrate from {osp} to the {ocp} cluster that {project-full} is deployed on, the migration allocates persistent volumes without  Customized Data Importer (CDI). In these cases, you might need to adjust the file system overhead.
+When you migrate from {osp} to the {ocp} cluster that {project-full} is deployed on, the migration allocates persistent volumes without Customized Data Importer (CDI). In these cases, you might need to adjust the file system overhead.
 endif::[]
 
-If the configured file system overhead, which has a default value of 10%, is too low, the disk transfer will fail due to lack of space. In such a case, you would want to increase the file system overhead.
+The configured file system overhead has a default value of 10%. If that is too low, the disk transfer fails due to lack of space. In this case, increase the file system overhead.
 
-In some cases, however, you might want to decrease the file system overhead to reduce storage consumption.
+If you need to reduce storage consumption, decrease the file system overhead.
 
 You can change the file system overhead by changing the value of the `controller_filesystem_overhead` in the `spec` portion of the `forklift-controller` CR, as described in xref:configuring-mtv-operator_mtv[Configuring the MTV Operator].

documentation/modules/vmware-prerequisites.adoc

@@ -5,8 +5,6 @@
 [id="vmware-prerequisites_{context}"]
 = VMware prerequisites
 
-It is strongly recommended to create a VDDK image to accelerate migrations. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image].
-
 The following prerequisites apply to VMware migrations:
 
 * You must use a xref:compatibility-guidelines_mtv[compatible version] of VMware vSphere.
@@ -15,7 +13,6 @@ The following prerequisites apply to VMware migrations:
 * The VM operating system must be certified and supported for use as a link:https://access.redhat.com/articles/973163#ocpvirt[guest operating system with {virt}] _and_ for link:https://access.redhat.com/articles/1351473[conversion to KVM with `virt-v2v`].
 * If you are running a warm migration, you must enable link:https://kb.vmware.com/s/article/1020128[changed block tracking (CBT)] on the VMs and on the VM disks.
 * If you are migrating more than 10 VMs from an ESXi host in the same migration plan, you must increase the NFC service memory of the host.
-* It is strongly recommended to disable hibernation because {project-first} does not support migrating hibernated VMs.
 
 
 [IMPORTANT]
@@ -28,6 +25,16 @@ In the event of a power outage, data might be lost for a VM with disabled hibern
 Neither {project-short} nor OpenShift Virtualization support conversion of Btrfs for migrating VMs from VMWare.
 ====
 
+[TIP]
+====
+To accelerate migration and reduce the risk of a migration plan failing, create a VMware Virtual Disk Development Kit (VDDK) image in a secure registry that is accessible to all clusters. If you are not using VDDK and a plan fails, then retry with VDDK installed. For more information, see xref:../master.adoc#creating-vddk-image_vmware[Creating a VDDK image].
+====
+
+[TIP]
+====
+It is strongly recommended to disable hibernation because {project-first} does not support migrating hibernated VMs.
+====
+
 [discrete]
 [id="vmware-privileges_{context}"]
 == VMware privileges