[1.2.X] Fixed #15710 - removed "that that" typos.
Backport of r15942 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@15943 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
ce9b216882
commit
d935b232a2
|
@ -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.
|
||||
|
||||
|
|
|
@ -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
|
||||
------------------
|
||||
|
|
Loading…
Reference in New Issue