From bc52fdc44657723f633a1753d45f045298a92d44 Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Fri, 19 Jan 2007 03:18:36 +0000 Subject: [PATCH] Fixed #3317 -- Fixed typos in docs/testing.txt. Thanks for the patch, Marc Fargas git-svn-id: http://code.djangoproject.com/svn/django/trunk@4349 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/testing.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/testing.txt b/docs/testing.txt index 61b34e8c83..7618aaea66 100644 --- a/docs/testing.txt +++ b/docs/testing.txt @@ -244,11 +244,11 @@ can be invoked on the ``Client`` instance. ``login(path, username, password)`` In a production site, it is likely that some views will be protected with - the @login_required URL provided by ``django.contrib.auth``. Interacting + the @login_required decorator provided by ``django.contrib.auth``. Interacting with a URL that has been login protected is a slightly complex operation, - so the Test Client provides a simple URL to automate the login process. A + so the Test Client provides a simple method to automate the login process. A call to ``login()`` stimulates the series of GET and POST calls required - to log a user into a @login_required protected URL. + to log a user into a @login_required protected view. If login is possible, the final return value of ``login()`` is the response that is generated by issuing a GET request on the protected URL. If login