Merge branch '1.1'

* 1.1:
  Remove gendered pronouns

doc/providers/security.rst

@@ -165,9 +165,9 @@ Using a form to authenticate users is very similar to the above configuration.
 Instead of using the ``http`` setting, use the ``form`` one and define these
 two parameters:
 
-* **login_path**: The login path where the user is redirected when he is
-  accessing a secured area without being authenticated so that he can enter
-  his credentials;
+* **login_path**: The login path where the user is redirected when they are
+  accessing a secured area without being authenticated so that they can enter
+  their credentials;
 
 * **check_path**: The check URL used by Symfony to validate the credentials of
   the user.
@@ -377,7 +377,7 @@ parameter to any URL when logged in as a user who has the
 
 You can check that you are impersonating a user by checking the special
 ``ROLE_PREVIOUS_ADMIN``. This is useful for instance to allow the user to
-switch back to his primary account:
+switch back to their primary account:
 
 .. code-block:: jinja
 

doc/providers/session.rst

@@ -60,7 +60,7 @@ Usage
 -----
 
 The Session provider provides a ``session`` service. Here is an example that
-authenticates a user and creates a session for him::
+authenticates a user and creates a session for them::
 
     use Symfony\Component\HttpFoundation\Response;