summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAdrian Holovaty <adrian@holovaty.com>2007-08-15 05:30:23 +0000
committerAdrian Holovaty <adrian@holovaty.com>2007-08-15 05:30:23 +0000
commit4f62b0a19381f80944f5358ccfb4f54a13c5bb69 (patch)
tree990f2ec25c693adeb0ce9a47f3a2924309bd6c13 /docs
parent3bfda4fa621a771d0d6c16e5db605226fa2a546a (diff)
Fixed some ReST errors in docs/testing.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5891 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/testing.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/testing.txt b/docs/testing.txt
index 0bd53f15d7..99fae15ec4 100644
--- a/docs/testing.txt
+++ b/docs/testing.txt
@@ -213,7 +213,7 @@ For developers new to testing, however, this choice can seem confusing. Here,
then, are a few key differences to help you decide which approach is right for
you:
- * If you've been using Python for a while, ``doctest`` will probably feel
+ * If you've been using Python for a while, ``doctest`` will probably feel
more "pythonic". It's designed to make writing tests as easy as possible,
so it requires no overhead of writing classes or methods. You simply put
tests in docstrings. This has the added advantage of serving as
@@ -561,7 +561,7 @@ The ``get()`` and ``post()`` methods both return a ``Response`` object. This
Django views; this object is simpler and has some additional data useful for
tests.
-Specifically, a ``Response`` object has the following attributes::
+Specifically, a ``Response`` object has the following attributes:
=============== ==========================================================
Attribute Description