mirror of
https://github.com/django/django.git
synced 2025-08-04 02:48:35 +00:00
[2.0.x] Fixed 'a'/'an' mix-ups in docs.
Backport of 617686e226
from master
This commit is contained in:
parent
f2d5417d3b
commit
8a6392e4c6
5 changed files with 6 additions and 6 deletions
|
@ -650,7 +650,7 @@ registered with any ``Admin`` instance::
|
|||
|
||||
This example sets up two admin sites. On the first site, the
|
||||
``Author`` and ``Publisher`` objects are exposed; ``Publisher``
|
||||
objects have an tabular inline showing books published by that
|
||||
objects have a tabular inline showing books published by that
|
||||
publisher. The second site exposes just publishers, without the
|
||||
inlines.
|
||||
|
||||
|
|
|
@ -227,7 +227,7 @@ This usage isn't particularly recommended as it makes it easier to accidentally
|
|||
introduce errors between the intended meaning of a match and the arguments
|
||||
of the view.
|
||||
|
||||
In either case, using only one style within an given regex is recommended. When
|
||||
In either case, using only one style within a given regex is recommended. When
|
||||
both styles are mixed, any unnamed groups are ignored and only named groups are
|
||||
passed to the view function.
|
||||
|
||||
|
|
|
@ -303,7 +303,7 @@ Advanced features of ``TransactionTestCase``
|
|||
recommended that you do not hard code primary key values in tests.
|
||||
|
||||
Using ``reset_sequences = True`` will slow down the test, since the primary
|
||||
key reset is an relatively expensive database operation.
|
||||
key reset is a relatively expensive database operation.
|
||||
|
||||
.. _testing-reusable-applications:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue