p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[1.8.x] Fixed doc typos. 

Backport of e42a720ba2 from master
This commit is contained in:
Floris den Hengst 2015-03-07 17:34:33 +01:00 committed by Tim Graham
parent 5b91802718
commit bd36f2d432
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/applications.txt
View File

@ -243,7 +243,7 @@ Methods
In the usual initialization process, the ``ready`` method is only called In the usual initialization process, the ``ready`` method is only called
once by Django. But in some corner cases, particularly in tests which once by Django. But in some corner cases, particularly in tests which
are fiddling with installed applications, ``ready`` might be called more are fiddling with installed applications, ``ready`` might be called more
than once. In that case, either write idempotents methods, or put a flag than once. In that case, either write idempotent methods, or put a flag
on your ``AppConfig`` classes to prevent re-running code which should on your ``AppConfig`` classes to prevent re-running code which should
be executed exactly one time. be executed exactly one time.

2
docs/ref/contrib/admin/actions.txt
View File

@ -70,7 +70,7 @@ Writing action functions
------------------------ ------------------------
First, we'll need to write a function that gets called when the action is First, we'll need to write a function that gets called when the action is
trigged from the admin. Action functions are just regular functions that take triggered from the admin. Action functions are just regular functions that take
three arguments: three arguments:
* The current :class:`ModelAdmin` * The current :class:`ModelAdmin`

2
docs/ref/contrib/gis/gdal.txt
View File

@ -6,7 +6,7 @@ GDAL API
:synopsis: GeoDjango's high-level interface to the GDAL library. :synopsis: GeoDjango's high-level interface to the GDAL library.
`GDAL`__ stands for **Geospatial Data Abstraction Library**, `GDAL`__ stands for **Geospatial Data Abstraction Library**,
and is a veritable "swiss army knife" of GIS data functionality. A subset and is a veritable "Swiss army knife" of GIS data functionality. A subset
of GDAL is the `OGR`__ Simple Features Library, which specializes of GDAL is the `OGR`__ Simple Features Library, which specializes
in reading and writing vector geographic data in a variety of standard in reading and writing vector geographic data in a variety of standard
formats. formats.

4
docs/ref/files/uploads.txt
View File

@ -111,8 +111,8 @@ Subclasses of ``UploadedFile`` include:
A file uploaded into memory (i.e. stream-to-memory). This class is used A file uploaded into memory (i.e. stream-to-memory). This class is used
by the :class:`~django.core.files.uploadhandler.MemoryFileUploadHandler`. by the :class:`~django.core.files.uploadhandler.MemoryFileUploadHandler`.
Built-in upload handers Built-in upload handlers
======================= ========================
.. module:: django.core.files.uploadhandler .. module:: django.core.files.uploadhandler
:synopsis: Django's handlers for file uploads. :synopsis: Django's handlers for file uploads.

2
docs/topics/db/sql.txt
View File

@ -56,7 +56,7 @@ options that make it very powerful.
.. admonition:: Model table names .. admonition:: Model table names
Where'd the name of the ``Person`` table come from in that example? Where did the name of the ``Person`` table come from in that example?
By default, Django figures out a database table name by joining the By default, Django figures out a database table name by joining the
model's "app label" -- the name you used in ``manage.py startapp`` -- to model's "app label" -- the name you used in ``manage.py startapp`` -- to