Added some sphinx cross-reference links to the built-in template tags and filters in multiple areas of the documentation. Also fixed a few minor inconsistencies and did a little PEP8 cleanup while I was at it.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16922 bcc190cf-cafb-0310-a4f2-bffc1f526a37

2 files changed, 10 insertions, 9 deletions

diff --git a/docs/intro/tutorial03.txt b/docs/intro/tutorial03.txt
index 108d55c23c..23353a277a 100644
--- a/docs/intro/tutorial03.txt
+++ b/docs/intro/tutorial03.txt
@@ -420,9 +420,10 @@ on the object ``poll``. Failing that, it tries an attribute lookup -- which
 works, in this case. If attribute lookup had failed, it would've tried a
 list-index lookup.
 
-Method-calling happens in the ``{% for %}`` loop: ``poll.choice_set.all`` is
-interpreted as the Python code ``poll.choice_set.all()``, which returns an
-iterable of Choice objects and is suitable for use in the ``{% for %}`` tag.
+Method-calling happens in the :ttag:`{% for %}<for>` loop:
+``poll.choice_set.all`` is interpreted as the Python code
+``poll.choice_set.all()``, which returns an iterable of Choice objects and is
+suitable for use in the :ttag:`{% for %}<for>` tag.
 
 See the :doc:`template guide </topics/templates>` for more about templates.
 
diff --git a/docs/intro/tutorial04.txt b/docs/intro/tutorial04.txt
index f0d2abc191..2763850ecd 100644
--- a/docs/intro/tutorial04.txt
+++ b/docs/intro/tutorial04.txt
@@ -49,13 +49,13 @@ A quick rundown:
       data), we need to worry about Cross Site Request Forgeries.
       Thankfully, you don't have to worry too hard, because Django comes with
       a very easy-to-use system for protecting against it. In short, all POST
-      forms that are targeted at internal URLs should use the ``{% csrf_token %}``
-      template tag.
+      forms that are targeted at internal URLs should use the
+      :ttag:`{% csrf_token %}<csrf_token>` template tag.
 
-The ``{% csrf_token %}`` tag requires information from the request object, which
-is not normally accessible from within the template context. To fix this, a
-small adjustment needs to be made to the ``detail`` view, so that it looks like
-the following::
+The :ttag:`{% csrf_token %}<csrf_token>` tag requires information from the
+request object, which is not normally accessible from within the template
+context. To fix this, a small adjustment needs to be made to the ``detail``
+view, so that it looks like the following::
 
     from django.template import RequestContext
     # ...