From 9ad98054db2dd2a636e3b7f0a2fb28b09738500c Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Tue, 23 Jan 2007 02:11:33 +0000 Subject: [PATCH] Fixed small inconsistency in docs/url_dispatch.txt 'New in Django development version' text git-svn-id: http://code.djangoproject.com/svn/django/trunk@4395 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/url_dispatch.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/url_dispatch.txt b/docs/url_dispatch.txt index 4991557859..8ad9cb0e73 100644 --- a/docs/url_dispatch.txt +++ b/docs/url_dispatch.txt @@ -393,7 +393,7 @@ to pass metadata and options to views. Passing extra options to ``include()`` -------------------------------------- -**New in the Django development version.** +**New in Django development version.** Similarly, you can pass extra options to ``include()``. When you pass extra options to ``include()``, *each* line in the included URLconf will be passed @@ -435,7 +435,7 @@ every view in the the included URLconf accepts the extra options you're passing. Passing callable objects instead of strings =========================================== -**New in the Django development version.** +**New in Django development version.** Some developers find it more natural to pass the actual Python function object rather than a string containing the path to its module. This alternative is