Fixed #15002 - Fix title casing to conform to style guidelines. thanks adamv.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15135 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/howto/custom-model-fields.txt

@@ -281,7 +281,7 @@ custom form field, and/or implementing the :meth:`formfield` method on
 your field to return a form field class whose `to_python()` returns the
 correct datatype.
 
-Documenting your Custom Field
+Documenting your custom field
 -----------------------------
 
 .. class:: django.db.models.Field

docs/howto/deployment/modwsgi.txt

@@ -21,7 +21,7 @@ the details about how to use mod_wsgi. You'll probably want to start with the
 .. _official mod_wsgi documentation: http://code.google.com/p/modwsgi/
 .. _installation and configuration documentation: http://code.google.com/p/modwsgi/wiki/InstallationInstructions
 
-Basic Configuration
+Basic configuration
 ===================
 
 Once you've got mod_wsgi installed and activated, edit your ``httpd.conf`` file

docs/ref/models/querysets.txt

@@ -1746,7 +1746,7 @@ SQL equivalents::
 
 .. _aggregation-functions:
 
-Aggregation Functions
+Aggregation functions
 ---------------------
 
 Django provides the following aggregation functions in the

docs/topics/db/managers.txt

@@ -276,7 +276,7 @@ it into the inheritance hierarchy *after* the defaults::
 
 .. _manager-types:
 
-Controlling Automatic Manager Types
+Controlling automatic Manager types
 ===================================
 
 This document has already mentioned a couple of places where Django creates a
@@ -326,7 +326,7 @@ it will use :class:`django.db.models.Manager`.
     so that existing code will :doc:`continue to work </misc/api-stability>` in
     future Django versions.
 
-Writing Correct Managers For Use In Automatic Manager Instances
+Writing correct Managers for use in automatic Manager instances
 ---------------------------------------------------------------
 
 As already suggested by the `django.contrib.gis` example, above, the

docs/topics/http/decorators.txt

 ===============
-View Decorators
+View decorators
 ===============
 
 .. currentmodule:: django.views.decorators.http
@@ -7,7 +7,7 @@ View Decorators
 Django provides several decorators that can be applied to views to support
 various HTTP features.
 
-Allowed HTTP Methods
+Allowed HTTP methods
 ====================
 
 .. function:: require_http_methods(request_method_list)
@@ -47,7 +47,7 @@ headers; see
 
 .. currentmodule:: django.views.decorators.http
 
-GZip Compression
+GZip compression
 ================
 
 .. function:: gzip_page()
@@ -58,7 +58,7 @@ storage on the ``Accept-Encoding`` header.
 
 .. currentmodule:: django.views.decorators.vary
 
-Vary Headers
+Vary headers
 ============
 
 The ``Vary`` header defines which request headers a cache mechanism should take

docs/topics/http/urls.txt

@@ -462,7 +462,7 @@ included URLconf, as expected.
 
 .. _topics-http-defining-url-namespaces:
 
-Defining URL Namespaces
+Defining URL namespaces
 -----------------------
 
 When you need to deploy multiple instances of a single application, it can be

docs/topics/http/views.txt

 =============
-Writing Views
+Writing views
 =============
 
 A view function, or *view* for short, is simply a Python function that takes a
@@ -52,7 +52,7 @@ Let's step through this code one line at a time:
     ``America/Chicago``. This probably isn't where you live, so you might want
     to change it in your settings file.
 
-Mapping URLs to Views
+Mapping URLs to views
 =====================
 
 So, to recap, this view function returns an HTML page that includes the current