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

@@ -19,6 +19,6 @@ Before this update, deleting the `MigPlan` triggered unnecessary virtual machine
 
 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. This release resolves the pod anti-affinity issue, allowing for scheduling on different nodes. As a result, you 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)]
 
-.Migration-controller Panic due to LimitRange "NIL" found in source project
+.Migration-controller panics due to LimitRange "NIL" found in source project
 
 Before this update, the missing `Min` spec in a LimitRange within the `openshift-migration` namespace caused a panic in the migration-controller pod, disrupting the user experience and preventing successful volume migration. With this release, the migration-controller pod no longer crashes when encountering a LimitRange set to `Nil`. As a result, `rsync` pods now comply with the specified limits, improving the migration process stability and eliminating crashloopbacks in source namespaces.