summaryrefslogtreecommitdiff
path: root/docs/intro/tutorial01.txt
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2013-12-30 17:59:18 -0500
committerTim Graham <timograham@gmail.com>2013-12-30 17:59:18 -0500
commitec020cab7ef4b1943a8fe9a4d6872f7e874db707 (patch)
tree25c27b83e3dde8f0667a2c047220c7dd4cfe63f2 /docs/intro/tutorial01.txt
parentdf075c74896b63ff39c250bb52a1f168265dfeee (diff)
Fixed a broken link in docs/intro/tutorial01.txt.
Diffstat (limited to 'docs/intro/tutorial01.txt')
-rw-r--r--docs/intro/tutorial01.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt
index 0bd3d0abaf..3fa07e132c 100644
--- a/docs/intro/tutorial01.txt
+++ b/docs/intro/tutorial01.txt
@@ -696,7 +696,7 @@ automatically-generated admin.
:meth:`~django.db.models.Model.__unicode__` and converts the result to a
UTF-8 bytestring. This means that ``unicode(p)`` will return a Unicode
string, and ``str(p)`` will return a bytestring, with characters encoded
- as UTF-8. Python does the opposite: :class:`object` has a ``__unicode__``
+ as UTF-8. Python does the opposite: ``object`` has a ``__unicode__``
method that calls ``__str__`` and interprets the result as an ASCII
bytestring. This difference can create confusion.