From 7a30b4e03ae8848792bd114741bc2fb175d280a4 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Fri, 1 Jun 2007 06:19:01 +0000 Subject: unicode: Merged from trunk up to [5398]. git-svn-id: http://code.djangoproject.com/svn/django/branches/unicode@5399 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/testing.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/testing.txt b/docs/testing.txt index d36d5204e2..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. @@ -579,7 +579,7 @@ control the particular collation used by the test database with the ``TEST_DATABASE_COLLATION`` setting. Refer to the settings_ documentation for details of these advanced settings. -.. _settings: ../settings.txt +.. _settings: ../settings/ The test database is created by the user in the ``DATABASE_USER`` setting. This user needs to have sufficient privileges to create a new database on the -- cgit v1.3