Reworded

Author: javiereguiluz

deployment/proxies.rst

@@ -31,9 +31,8 @@ and what headers your reverse proxy uses to send information::
 
     // tell Symfony about your reverse proxy
     Request::setTrustedProxies(
-        // you can use IP address, IP address ranges or the 'REMOTE_ADDR' string,
-        // which is replaced at run time by the $_SERVER['REMOTE_ADDR'] env var
-        ['192.0.0.1', '10.0.0.0/8', 'REMOTE_ADDR'],
+        // the IP address (or range) of your proxy
+        ['192.0.0.1', '10.0.0.0/8'],
 
         // trust *all* "X-Forwarded-*" headers
         Request::HEADER_X_FORWARDED_ALL
@@ -45,10 +44,6 @@ and what headers your reverse proxy uses to send information::
         // Request::HEADER_X_FORWARDED_AWS_ELB
     );
 
-.. versionadded:: 4.4
-
-    The support for the ``REMOTE_ADDR`` env var was introduced in Symfony 4.4.
-
 The Request object has several ``Request::HEADER_*`` constants that control exactly
 *which* headers from your reverse proxy are trusted. The argument is a bit field,
 so you can also pass your own value (e.g. ``0b00110``).
@@ -71,7 +66,7 @@ In this case, you'll need to - *very carefully* - trust *all* proxies.
        // ...
        Request::setTrustedProxies(
            // trust *all* requests (the 'REMOTE_ADDR' string is replaced at
-           // run time by the $_SERVER['REMOTE_ADDR'] env var)
+           // run time by $_SERVER['REMOTE_ADDR'])
            ['127.0.0.1', 'REMOTE_ADDR'],
 
            // if you're using ELB, otherwise use a constant from above
@@ -80,7 +75,7 @@ In this case, you'll need to - *very carefully* - trust *all* proxies.
 
 .. versionadded:: 4.4
 
-    The support for the ``REMOTE_ADDR`` env var was introduced in Symfony 4.4.
+    The support for the ``REMOTE_ADDR`` option was introduced in Symfony 4.4.
 
 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