Fixed #15710 - removed "that that" typos.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15942 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Timo Graham 2011-03-29 10:24:42 +00:00
parent 6a25d90e49
commit 99b2728b74
2 changed files with 2 additions and 2 deletions

View File

@ -454,7 +454,7 @@ Exposing multiple databases in Django's admin interface
Django's admin doesn't have any explicit support for multiple 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 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 need to write custom :class:`~django.contrib.admin.ModelAdmin` classes
that will direct the admin to use a specific database for content. that will direct the admin to use a specific database for content.

View File

@ -24,7 +24,7 @@ introduce controlled coupling for convenience's sake.
:func:`render()` is the same as a call to :func:`render()` is the same as a call to
:func:`render_to_response()` with a `context_instance` argument that :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 Required arguments
------------------ ------------------