From e8161980347da5a68b4224d8a9ffc466630a796d Mon Sep 17 00:00:00 2001 From: Szczepan Cieślik Date: Sat, 22 Feb 2014 18:30:28 +0100 Subject: Fixed docs typos. --- docs/topics/testing/tools.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/topics/testing') diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index e31021eaef..a93ef39835 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -1255,7 +1255,7 @@ your test suite. :param empty_value: the expected clean output for inputs in ``empty_values``. For example, the following code tests that an ``EmailField`` accepts - "a@a.com" as a valid email address, but rejects "aaa" with a reasonable + ``a@a.com`` as a valid email address, but rejects ``aaa`` with a reasonable error message:: self.assertFieldOutput(EmailField, {'a@a.com': 'a@a.com'}, {'aaa': [u'Enter a valid email address.']}) @@ -1412,7 +1412,7 @@ your test suite. comparison is based on XML semantics. Similarly to :meth:`~SimpleTestCase.assertHTMLEqual`, the comparison is made on parsed content, hence only semantic differences are considered, not - syntax differences. When unvalid XML is passed in any parameter, an + syntax differences. When invalid XML is passed in any parameter, an ``AssertionError`` is always raised, even if both string are identical. Output in case of error can be customized with the ``msg`` argument. -- cgit v1.3