summaryrefslogtreecommitdiff
path: root/docs/topics/auth/customizing.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics/auth/customizing.txt')
-rw-r--r--docs/topics/auth/customizing.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt
index 9ae30b4b25..3c73783b24 100644
--- a/docs/topics/auth/customizing.txt
+++ b/docs/topics/auth/customizing.txt
@@ -64,7 +64,7 @@ That's the basic authentication backend that checks the Django users database
and queries the built-in permissions. It does not provide protection against
brute force attacks via any rate limiting mechanism. You may either implement
your own rate limiting mechanism in a custom auth backend, or use the
-mechanisms provided by most Web servers.
+mechanisms provided by most web servers.
The order of :setting:`AUTHENTICATION_BACKENDS` matters, so if the same
username and password is valid in multiple backends, Django will stop