diff options
| author | Sylvain Bellemare <sbellem@gmail.com> | 2013-11-05 12:25:19 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-11-07 09:31:44 -0500 |
| commit | 3935b0f2634d200b122079eb7bf82d9cd4f4c511 (patch) | |
| tree | a60332c573cd33691df5408d6e0abf23c3364772 | |
| parent | 7be638390e18fcbfaaed638f9908673360c280d3 (diff) | |
Removed no longer relevant word
| -rw-r--r-- | docs/topics/auth/customizing.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index a7240a8e6d..fa6075fac8 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -47,7 +47,7 @@ Specifying authentication backends Behind the scenes, Django maintains a list of "authentication backends" that it checks for authentication. When somebody calls :func:`django.contrib.auth.authenticate()` -- as described in :ref:`How to log -a user in <how-to-log-a-user-in>` above -- Django tries authenticating across +a user in <how-to-log-a-user-in>` -- Django tries authenticating across all of its authentication backends. If the first authentication method fails, Django tries the second one, and so on, until all backends have been attempted. |