AWS drs documentation change
Summary
Minor grammatical corrections and language improvements in cross-region failover and failback documentation.
Security assessment
Changes are purely editorial, including fixing grammar ('perform failover and failback your' to 'perform failover and failback on your'), subject-verb agreement ('remains' to 'remain'), and removing an extra word ('Do not to stop' to 'Do not stop'). No security-related content is added or modified.
Diff
diff --git a/drs/latest/userguide/failback-failover-region-region.md b/drs/latest/userguide/failback-failover-region-region.md index 5d73734ce..e8f1d0c46 100644 --- a//drs/latest/userguide/failback-failover-region-region.md +++ b//drs/latest/userguide/failback-failover-region-region.md @@ -11 +11 @@ Overview and prerequisitesPerforming cross-region failback -AWS Elastic Disaster Recovery (AWS DRS) allows you to perform failover and failback your EC2-based applications from one AWS Region to another AWS Region. The failover process is the same as failing over into an AWS Region from a source outside of AWS, but the failback process is different. The instructions below describe the complete cross-Region failover and failback process. In the examples, we use us-east-1 as the source AWS Region and us-east-2 as the recovery AWS Region, but any combination of [AWS Regions that are supported by DRS ](./supported-regions.html) will work. +AWS Elastic Disaster Recovery (AWS DRS) allows you to perform failover and failback on your EC2-based applications from one AWS Region to another AWS Region. The failover process is the same as failing over into an AWS Region from a source outside of AWS, but the failback process is different. The instructions below describe the complete cross-Region failover and failback process. In the examples, we use us-east-1 as the source AWS Region and us-east-2 as the recovery AWS Region, but any combination of [AWS Regions that are supported by DRS ](./supported-regions.html) will work. @@ -122 +122 @@ Navigate to the **Recovery instances** in the AWS DRS console. Select the releva -If you have started reversed replication for the recovery instance (A3), you will not be able to disconnect it. To remove the recovery instances (A3) in the source region, simply delete the server. This will ensure that the newly launched failed-back instances (A4) remains protected. +If you have started reversed replication for the recovery instance (A3), you will not be able to disconnect it. To remove the recovery instances (A3) in the source region, simply delete the server. This will ensure that the newly launched failed-back instances (A4) remain protected. @@ -137 +137 @@ To conduct a drill, follow the steps 1 and 2 as described above, and then perfor - 1. Do not to stop the source server (B1) in the recovery AWS region as recommended in the note of step 1-e. + 1. Do not stop the source server (B1) in the recovery AWS region as recommended in the note of step 1-e.