Aug 19, 2016
diff --git a/security/custom_provider.rst b/security/custom_provider.rst
 the configured user provider to return a user object for a given username.
 Symfony then checks whether the password of this user is correct and generates
 a security token so the user stays authenticated during the current session.
 Out of the box, Symfony has four user providers: ``in_memory``, ``entity``,
 Out of the box, Symfony has four user providers: ``memory``, ``entity``,
 ``ldap`` and ``chain``. In this entry you'll see how you can create your
 own user provider, which could be useful if your users are accessed via a
 custom database, a file, or - as shown in this example - a web service.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -9,7 +9,7 @@ When a user submits a username and password, the authentication layer asks
		the configured user provider to return a user object for a given username.
		Symfony then checks whether the password of this user is correct and generates
		a security token so the user stays authenticated during the current session.
		Out of the box, Symfony has four user providers: ``in_memory``, ``entity``,
		Out of the box, Symfony has four user providers: ``memory``, ``entity``,
		``ldap`` and ``chain``. In this entry you'll see how you can create your
		own user provider, which could be useful if your users are accessed via a
		custom database, a file, or - as shown in this example - a web service.
Expand Down