Reword

Author: javiereguiluz

deployment/proxies.rst

@@ -76,11 +76,12 @@ That's it! It's critical that you prevent traffic from all non-trusted sources.
 If you allow outside traffic, they could "spoof" their true IP address and
 other information.
 
-.. caution::
-
-    In case you are also using `CloudFront`_ or another reverse proxy on top of your load balancer, calling ``$request->server->get('REMOTE_ADDR')`` as in the above example won't be enough, as it will only whitelist the node sitting directly above your application (in this case your load balancer). You need to make sure you also append the IP addresses or ranges of any additional proxy to the array of trusted proxies. 
-    
-    In the case of `CloudFront`_, you can find the list of IP ranges `at this address <https://ip-ranges.amazonaws.com/ip-ranges.json>`_. 
+If you are also using a reverse proxy on top of your load balancer (e.g.
+`CloudFront`_), calling ``$request->server->get('REMOTE_ADDR')`` won't be
+enough, as it will only trust the node sitting directly above your application
+(in this case your load balancer). You also need to append the IP addresses or
+ranges of any additional proxy (e.g. `CloudFront IP ranges`_) to the array of
+trusted proxies.
 
 Custom Headers When Using a Reverse Proxy
 -----------------------------------------
@@ -100,3 +101,4 @@ In this case, you'll need to set the header ``X-Forwarded-Proto`` with the value
 
 .. _`security groups`: http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-security-groups.html
 .. _`CloudFront`: https://en.wikipedia.org/wiki/Amazon_CloudFront
+.. _`CloudFront IP ranges`: https://ip-ranges.amazonaws.com/ip-ranges.json