From 8d3026bd9412a85f9e915aadf27745b0ec317e6e Mon Sep 17 00:00:00 2001
From: Adrian Holovaty <adrian@holovaty.com>
Date: Thu, 31 May 2007 04:30:40 +0000
Subject: [PATCH] Fixed #4439 -- Fixed typo in docs/testing.txt. Thanks, hayley

git-svn-id: http://code.djangoproject.com/svn/django/trunk@5387 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/testing.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/testing.txt b/docs/testing.txt
index 4a6d5694f5..dedb1e15a8 100644
--- a/docs/testing.txt
+++ b/docs/testing.txt
@@ -147,7 +147,7 @@ doctests or unit tests are right for you.
 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
 there's no overhead of writing classes or methods; you simply put tests in
-docstrings. This gives the added advantage of given your modules automatic
+docstrings. This gives the added advantage of giving your modules automatic
 documentation -- well-written doctests can kill both the documentation and the
 testing bird with a single stone.