summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
authorJames Bennett <ubernostrum@gmail.com>2010-03-07 00:52:11 +0000
committerJames Bennett <ubernostrum@gmail.com>2010-03-07 00:52:11 +0000
commit8a8366d2faf2de41ac3072f80fd522dc273cf381 (patch)
treee83847f6eb24c95635685c5fc7882003c463540c /docs/topics
parent55bcc8ac3013efb852d71f937f12132bc3371780 (diff)
[1.1.X] Fixed #13048: Corrected typo in email documentation. Backport of [12694] from trunk.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@12695 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/email.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/topics/email.txt b/docs/topics/email.txt
index c80a035b53..ebb4e57a39 100644
--- a/docs/topics/email.txt
+++ b/docs/topics/email.txt
@@ -354,11 +354,11 @@ send out, you could send this with::
Testing e-mail sending
----------------------
-The are times when you do not want Django to send e-mails at all. For example,
-while developing a website, you probably don't want to send out thousands of
-e-mails -- but you may want to validate that e-mails will be sent to the right
-people under the right conditions, and that those e-mails will contain the
-correct content.
+There are times when you do not want Django to send e-mails at
+all. For example, while developing a website, you probably don't want
+to send out thousands of e-mails -- but you may want to validate that
+e-mails will be sent to the right people under the right conditions,
+and that those e-mails will contain the correct content.
The easiest way to test your project's use of e-mail is to use a "dumb" e-mail
server that receives the e-mails locally and displays them to the terminal,