From 803b95c6a4756ca06756e7a554553d0c25d8034a Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Tue, 4 Dec 2007 06:16:28 +0000 Subject: [PATCH] Edited docs/request_response.txt changes from [6808] git-svn-id: http://code.djangoproject.com/svn/django/trunk@6881 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/request_response.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/request_response.txt b/docs/request_response.txt index 6fcad8ee3d2..2445b3e6b9e 100644 --- a/docs/request_response.txt +++ b/docs/request_response.txt @@ -560,10 +560,10 @@ Three things to note about 404 views: you must create a ``404.html`` template in the root of your template directory. The default 404 view will use that template for all 404 errors. The default 404 view will pass one variable - to the template: ``request_path``, which is the URL which - resulted in the 404. + to the template: ``request_path``, which is the URL that resulted + in the 404. - * If ``DEBUG`` is set to ``True`` (in your settings module) then your 404 + * If ``DEBUG`` is set to ``True`` (in your settings module), then your 404 view will never be used, and the traceback will be displayed instead. The 500 (server error) view