From 3935b0f2634d200b122079eb7bf82d9cd4f4c511 Mon Sep 17 00:00:00 2001 From: Sylvain Bellemare Date: Tue, 5 Nov 2013 12:25:19 +0100 Subject: [PATCH] Removed no longer relevant word --- docs/topics/auth/customizing.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index a7240a8e6de..fa6075fac8d 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 ` above -- Django tries authenticating across +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.