From 8a8c0ed0f9e915296fefa716628f0d9ea55cc770 Mon Sep 17 00:00:00 2001
From: Alex Gaynor <alex.gaynor@gmail.com>
Date: Sun, 24 Oct 2010 17:29:24 +0000
Subject: [PATCH] Fixed #14551 -- corrected a type in the remote user auth
 documentation.  Thanks to mag for the report and fix.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@14344 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/howto/auth-remote-user.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/howto/auth-remote-user.txt b/docs/howto/auth-remote-user.txt
index 9dbde29e5c..deab794cb1 100644
--- a/docs/howto/auth-remote-user.txt
+++ b/docs/howto/auth-remote-user.txt
@@ -2,7 +2,7 @@
 Authentication using ``REMOTE_USER``
 ====================================
 
-.. currentmodule:: django.contrib.backends
+.. currentmodule:: django.contrib.auth.backends
 
 This document describes how to make use of external authentication sources
 (where the Web server sets the ``REMOTE_USER`` environment variable) in your
@@ -68,7 +68,7 @@ If your authentication mechanism uses a custom HTTP header and not
 ``RemoteUserBackend``
 =====================
 
-.. class:: django.contrib.backends.RemoteUserBackend
+.. class:: django.contrib.auth.backends.RemoteUserBackend
 
 If you need more control, you can create your own authentication backend
 that inherits from ``RemoteUserBackend`` and overrides certain parts: