AWS wellarchitected documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for terminology consistency
Security assessment
The change is a minor terminology adjustment without altering technical meaning. No security implications are introduced or modified.
Diff
diff --git a/wellarchitected/latest/framework/cost_data_transfer_optimized_components.md b/wellarchitected/latest/framework/cost_data_transfer_optimized_components.md index 67cd88119..fb577d983 100644 --- a//wellarchitected/latest/framework/cost_data_transfer_optimized_components.md +++ b//wellarchitected/latest/framework/cost_data_transfer_optimized_components.md @@ -25 +25 @@ When planning or reviewing your workload architecture, consider the following: - * **Use AWS Direct Connect** AWS Direct Connect bypasses the public internet and establishes a direct, private connection between your on-premises network and AWS. This can be more cost-effective and consistent than transferring large volumes of data over the internet. + * **Use AWS Direct Connect** Direct Connect bypasses the public internet and establishes a direct, private connection between your on-premises network and AWS. This can be more cost-effective and consistent than transferring large volumes of data over the internet.