Author: timo
Date: 2010-11-28 11:49:43 -0600 (Sun, 28 Nov 2010)
New Revision: 14735

Modified:
   django/trunk/docs/releases/1.0-porting-guide.txt
Log:
Fixed #14790 - Fix reST in 1.0 porting guide - thanks adamv.

Modified: django/trunk/docs/releases/1.0-porting-guide.txt
===================================================================
--- django/trunk/docs/releases/1.0-porting-guide.txt    2010-11-28 02:50:31 UTC 
(rev 14734)
+++ django/trunk/docs/releases/1.0-porting-guide.txt    2010-11-28 17:49:43 UTC 
(rev 14735)
@@ -373,7 +373,7 @@
   ``sender=None``
 
 * Make any custom signals you've declared into instances of
-  :class:`django.dispatch.Signal`` instead of anonymous objects.
+  :class:`django.dispatch.Signal` instead of anonymous objects.
 
 Here's quick summary of the code changes you'll need to make:
 
@@ -626,8 +626,8 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 ``django.http.HttpResponse.headers`` has been renamed to ``_headers`` and
-:class:`HttpResponse`` now supports containment checking directly. So use
-``if header in response:`` instead of ``if header in response.headers:``.
+:class:`~django.http.HttpResponse` now supports containment checking directly.
+So use ``if header in response:`` instead of ``if header in 
response.headers:``.
 
 Generic relations
 -----------------
@@ -661,7 +661,7 @@
 Running management commands from your code
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-:mod:`django.core.management`` has been greatly refactored.
+:mod:`django.core.management` has been greatly refactored.
 
 Calls to management services in your code now need to use
 ``call_command``. For example, if you have some test code that calls flush and

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to