AWS drs documentation change
Summary
Minor grammatical corrections and typo fixes in the FAQ, including removing duplicate words and fixing possessive form.
Security assessment
The changes are purely grammatical and typographical (e.g., 'store' to 'stores', removing extra 'and', 'it's' to 'its'). No security-related content was added, removed, or modified. The mention of encrypted data storage and encrypted transit remains unchanged in substance.
Diff
diff --git a/drs/latest/userguide/FAQ.md b/drs/latest/userguide/FAQ.md index 8045cac9c..d2238244a 100644 --- a//drs/latest/userguide/FAQ.md +++ b//drs/latest/userguide/FAQ.md @@ -17 +17 @@ With AWS Elastic Disaster Recovery, you can recover your applications on AWS fro -You can use the CEDR to DRS Upgrade Assessment Tool and the Server Upgrade Tool and to move your source servers from CloudEndure Disaster Recovery (CEDR) to AWS Elastic Disaster Recovery (DRS). [Learn more in the CloudEndure documentation](https://docs.cloudendure.com/#Configuring_and_Running_Disaster_Recovery/Upgrade_CEDR_to_DRS/Upgrade_CEDR_to_DRS.htm#Upgrading_from_CEDR_to_AWS%C2%A0DRS%3FTocPath%3DNavigation%7CConfiguring%2520and%2520Running%2520Disaster%2520Recovery%7CUpgrading%2520from%2520CEDR%2520to%2520AWS%25C2%25A0DRS%7C_____0). +You can use the CEDR to DRS Upgrade Assessment Tool and the Server Upgrade Tool to move your source servers from CloudEndure Disaster Recovery (CEDR) to AWS Elastic Disaster Recovery (DRS). [Learn more in the CloudEndure documentation](https://docs.cloudendure.com/#Configuring_and_Running_Disaster_Recovery/Upgrade_CEDR_to_DRS/Upgrade_CEDR_to_DRS.htm#Upgrading_from_CEDR_to_AWS%C2%A0DRS%3FTocPath%3DNavigation%7CConfiguring%2520and%2520Running%2520Disaster%2520Recovery%7CUpgrading%2520from%2520CEDR%2520to%2520AWS%25C2%25A0DRS%7C_____0). @@ -31 +31 @@ Because AWS Elastic Disaster Recovery works at the OS layer it can protect not o -AWS Elastic Disaster Recovery store only configuration and log data on the AWS Elastic Disaster Recovery Console's encrypted database. Replicated data is always stored on the customer’s own cloud VPC. The replicated data is encrypted in transit. +AWS Elastic Disaster Recovery stores only configuration and log data on the AWS Elastic Disaster Recovery Console's encrypted database. Replicated data is always stored on the customer’s own cloud VPC. The replicated data is encrypted in transit. @@ -187 +187 @@ You can then set this launch template as your default version. -You can now use the CEDR to DRS Upgrade Assessment Tool and the Server Upgrade Tool and to move your source servers from CloudEndure Disaster Recovery (CEDR) to AWS Elastic Disaster Recovery (AWS DRS). [Learn more in the CloudEndure documentation](https://docs.cloudendure.com/#Configuring_and_Running_Disaster_Recovery/Upgrade_CEDR_to_DRS/Upgrade_CEDR_to_DRS.htm#Upgrading_from_CEDR_to_AWS%C2%A0DRS%3FTocPath%3DNavigation%7CConfiguring%2520and%2520Running%2520Disaster%2520Recovery%7CUpgrading%2520from%2520CEDR%2520to%2520AWS%25C2%25A0DRS%7C_____0). +You can now use the CEDR to DRS Upgrade Assessment Tool and the Server Upgrade Tool to move your source servers from CloudEndure Disaster Recovery (CEDR) to AWS Elastic Disaster Recovery (AWS DRS). [Learn more in the CloudEndure documentation](https://docs.cloudendure.com/#Configuring_and_Running_Disaster_Recovery/Upgrade_CEDR_to_DRS/Upgrade_CEDR_to_DRS.htm#Upgrading_from_CEDR_to_AWS%C2%A0DRS%3FTocPath%3DNavigation%7CConfiguring%2520and%2520Running%2520Disaster%2520Recovery%7CUpgrading%2520from%2520CEDR%2520to%2520AWS%25C2%25A0DRS%7C_____0). @@ -207 +207 @@ Until the server is ready on DRS, CloudEndure will still be your way to launch R -Do **_not_ ** do use the **Remove from console** option available from the CloudEndure user console. By keeping this server’s records in CloudEndure, you also maintain it’s Point In Time recovery points, allowing you to launch a recovery instance using CloudEndure, should you need such a recovery instance before this server is ready on Elastic Disaster Recovery. +Do **_not_ ** use the **Remove from console** option available from the CloudEndure user console. By keeping this server’s records in CloudEndure, you also maintain its Point In Time recovery points, allowing you to launch a recovery instance using CloudEndure, should you need such a recovery instance before this server is ready on Elastic Disaster Recovery.