Merge branch '4.4' into 5.2

* 4.4:
  Some minor rewords

Author: javiereguiluz

frontend/encore/babel.rst

@@ -24,7 +24,7 @@ Need to extend the Babel configuration further? The easiest way is via
             babelConfig.plugins.push('styled-jsx/babel');
         }, {
             // node_modules is not processed through Babel by default
-            // but you can whitelist specific modules to process
+            // but you can allow some specific modules to be processed
             includeNodeModules: ['foundation-sites'],
 
             // or completely control the exclude rule (note that you

reference/configuration/framework.rst

@@ -562,7 +562,7 @@ instance), the host might have been manipulated by an attacker.
 The Symfony :method:`Request::getHost() <Symfony\\Component\\HttpFoundation\\Request::getHost>`
 method might be vulnerable to some of these attacks because it depends on
 the configuration of your web server. One simple solution to avoid these
-attacks is to whitelist the hosts that your Symfony application can respond
+attacks is to configure a list of hosts that your Symfony application can respond
 to. That's the purpose of this ``trusted_hosts`` option. If the incoming
 request's hostname doesn't match one of the regular expressions in this list,
 the application won't respond and the user will receive a 400 response.

reference/constraints/Uuid.rst

@@ -4,7 +4,7 @@ UUID
 Validates that a value is a valid `Universally unique identifier (UUID)`_ per `RFC 4122`_.
 By default, this will validate the format according to the RFC's guidelines, but this can
 be relaxed to accept non-standard UUIDs that other systems (like PostgreSQL) accept.
-UUID versions can also be restricted using a whitelist.
+UUID versions can also be restricted using a list of allowed versions.
 
 ==========  ===================================================================
 Applies to  :ref:`property or method <validation-property-target>`

security.rst

@@ -1048,8 +1048,8 @@ like this:
   will have ``IS_AUTHENTICATED_REMEMBERED`` but will not have ``IS_AUTHENTICATED_FULLY``.
 
 * ``IS_AUTHENTICATED_ANONYMOUSLY``: *All* users (even anonymous ones) have
-  this - this is useful when *whitelisting* URLs to guarantee access - some
-  details are in :doc:`/security/access_control`.
+  this - this is useful when defining a list of URLs with no access restriction
+  - some details are in :doc:`/security/access_control`.
 
 * ``IS_ANONYMOUS``: *Only* anonymous users are matched by this attribute.