Update modules/migration-mtc-release-notes-1-8-9.adoc

Co-authored-by: Shruti Deshpande <[email protected]>

Author: anarnold97

modules/migration-mtc-release-notes-1-8-9.adoc

@@ -15,7 +15,7 @@
 
 Before this update, deleting the `MigPlan` triggered unnecessary virtual machine (VM) migrations. This caused the VMs to resume, leading to migration failures. This release introduces a fix that prevents VMs from migrating when the `MigPlan` is actively removed. As a result, VMs no longer unintentionally migrate when MigPlans are deleted, ensuring a stable environment for users. link:https://issues.redhat.com/browse/MIG-1749[(MIG-1749)]
 
-.Virt-launcher pod remain in pending after migrate the VM from hostpath-csi-basic to hostpath-csi-pvc-block
+.Virt-launcher pod remain in pending after migrating the VM from hostpath-csi-basic to hostpath-csi-pvc-block
 
 Before this update, the `virt-launcher` pod stalled after migrating a VM due to pod anti-affinity conflicts with bound volumes. This resulted in a failed VM migration, causing the virt-launcher pod to get stuck. In this release, we actively resolve the pod anti-affinity issue, allowing for scheduling on different nodes. As a result, users can now migrate VMs from `hostpath-csi-basic` to `hostpath-csi-pvc-block` without pods getting stuck in a pending state, thereby improving the overall migration process efficiency. link:https://issues.redhat.com/browse/MIG-1750[(MIG-1750)]