after Kobi and Aviv's reviews

Author: RichardHoch

documentation/doc-Migrating_your_virtual_machines/assemblies/assembly_advanced-migration-options.adoc

@@ -39,7 +39,7 @@ include::../modules/adding-hook-using-ui.adoc[leveloffset=+2]
 
 include::../modules/adding-hook-using-cli.adoc[leveloffset=+2]
 
-include::../modules/about-udn.adoc[leveloffset=+2]
+include::../modules/about-udn.adoc[leveloffset=+1]
 
 == Scheduling target VMs
 

documentation/modules/configuring-target-vm-scheduling-ui.adoc

@@ -11,7 +11,7 @@ You can use the {project-first} user interface, which is located in the {ocp} we
 
 The *Virtualization* section of the {ocp} web console supports the following options for scheduling target VMs:
 
-* *VM target mode selector*: Ensures VMs are scheduled on nodes that are an exact match for key-value pairs you create. This type of label is often used for nodes with special capabilities, such as GPU nodes or storage nodes. 
+* *VM target node selector*: Ensures VMs are scheduled on nodes that are an exact match for key-value pairs you create. This type of label is often used for nodes with special capabilities, such as GPU nodes or storage nodes. 
 * *VM target labels*: Applies organizational or operational labels to migrated VMs for identification and management.
 * *VM target affinity rules*: Implements placement policies such as co-locating related workloads or, for disaster recovery, ensuring that specific VMs are migrated to different nodes. This type of rule uses hard (requirements) and soft (preferences) conditions combined with logical operators, such as `Exists` or `DoesNotExist` instead of using the rigid key-value pairs used by a VM target node selector. As a result, target affinity rules are more flexible than target affinity rules.
 +

documentation/modules/creating-plan-wizard-vmware.adoc

@@ -343,7 +343,7 @@ Additionally, both types of rules allow you to include both _hard_ and _soft_ co
 *** Click *Add affinity rule*.
 *** Select the *Type* of affinity rule from the list. Valid options: Node Affinity, Workload (pod) Affinity, Workload (pod) Anti-Affinity.
 *** Select the *Condition* rom the list. Valid options: Preferred during scheduling (soft condition), Required  during scheduling (hard condition).
-*** Soft condition only: Enter a numerical *Weight*. The higher the weight, the stronger the preference. Valid options: whole numbers greater than 0.
+*** Soft condition only: Enter a numerical *Weight*. The higher the weight, the stronger the preference. Valid options: whole numbers from 1-100.
 *** Enter a *Typology key*, the key for the node label that the system uses to denote the domain.
 *** Optional: Select the *Workload labels* that you want to set by doing the following:
 **** Enter a *Key*.