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

Fixed typos in docs.

This commit is contained in:
Jakub Wilk 2016-03-13 19:47:58 +01:00
parent 91f87b8f91
commit 402da9ab7b
6 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/internals/howto-release-django.txt
View File

@ -365,7 +365,7 @@ You're almost done! All that's left to do now is:
New stable branch tasks New stable branch tasks
======================= =======================
There are several items to do in the time following a the creation of a new There are several items to do in the time following the creation of a new
stable branch (often following an alpha release). Some of these tasks don't stable branch (often following an alpha release). Some of these tasks don't
need to be done by the releaser. need to be done by the releaser.

2
docs/ref/utils.txt
View File

@ -155,7 +155,7 @@ The functions defined in this module share the following properties:
decorate methods or classes; in the latter case, ``name`` is the name decorate methods or classes; in the latter case, ``name`` is the name
of the method to be decorated and is required. of the method to be decorated and is required.
``decorator`` may also be a a list or tuple of functions. They are wrapped ``decorator`` may also be a list or tuple of functions. They are wrapped
in reverse order so that the call order is the order in which the functions in reverse order so that the call order is the order in which the functions
appear in the list/tuple. appear in the list/tuple.

2
docs/releases/1.0.txt
View File

@ -5,7 +5,7 @@ Django 1.0 release notes
Welcome to Django 1.0! Welcome to Django 1.0!
We've been looking forward to this moment for over three years, and it's finally We've been looking forward to this moment for over three years, and it's finally
here. Django 1.0 represents a the largest milestone in Django's development to here. Django 1.0 represents the largest milestone in Django's development to
date: a Web framework that a group of perfectionists can truly be proud of. date: a Web framework that a group of perfectionists can truly be proud of.
Django 1.0 represents over three years of community development as an Open Django 1.0 represents over three years of community development as an Open

2
docs/releases/security.txt
View File

@ -202,7 +202,7 @@ Versions affected
September 9, 2011 - CVE-2011-4137 September 9, 2011 - CVE-2011-4137
--------------------------------- ---------------------------------
`CVE-2011-4137 <https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-4137&cid=2>`_: Denial-of-service via via ``URLField.verify_exists``. `Full description <https://www.djangoproject.com/weblog/2011/sep/09/security-releases-issued/>`__ `CVE-2011-4137 <https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-4137&cid=2>`_: Denial-of-service via ``URLField.verify_exists``. `Full description <https://www.djangoproject.com/weblog/2011/sep/09/security-releases-issued/>`__
Versions affected Versions affected
~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~

2
docs/topics/conditional-view-processing.txt
View File

@ -167,7 +167,7 @@ For example, consider the following exchange between the client and server:
the version it is trying to update. the version it is trying to update.
4. Server checks to see if the resource has changed, by computing the ETag 4. Server checks to see if the resource has changed, by computing the ETag
the same way it does for a ``GET`` request (using the same function). the same way it does for a ``GET`` request (using the same function).
If the resource *has* changed, it will return a 412 status code code, If the resource *has* changed, it will return a 412 status code,
meaning "precondition failed". meaning "precondition failed".
5. Client sends a ``GET`` request to ``/foo/``, after receiving a 412 5. Client sends a ``GET`` request to ``/foo/``, after receiving a 412
response, to retrieve an updated version of the content before updating response, to retrieve an updated version of the content before updating

2
docs/topics/performance.txt
View File

@ -171,7 +171,7 @@ final steps towards producing well-performing code, not a shortcut.
:class:`~django.utils.functional.cached_property` :class:`~django.utils.functional.cached_property`
------------------------------------------------- -------------------------------------------------
It's common to have to call a class instances's method more than once. If It's common to have to call a class instance's method more than once. If
that function is expensive, then doing so can be wasteful. that function is expensive, then doing so can be wasteful.
Using the :class:`~django.utils.functional.cached_property` decorator saves the Using the :class:`~django.utils.functional.cached_property` decorator saves the