mirror of
https://github.com/django/django.git
synced 2025-10-09 18:12:39 +00:00
[1.7.x] Various documentation typo/spelling fixes
Errors detected by Topy (https://github.com/intgr/topy), all changes
verified by hand.
Backport of 11d453bcad
from master
This commit is contained in:
parent
4499c676ef
commit
ba1728dd9b
18 changed files with 18 additions and 19 deletions
|
@ -145,7 +145,7 @@ Handling errors in actions
|
|||
|
||||
If there are foreseeable error conditions that may occur while running your
|
||||
action, you should gracefully inform the user of the problem. This means
|
||||
handling exceptions and and using
|
||||
handling exceptions and using
|
||||
:meth:`django.contrib.admin.ModelAdmin.message_user` to display a user friendly
|
||||
description of the problem in the response.
|
||||
|
||||
|
|
|
@ -106,7 +106,7 @@ respectively).
|
|||
in the :doc:`sessions documentation </topics/http/sessions>` on
|
||||
how to enable sessions.
|
||||
|
||||
We will use the :class:`SessionWizardView` in all examples but is is completely
|
||||
We will use the :class:`SessionWizardView` in all examples but is completely
|
||||
fine to use the :class:`CookieWizardView` instead. As with your
|
||||
:class:`~django.forms.Form` classes, this :class:`WizardView` class can live
|
||||
anywhere in your codebase, but convention is to put it in :file:`views.py`.
|
||||
|
|
|
@ -739,7 +739,7 @@ systems and coordinate transformation::
|
|||
.. attribute:: z
|
||||
|
||||
Returns the Z coordinate of this point, or ``None`` if the
|
||||
the point does not have a Z coordinate::
|
||||
point does not have a Z coordinate::
|
||||
|
||||
>>> OGRGeometry('POINT (1 2 3)').z
|
||||
3.0
|
||||
|
|
|
@ -880,7 +880,7 @@ Returns WKB of the geometry in hexadecimal. Example::
|
|||
|
||||
.. attribute:: WKBWriter.byteorder
|
||||
|
||||
This property may be be set to change the byte-order of the geometry
|
||||
This property may be set to change the byte-order of the geometry
|
||||
representation.
|
||||
|
||||
=============== =================================================
|
||||
|
|
|
@ -793,7 +793,7 @@ Threaded option
|
|||
----------------
|
||||
|
||||
If you plan to run Django in a multithreaded environment (e.g. Apache using the
|
||||
the default MPM module on any modern operating system), then you **must** set
|
||||
default MPM module on any modern operating system), then you **must** set
|
||||
the ``threaded`` option of your Oracle database configuration to True::
|
||||
|
||||
'OPTIONS': {
|
||||
|
|
|
@ -174,7 +174,7 @@ RunSQL
|
|||
|
||||
RunSQL(sql, reverse_sql=None, state_operations=None, multiple=False)
|
||||
|
||||
Allows runnning of arbitrary SQL on the database - useful for more advanced
|
||||
Allows running of arbitrary SQL on the database - useful for more advanced
|
||||
features of database backends that Django doesn't support directly, like
|
||||
partial indexes.
|
||||
|
||||
|
|
|
@ -1025,7 +1025,7 @@ For a complete discussion on the usage of the following see the
|
|||
current point in time. Exactly what's returned depends on the value of
|
||||
:setting:`USE_TZ`:
|
||||
|
||||
* If :setting:`USE_TZ` is ``False``, this will be be a
|
||||
* If :setting:`USE_TZ` is ``False``, this will be a
|
||||
:ref:`naive <naive_vs_aware_datetimes>` datetime (i.e. a datetime
|
||||
without an associated timezone) that represents the current time
|
||||
in the system's local timezone.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue