AWS elasticloadbalancing documentation change
Summary
Replaced 'to receive' with 'in order to receive' in a sentence about targets not needing public IPs.
Security assessment
Grammatical edit with no impact on security content. The security principle (using private IPs for targets) remains identical.
Diff
diff --git a/elasticloadbalancing/latest/userguide/infrastructure-security.md b/elasticloadbalancing/latest/userguide/infrastructure-security.md index 0e1e2dbd0..972e8dcd9 100644 --- a//elasticloadbalancing/latest/userguide/infrastructure-security.md +++ b//elasticloadbalancing/latest/userguide/infrastructure-security.md @@ -28 +28 @@ When you create a load balancer in a VPC, it can be either internet-facing or in -Your load balancer sends requests to its registered targets using private IP addresses. Therefore, your targets do not need public IP addresses to receive requests from a load balancer. +Your load balancer sends requests to its registered targets using private IP addresses. Therefore, your targets do not need public IP addresses in order to receive requests from a load balancer.