diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt index 3c71f8f004..f0b64ae1cb 100644 --- a/docs/howto/custom-model-fields.txt +++ b/docs/howto/custom-model-fields.txt @@ -696,7 +696,7 @@ existing conversion code:: return self.get_prep_value(value) Some general advice --------------------- +------------------- Writing a custom field can be a tricky process, particularly if you're doing complex conversions between your Python types and your database and @@ -737,7 +737,7 @@ told to use it. To do so, simply assign the new ``File`` subclass to the special ``attr_class`` attribute of the ``FileField`` subclass. A few suggestions ------------------- +----------------- In addition to the above details, there are a few guidelines which can greatly improve the efficiency and readability of the field's code. diff --git a/docs/intro/tutorial03.txt b/docs/intro/tutorial03.txt index 2d1104d3d7..6569f0533d 100644 --- a/docs/intro/tutorial03.txt +++ b/docs/intro/tutorial03.txt @@ -415,7 +415,7 @@ template (or templates) you would change it in ``polls/urls.py``:: ... Namespacing URL names -====================== +===================== The tutorial project has just one app, ``polls``. In real Django projects, there might be five, ten, twenty apps or more. How does Django differentiate diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 50886d3e84..67307a9bc8 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -886,7 +886,7 @@ both as empty strings. Django will use a different connect descriptor depending on that choice. Threaded option ----------------- +--------------- If you plan to run Django in a multithreaded environment (e.g. Apache using the default MPM module on any modern operating system), then you **must** set diff --git a/docs/releases/1.0-porting-guide.txt b/docs/releases/1.0-porting-guide.txt index 72f01495a5..8dded73236 100644 --- a/docs/releases/1.0-porting-guide.txt +++ b/docs/releases/1.0-porting-guide.txt @@ -298,7 +298,7 @@ Old (0.96) New (1.0) ===================== ===================== Work with file fields using the new API -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The internal implementation of :class:`django.db.models.FileField` have changed. A visible result of this is that the way you access special attributes (URL, @@ -644,7 +644,7 @@ Testing ------- :meth:`django.test.Client.login` has changed -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Old (0.96):: diff --git a/docs/releases/1.1.txt b/docs/releases/1.1.txt index 1ef5667336..61da881ddf 100644 --- a/docs/releases/1.1.txt +++ b/docs/releases/1.1.txt @@ -267,7 +267,7 @@ A few notable improvements have been made to the :doc:`testing framework `. Test performance improvements -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. currentmodule:: django.test diff --git a/docs/topics/auth/passwords.txt b/docs/topics/auth/passwords.txt index 7015e65404..d39aebb89a 100644 --- a/docs/topics/auth/passwords.txt +++ b/docs/topics/auth/passwords.txt @@ -565,7 +565,7 @@ Django includes four validators: Validates whether the password is not entirely numeric. Integrating validation ------------------------ +---------------------- There are a few functions in ``django.contrib.auth.password_validation`` that you can call from your own forms or other code to integrate password diff --git a/docs/topics/pagination.txt b/docs/topics/pagination.txt index 0f436e6353..b89cdb2408 100644 --- a/docs/topics/pagination.txt +++ b/docs/topics/pagination.txt @@ -76,7 +76,7 @@ page:: Using ``Paginator`` in a view -============================== +============================= Here's a slightly more complex example using :class:`Paginator` in a view to paginate a queryset. We give both the view and the accompanying template to