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:32:26 -0500 |
| commit | b3da4cc0925b5d72701ea254ec8197d0f8b85210 (patch) | |
| tree | 692340c71c9f147a2ed0c90f7c3745ed5ee86c28 /docs | |
| parent | c89a56d9fe708925740d603d00261f189824e33a (diff) | |
[1.6.x] Removed no longer relevant word
Backport of 3935b0f263 from master
Diffstat (limited to 'docs')
| -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 d5bc9d96ba..29c874560d 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. |