AWS mgn documentation change
Summary
Minor wording improvements: replaced 'In order to' with 'To' and 'prior to' with 'before' for clarity.
Security assessment
Changes are purely linguistic improvements without any security implications. No security concepts were added, modified, or referenced.
Diff
diff --git a/mgn/latest/ug/Agentless-Replication-Related-FAQ.md b/mgn/latest/ug/Agentless-Replication-Related-FAQ.md index 117cb8bc9..65487587e 100644 --- a//mgn/latest/ug/Agentless-Replication-Related-FAQ.md +++ b//mgn/latest/ug/Agentless-Replication-Related-FAQ.md @@ -60 +60 @@ You can learn more about how agentless replication works and see a high-level di -Yes. In order to use agentless replication, customers must install the MGN vCenter Client in their source data center. The client discovers the source servers and replicates their data to AWS. +Yes. To use agentless replication, customers must install the MGN vCenter Client in their source data center. The client discovers the source servers and replicates their data to AWS. @@ -93 +93 @@ The MGN vCenter Client can be installed on the following 64 bit Linux versions: -Yes. In order to use the MGN vCenter Client, you must first generate the correct IAM credentials. Learn more in the [agentless replication documentation](./vcenter-credentials-mgn.html). +Yes. To use the MGN vCenter Client, you must first generate the correct IAM credentials. Learn more in the [agentless replication documentation](./vcenter-credentials-mgn.html). @@ -105 +105 @@ You can learn more about installing the MGN vCenter Client as well as installati -Yes. You can configure transparent proxy either by using an environment variable prior to the installation (Linux and Windows), or by using the --proxy-address flag in the Linux installer: +Yes. You can configure transparent proxy either by using an environment variable before the installation (Linux and Windows), or by using the --proxy-address flag in the Linux installer: