AWS directconnect documentation change
Summary
Corrected grammar, capitalized 'Transit Gateways', and updated section heading
Security assessment
Grammar and terminology standardization. No security mechanisms or vulnerabilities addressed.
Diff
diff --git a/directconnect/latest/UserGuide/multi-account-associate-vgw.md b/directconnect/latest/UserGuide/multi-account-associate-vgw.md index 024699d38..5b0787d42 100644 --- a//directconnect/latest/UserGuide/multi-account-associate-vgw.md +++ b//directconnect/latest/UserGuide/multi-account-associate-vgw.md @@ -9 +9 @@ Allowed prefixes -# Associate an Direct Connect virtual private gateway across accounts +# Associate a Direct Connect virtual private gateway across accounts @@ -21 +21 @@ Consider the case where the VPC CIDR is 10.0.0.0/16. You can set the **Allowed p -Any virtual interface inside network prefixes advertised over Direct Connect are only propagated to transit gateways across Regions, not within the same Region. For more information on how allowed prefixes interact with virtual private gateways and transit gateways, see [Allowed prefixes interactions](./allowed-to-prefixes.html). +Any virtual interface inside network prefixes advertised over Direct Connect are only propagated to Transit Gateways across Regions, not within the same Region. For more information on how allowed prefixes interact with virtual private gateways and Transit Gateways, see [Allowed prefixes interactions](./allowed-to-prefixes.html). @@ -31 +31 @@ Create a private virtual interface to the Direct Connect gateway -Transit gateway associations +Transit Gateway associations