From b3b541b68ea83164aee967539e4aa44cbdb88b6e Mon Sep 17 00:00:00 2001 From: Gary Wilson Jr Date: Tue, 31 Mar 2009 16:09:22 +0000 Subject: [1.0.X]: Fixed #10553 -- Corrected several uses of `URLconf` in documentation and comments, according to the Django style guide. Based on patch from rduffield. Backport of r10256 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@10257 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/howto/deployment/modpython.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/howto/deployment/modpython.txt') diff --git a/docs/howto/deployment/modpython.txt b/docs/howto/deployment/modpython.txt index 70f1e37749..14f0219421 100644 --- a/docs/howto/deployment/modpython.txt +++ b/docs/howto/deployment/modpython.txt @@ -58,12 +58,12 @@ be passed through to the mod_python handler in Django, via the ``PythonOption django.root ...`` line. The value set on that line (the last item) should match the string given in the ```` directive. The effect of this is that Django will automatically strip the ``/mysite`` string from the front -of any URLs before matching them against your ``URLConf`` patterns. If you -later move your site to live under ``/mysite2``, you will not have to change -anything except the ``django.root`` option in the config file. +of any URLs before matching them against your URLconf patterns. If you later +move your site to live under ``/mysite2``, you will not have to change anything +except the ``django.root`` option in the config file. When using ``django.root`` you should make sure that what's left, after the -prefix has been removed, begins with a slash. Your URLConf patterns that are +prefix has been removed, begins with a slash. Your URLconf patterns that are expecting an initial slash will then work correctly. In the above example, since we want to send things like ``/mysite/admin/`` to ``/admin/``, we need to remove the string ``/mysite`` from the beginning, so that is the -- cgit v1.3