AWS mgn documentation change
Summary
Minor grammatical and terminology improvements including replacing 'prior to' with 'before', fixing preposition in 'without impact to data replication', and changing 'click' to 'choose' for UI consistency.
Security assessment
Changes are purely editorial improvements with no security implications. No vulnerabilities, security configurations, or security features are mentioned or modified.
Diff
diff --git a/mgn/latest/ug/launching-test-gs.md b/mgn/latest/ug/launching-test-gs.md index 3e637c4e3..c89376a91 100644 --- a//mgn/latest/ug/launching-test-gs.md +++ b//mgn/latest/ug/launching-test-gs.md @@ -13 +13 @@ NEW - You can now accelerate your migration and modernization with AWS Transform -After you have added all of your source servers and configured their launch settings, you are ready to launch a test instance. It is crucial to test the migration of your source servers to AWS prior to initiating a cutover in order to verify that your source servers function properly within the AWS environment. +After you have added all of your source servers and configured their launch settings, you are ready to launch a test instance. It is crucial to test the migration of your source servers to AWS before initiating a cutover to verify that your source servers function properly within the AWS environment. @@ -27 +27 @@ You can test one source server at a time, or simultaneously test multiple source - * Take into consideration that once a test instance is launched, actual resources will be used in your AWS account and you will be billed for these resources. You can terminate the operation of launched Test instances once you verify that they are working properly without impact in order to data replication. + * Take into consideration that once a test instance is launched, actual resources will be used in your AWS account and you will be billed for these resources. You can terminate the operation of launched Test instances once you verify that they are working properly without impact to data replication. @@ -34 +34 @@ You can test one source server at a time, or simultaneously test multiple source -Prior to launching a Test instance, ensure that your source servers are ready for testing by looking for the following indicators on the **Source servers** page: +Before launching a Test instance, ensure that your source servers are ready for testing by looking for the following indicators on the **Source servers** page: @@ -82 +82 @@ You can tell that the Test instance launch started successfully through several -After you have launched your test instances, open the Amazon EC2 Console and SSH or RDP into your test instances in order to ensure that they function correctly. Validate connectivity and perform acceptance tests for your application. +After you have launched your test instances, open the Amazon EC2 Console and SSH or RDP into your test instances to ensure that they function correctly. Validate connectivity and perform acceptance tests for your application. @@ -86 +86 @@ After you have launched your test instances, open the Amazon EC2 Console and SSH -If you encounter any issues and want to launch new test instances, or if you are performing a scheduled test and plan to perform additional tests prior to cutover, you can revert the test. This will revert your source servers' **Migration lifecycle** status to **Ready for testing** , indicating that these servers still require additional testing before they are ready for cutover. During a revert, you will also have the option to delete your Test instances for cost-saving purposes. +If you encounter any issues and want to launch new test instances, or if you are performing a scheduled test and plan to perform additional tests before cutover, you can revert the test. This will revert your source servers' **Migration lifecycle** status to **Ready for testing** , indicating that these servers still require additional testing before they are ready for cutover. During a revert, you will also have the option to delete your Test instances for cost-saving purposes. @@ -123 +123 @@ The console will indicate that testing has been finalized. The selected source s - 7. The Amazon EC2 Console will automatically search for and display the test instance. Select the instance, open the **Instance state** menu, and choose **Terminate instance**. When the confirmation dialogue appears, click **Terminate**. + 7. The Amazon EC2 Console will automatically search for and display the test instance. Select the instance, open the **Instance state** menu, and choose **Terminate instance**. When the confirmation dialogue appears, choose **Terminate**.