summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/db/multi-db.txt2
-rw-r--r--docs/topics/http/shortcuts.txt2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/db/multi-db.txt b/docs/topics/db/multi-db.txt
index 5a052d4a17..9a603b52fe 100644
--- a/docs/topics/db/multi-db.txt
+++ b/docs/topics/db/multi-db.txt
@@ -454,7 +454,7 @@ Exposing multiple databases in Django's admin interface
Django's admin doesn't have any explicit support for multiple
databases. If you want to provide an admin interface for a model on a
-database other than that that specified by your router chain, you'll
+database other than that specified by your router chain, you'll
need to write custom :class:`~django.contrib.admin.ModelAdmin` classes
that will direct the admin to use a specific database for content.
diff --git a/docs/topics/http/shortcuts.txt b/docs/topics/http/shortcuts.txt
index cc24560295..4a0fa58c41 100644
--- a/docs/topics/http/shortcuts.txt
+++ b/docs/topics/http/shortcuts.txt
@@ -24,7 +24,7 @@ introduce controlled coupling for convenience's sake.
:func:`render()` is the same as a call to
:func:`render_to_response()` with a `context_instance` argument that
- that forces the use of a :class:`~django.template.RequestContext`.
+ forces the use of a :class:`~django.template.RequestContext`.
Required arguments
------------------