Fixed #4668, #4669, #4670, #4671 -- Fixed a group of ReST markup errors. Thanks, Richard House.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@5537 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-06-25 16:11:32 +00:00
parent 17145eef4c
commit 85f6f15263
5 changed files with 6 additions and 5 deletions

View File

@ -122,6 +122,7 @@ answer newbie questions, and generally made Django that much better:
Ian Holsman <http://feh.holsman.net/> Ian Holsman <http://feh.holsman.net/>
Kieran Holland <http://www.kieranholland.com> Kieran Holland <http://www.kieranholland.com>
Sung-Jin Hong <serialx.net@gmail.com> Sung-Jin Hong <serialx.net@gmail.com>
Richard House <Richard.House@i-logue.com>
Robert Rock Howard <http://djangomojo.com/> Robert Rock Howard <http://djangomojo.com/>
Jason Huggins <http://www.jrandolph.com/blog/> Jason Huggins <http://www.jrandolph.com/blog/>
Hyun Mi Ae Hyun Mi Ae

View File

@ -325,7 +325,7 @@ Manually checking a user's password
If you'd like to manually authenticate a user by comparing a If you'd like to manually authenticate a user by comparing a
plain-text password to the hashed password in the database, use the plain-text password to the hashed password in the database, use the
convenience function `django.contrib.auth.models.check_password`. It convenience function ``django.contrib.auth.models.check_password``. It
takes two arguments: the plain-text password to check, and the full takes two arguments: the plain-text password to check, and the full
value of a user's ``password`` field in the database to check against, value of a user's ``password`` field in the database to check against,
and returns ``True`` if they match, ``False`` otherwise. and returns ``True`` if they match, ``False`` otherwise.

View File

@ -104,7 +104,7 @@ Lawrence, Kansas, USA.
`Wilson Miner`_ `Wilson Miner`_
Wilson's design-fu makes us all look like rock stars. By day, he's an Wilson's design-fu makes us all look like rock stars. By day, he's an
interactive designer for `Apple`. Don't ask him what he's working on, or interactive designer for `Apple`_. Don't ask him what he's working on, or
he'll have to kill you. He lives in San Francisco. he'll have to kill you. He lives in San Francisco.
On IRC, Wilson goes by ``wilsonian``. On IRC, Wilson goes by ``wilsonian``.

View File

@ -754,10 +754,10 @@ If the results are paginated, the context will contain these extra variables:
* ``previous``: The previous page number, as an integer. This is 1-based. * ``previous``: The previous page number, as an integer. This is 1-based.
* `last_on_page`: The number of the * ``last_on_page``: The number of the
last result on the current page. This is 1-based. last result on the current page. This is 1-based.
* `first_on_page`: The number of the * ``first_on_page``: The number of the
first result on the current page. This is 1-based. first result on the current page. This is 1-based.
* ``pages``: The total number of pages, as an integer. * ``pages``: The total number of pages, as an integer.

View File

@ -342,7 +342,7 @@ If ``TEMPLATE_CONTEXT_PROCESSORS`` contains this processor, every
* ``user`` -- An ``auth.User`` instance representing the currently * ``user`` -- An ``auth.User`` instance representing the currently
logged-in user (or an ``AnonymousUser`` instance, if the client isn't logged-in user (or an ``AnonymousUser`` instance, if the client isn't
logged in). See the `user authentication docs`. logged in). See the `user authentication docs`_.
* ``messages`` -- A list of messages (as strings) for the currently * ``messages`` -- A list of messages (as strings) for the currently
logged-in user. Behind the scenes, this calls logged-in user. Behind the scenes, this calls