Title in sentence case for consistency (pypa#467)

Author: hugovk

source/discussions/deploying-python-applications.rst

@@ -36,7 +36,7 @@ Supporting multiple hardware platforms
 
 
 
-OS Packaging & Installers
+OS packaging & installers
 =========================
 
 ::
@@ -77,7 +77,7 @@ There are several examples for different kinds of programs (console, GUI) in
 the `documentation <https://pynsist.readthedocs.io>`__. The tool is released
 under the MIT-licence.
 
-Application Bundles
+Application bundles
 ===================
 
 ::
@@ -88,7 +88,7 @@ Application Bundles
   - wheels kinda/sorta
 
 
-Configuration Management
+Configuration management
 ========================
 
 ::

source/discussions/install-requires-vs-requirements.rst

@@ -1,7 +1,7 @@
-.. _`install_requires vs Requirements files`:
+.. _`install_requires vs requirements files`:
 
 ======================================
-install_requires vs Requirements files
+install_requires vs requirements files
 ======================================
 
 .. contents:: Contents

source/guides/dropping-older-python-versions.rst

@@ -1,7 +1,7 @@
 .. _`Dropping support for older Python versions`:
 
 ==========================================
-Dropping Support for Older Python Versions
+Dropping support for older Python versions
 ==========================================
 
 Dropping support for older Python versions is supported by the standard :ref:`core-metadata` 1.2 specification via a "Requires-Python" attribute.

source/guides/hosting-your-own-index.rst

@@ -21,7 +21,7 @@ valid HTTPS. At this time, the security of your user's installations depends on
 all repositories using a valid HTTPS setup.
 
 
-"Manual" Repository
+"Manual" repository
 ===================
 
 The directory layout is fairly simple, within a root directory you need to

source/guides/packaging-binary-extensions.rst

@@ -297,7 +297,7 @@ For interim guidance on this topic, see the discussion in
    discouraged
 
 
-Additional Resources
+Additional resources
 ====================
 
 Cross-platform development and distribution of extension modules is a complex topic,

source/guides/packaging-namespace-packages.rst

@@ -77,7 +77,7 @@ There are currently three different approaches to creating namespace packages:
     same namespace.
 
 Native namespace packages
---------------------------------
+-------------------------
 
 Python 3.3 added **implicit** namespace packages from :pep:`420`. All that is
 required to create a native namespace package is that you just omit

source/guides/supporting-multiple-python-versions.rst

@@ -45,7 +45,7 @@ correctly on all the target Python versions (and OSs!) could be very
 time-consuming. Fortunately, several tools are available for dealing with
 this, and these will briefly be discussed here.
 
-Automated Testing and Continuous Integration
+Automated testing and continuous integration
 --------------------------------------------
 
 Several hosted services for automated testing are available. These services
@@ -120,7 +120,7 @@ package: with python-future_, the ``futurize`` script can be called with the
 provides for forward-compatibility to Python 3. Any remaining compatibility
 problems would require manual changes.
 
-What's in Which Python?
+What's in which Python?
 -----------------------
 
 Ned Batchelder provides a list of changes in each Python release for

source/guides/supporting-windows-using-appveyor.rst

@@ -34,7 +34,7 @@ using Appveyor as a build service (even if not using it for testing) it is
 possible for projects without a dedicated Windows environment to provide
 Windows-targeted binaries.
 
-Setting Up
+Setting up
 ==========
 
 In order to use Appveyor to build Windows wheels for your project, you must
@@ -143,7 +143,7 @@ of links, one of which is "Artifacts". That page will include a list of links
 to the wheels for that Python version / architecture. You can download those
 wheels and upload them to PyPI as part of your release process.
 
-Additional Notes
+Additional notes
 ================
 
 Testing with tox

source/guides/tool-recommendations.rst

@@ -8,7 +8,7 @@ If you're familiar with Python packaging and installation, and just want to know
 what tools are currently recommended, then here it is.
 
 
-Application Dependency Management
+Application dependency management
 =================================
 
 Use :ref:`pipenv` to manage library dependencies when developing Python
@@ -18,7 +18,7 @@ on using ``pipenv``.
 Consider other tools such as :ref:`pip` when ``pipenv`` does not meet your use
 case.
 
-Installation Tool Recommendations
+Installation tool recommendations
 =================================
 
 * Use :ref:`pip` to install Python :term:`packages <Distribution Package>` from
@@ -38,7 +38,7 @@ Installation Tool Recommendations
     on the scientific community.
 
 
-Packaging Tool Recommendations
+Packaging tool recommendations
 ==============================
 
 * Use :ref:`setuptools` to define projects and create :term:`Source Distributions
@@ -52,7 +52,7 @@ Packaging Tool Recommendations
   to :term:`PyPI <Python Package Index (PyPI)>`.
 
 
-Publishing Platform Migration
+Publishing platform migration
 =============================
 
 The original Python Package Index implementation (hosted at

source/specifications/core-metadata.rst

@@ -1,7 +1,7 @@
 .. _`core-metadata`:
 
 ============================
-Core Metadata Specifications
+Core metadata specifications
 ============================
 
 The current core metadata file format, version 2.1, is specified in :pep:`566`.