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

Author: anarnold97

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

@@ -49,4 +49,4 @@ When a migration plan includes a namespace that does not have any persistent vol
 
 There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. 
 
-This issue is not only limited to edge cases. In certain circumstances, such as when network restrictions are applied that cause the DVM phase to fail, the UI still reports the migration status as successful. This behavior is similar to what was previously observed in link:https://issues.redhat.com/browse/MIG-1711[MIG-1711] but occurs under different conditions. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)] 
+This issue is not only limited to unusual or unexpected cases. In certain circumstances, such as when network restrictions are applied that cause the DVM phase to fail, the UI still reports the migration status as successful. This behavior is similar to what was previously observed in link:https://issues.redhat.com/browse/MIG-1711[MIG-1711] but occurs under different conditions. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)]