summaryrefslogtreecommitdiff
path: root/docs/intro
diff options
context:
space:
mode:
Diffstat (limited to 'docs/intro')
-rw-r--r--docs/intro/contributing.txt2
-rw-r--r--docs/intro/tutorial05.txt2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/intro/contributing.txt b/docs/intro/contributing.txt
index a343814c02..c94038bc56 100644
--- a/docs/intro/contributing.txt
+++ b/docs/intro/contributing.txt
@@ -281,7 +281,7 @@ correctly in a couple different situations.
computer programming, so there's lots of information out there:
* A good first look at writing tests for Django can be found in the
- documentation on :doc:`Testing Django applications</topics/testing/>`.
+ documentation on :doc:`Testing Django applications </topics/testing/overview>`.
* Dive Into Python (a free online book for beginning Python developers)
includes a great `introduction to Unit Testing`__.
* After reading those, if you want something a little meatier to sink
diff --git a/docs/intro/tutorial05.txt b/docs/intro/tutorial05.txt
index 163b7cdd0f..d1f95176ed 100644
--- a/docs/intro/tutorial05.txt
+++ b/docs/intro/tutorial05.txt
@@ -632,7 +632,7 @@ a piece of code, it usually means that code should be refactored or removed.
Coverage will help to identify dead code. See
:ref:`topics-testing-code-coverage` for details.
-:doc:`Testing Django applications </topics/testing>` has comprehensive
+:doc:`Testing Django applications </topics/testing/index>` has comprehensive
information about testing.
.. _Selenium: http://seleniumhq.org/