From 7988a4858357bb39b14af36ba0b5b5ad7d89989d Mon Sep 17 00:00:00 2001
From: Adrian Holovaty <adrian@holovaty.com>
Date: Tue, 24 Oct 2006 16:23:05 +0000
Subject: [PATCH] Made small edits to docs/templates_python.txt

git-svn-id: http://code.djangoproject.com/svn/django/trunk@3920 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/templates_python.txt | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/templates_python.txt b/docs/templates_python.txt
index 81e7d45133..ae2582d7b8 100644
--- a/docs/templates_python.txt
+++ b/docs/templates_python.txt
@@ -312,18 +312,18 @@ optional, third positional argument, ``processors``. In this example, the
         }, [ip_address_processor])
 
 Note::
-    If you are using Django's ``render_to_response()`` shortcut to populate a
+    If you're using Django's ``render_to_response()`` shortcut to populate a
     template with the contents of a dictionary, your template will be passed a
-    ``Context`` instance by default (not a ``RequestContext``). If you wish to
-    use a ``RequestContext`` in your template rendering, you need to pass an
-    optional third argument to ``render_to_response()``: a ``RequestContext``
+    ``Context`` instance by default (not a ``RequestContext``). To use a
+    ``RequestContext`` in your template rendering, pass an optional third
+    argument to ``render_to_response()``: a ``RequestContext``
     instance. Your code might look like this::
 
         def some_view(request):
             # ...
             return render_to_response('my_template'html',
                                       my_data_dictionary,
-                                      context_instance = RequestContext(request))
+                                      context_instance=RequestContext(request))
 
 Here's what each of the default processors does:
 
@@ -1092,7 +1092,7 @@ Configuring the template system in standalone mode
 .. note::
 
     This section is only of interest to people trying to use the template
-    system as an output component in another application. If you are using the
+    system as an output component in another application. If you're using the
     template system as part of a Django application, nothing here applies to
     you.
 
@@ -1109,7 +1109,7 @@ described in the `settings file`_ documentation. Simply import the appropriate
 pieces of the templating system and then, *before* you call any of the
 templating functions, call ``django.conf.settings.configure()`` with any
 settings you wish to specify. You might want to consider setting at least
-``TEMPLATE_DIRS`` (if you are going to use template loaders),
+``TEMPLATE_DIRS`` (if you're going to use template loaders),
 ``DEFAULT_CHARSET`` (although the default of ``utf-8`` is probably fine) and
 ``TEMPLATE_DEBUG``. All available settings are described in the
 `settings documentation`_, and any setting starting with *TEMPLATE_*