vddk validator

Author: RichardHoch

documentation/modules/vddk-validator-containers.adoc

@@ -8,10 +8,12 @@
 
 When you set cluster or project resource quotas, be sure that you have a sufficient quota for the {project-short} pods to perform the migration. 
 
-For more information on creating, setting, and viewing quotas, see {ocp-doc}/building_applications/index#quotas[Quotas]
+For more information on creating, setting, and viewing quotas, see {ocp-doc}/building_applications/index#quotas[Quotas].
 
-The defaults that are related to VDDK validator containers are listed as follows. You can override these defaults in the `ForkliftController` custom resource (CR).
+[id="defaults-that-can-be-overridden-in-forklift-controller_{context}"]
+== Defaults that can be overridden in the ForkliftController CR:
 
+The defaults that are related to VDDK validator containers are listed as follows. You can override these defaults in the `ForkliftController` custom resource (CR).
 
 [NOTE]
 ====
@@ -20,9 +22,6 @@ These settings are highly dependent on your environment. If there are many migr
 Migration success or failure is also connected to the `MAX_VM_INFLIGHT` setting that determines how many VMs or disks are migrated at once.
 ====
 
-[id="defaults-that-can-be-overridden-in-forklift-controller_{context}"]
-== Defaults that can be overridden in the ForkliftController CR:
-
 * These defaults affect both cold and warm migrations:
 +
 Cold migration is likely to be more resource intensive because it copies the disks. For warm migration, you could potentially reduce the requests.
@@ -44,7 +43,7 @@ Cold and warm migration using `virt-v2v` can be resource-intensive. For more det
 ** hooks_container_requests_cpu: `100m`
 ** hooks_container_requests_memory: `150Mi`
 
-* TThese defaults affect all Open Virtual Appliance (OVA) file migrations: migrations:
+* These defaults affect all Open Virtual Appliance (OVA) file migrations:
 
 ** ova_container_limits_cpu: `1000m`
 ** ova_container_limits_memory: `1Gi`