AWS Security ChangesHomeSearch

AWS mgn documentation change

Service: mgn · 2025-03-26 · Documentation low

File: mgn/latest/ug/migration-dashboard.md

Summary

Updated phrasing and grammar in multiple sections, replacing 'the following' with 'these' and adjusting verb tenses for consistency

Security assessment

Changes are purely stylistic/grammatical improvements with no security context or references to vulnerabilities

Diff

diff --git a/mgn/latest/ug/migration-dashboard.md b/mgn/latest/ug/migration-dashboard.md
index 798678dfb..a9be6094c 100644
--- a/mgn/latest/ug/migration-dashboard.md
+++ b/mgn/latest/ug/migration-dashboard.md
@@ -158 +158 @@ Within the **Lifecycle** box, you can review the **Launch status** and **Last te
-You can use the following indicators to verify that your test instance was successfully launched::
+You can use these indicators to verify that your test instance was successfully launched::
@@ -323 +323 @@ You can perform a variety of actions, control data replication, and manage your
-The **Actions** menu allows you to perform the following actions:
+The **Actions** menu allows you to perform these actions:
@@ -327 +327 @@ The **Actions** menu allows you to perform the following actions:
-To construct a custom installation command, take the following steps: 
+To construct a custom installation command, take these steps: 
@@ -370 +370 @@ To see your archived servers, open the **Preferences** menu by clicking the gear
-The Replication menu allows you to manage data replication for your source servers through the following actions:
+The Replication menu allows you to manage data replication for your source servers through these actions:
@@ -442 +442 @@ The entire AWS Application Migration Service Console is color-coded for ease of
-Healthy servers with no errors are characterized by the color blue. Both the **Lifecycle** and **Data replication** **status** boxes will display all steps and information in blue if the server is healthy.
+Healthy servers with no errors are characterized by the color blue. Both the **Lifecycle** and **Data replication** **status** boxes display all steps and information in blue if the server is healthy.
@@ -444 +444 @@ Healthy servers with no errors are characterized by the color blue. Both the **L
-The following are examples of healthy servers:
+These are examples of healthy servers:
@@ -450 +450 @@ Servers that are experiencing temporary issues will be characterized by the colo
-The following are examples of servers experiencing temporary issues:
+These are examples of servers experiencing temporary issues: