minor symfony#4042 [Cookbook] apply headline guidelines to the cookbook articles (xabbuh)

This PR was merged into the 2.3 branch.

Discussion
----------

[Cookbook] apply headline guidelines to the cookbook articles

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | all
| Fixed tickets |

This completes the work started in symfony#3765, symfony#3828 and symfony#3829.

Commits
-------

1fa40f3 apply headline guidelines to the cookbook articles

Author: weaverryan

cookbook/assetic/apply_to_option.rst

@@ -1,7 +1,7 @@
 .. index::
    single: Assetic; Apply filters
 
-How to Apply an Assetic Filter to a Specific File Extension
+How to Apply an Assetic Filter to a specific File Extension
 ===========================================================
 
 Assetic filters can be applied to individual files, groups of files or even,
@@ -49,7 +49,7 @@ An example configuration might look like this:
             ),
         ));
 
-Filter a Single File
+Filter a single File
 --------------------
 
 You can now serve up a single CoffeeScript file as JavaScript from within your
@@ -75,7 +75,7 @@ templates:
 This is all that's needed to compile this CoffeeScript file and serve it
 as the compiled JavaScript.
 
-Filter Multiple Files
+Filter multiple Files
 ---------------------
 
 You can also combine multiple CoffeeScript files into a single output file:
@@ -107,7 +107,7 @@ JavaScript.
 
 .. _cookbook-assetic-apply-to:
 
-Filtering based on a File Extension
+Filtering Based on a File Extension
 -----------------------------------
 
 One of the great advantages of using Assetic is reducing the number of asset
@@ -146,7 +146,7 @@ applied to all ``.coffee`` files:
                 apply_to="\.coffee$" />
                 <assetic:node-paths>/usr/lib/node_modules/</assetic:node-path>
         </assetic:config>
-        
+
     .. code-block:: php
 
         // app/config/config.php

cookbook/assetic/asset_management.rst

@@ -159,7 +159,7 @@ the :ref:`cssrewrite <cookbook-assetic-cssrewrite>` filter.
 
 .. _cookbook-assetic-including-image:
 
-Including images
+Including Images
 ~~~~~~~~~~~~~~~~
 
 To include an image you can use the ``image`` tag.
@@ -422,7 +422,7 @@ into your template:
 A more detailed guide about configuring and using Assetic filters as well as
 details of Assetic's debug mode can be found in :doc:`/cookbook/assetic/uglifyjs`.
 
-Controlling the URL used
+Controlling the URL Used
 ------------------------
 
 If you wish to, you can control the URLs that Assetic produces. This is
@@ -471,7 +471,7 @@ it might be downright frustrating.
 Fortunately, Assetic provides a way to dump your assets to real files, instead
 of being generated dynamically.
 
-Dumping Asset Files in the ``prod`` environment
+Dumping Asset Files in the ``prod`` Environment
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 In the ``prod`` environment, your JS and CSS files are represented by a single
@@ -500,7 +500,7 @@ This will physically generate and write each file that you need (e.g. ``/js/abcd
 If you update any of your assets, you'll need to run this again to regenerate
 the file.
 
-Dumping Asset Files in the ``dev`` environment
+Dumping Asset Files in the ``dev`` Environment
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 By default, each asset path generated in the ``dev`` environment is handled

cookbook/assetic/jpeg_optimize.rst

@@ -1,7 +1,7 @@
 .. index::
    single: Assetic; Image optimization
 
-How to Use Assetic For Image Optimization with Twig Functions
+How to Use Assetic for Image Optimization with Twig Functions
 =============================================================
 
 Amongst its many filters, Assetic has four filters which can be used for on-the-fly
@@ -111,7 +111,7 @@ remove these by using the ``strip_all`` option:
             ),
         ));
 
-Lowering Maximum Quality
+Lowering maximum Quality
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
 The quality level of the JPEG is not affected by default. You can gain
@@ -152,7 +152,7 @@ image quality:
             ),
         ));
 
-Shorter syntax: Twig Function
+Shorter Syntax: Twig Function
 -----------------------------
 
 If you're using Twig, it's possible to achieve all of this with a shorter

cookbook/assetic/uglifyjs.rst

@@ -1,7 +1,7 @@
 .. index::
    single: Assetic; UglifyJS
 
-How to Minify CSS/JS Files (using UglifyJS and UglifyCSS)
+How to Minify CSS/JS Files (Using UglifyJS and UglifyCSS)
 =========================================================
 
 `UglifyJS`_ is a JavaScript parser/compressor/beautifier toolkit. It can be used
@@ -183,7 +183,7 @@ and :ref:`dump your assetic assets <cookbook-asetic-dump-prod>`.
     rather than the common config file. For details on applying filters by
     file extension, see :ref:`cookbook-assetic-apply-to`.
 
-Install, configure and use UglifyCSS
+Install, Configure and Use UglifyCSS
 ------------------------------------
 
 The usage of UglifyCSS works the same way as UglifyJS. First, make sure

cookbook/bundles/best_practices.rst

@@ -1,7 +1,7 @@
 .. index::
    single: Bundle; Best practices
 
-How to use Best Practices for Structuring Bundles
+How to Use best Practices for Structuring Bundles
 =================================================
 
 A bundle is a directory that has a well-defined structure and can host anything

cookbook/bundles/extension.rst

@@ -2,7 +2,7 @@
    single: Configuration; Semantic
    single: Bundle; Extension configuration
 
-How to expose a Semantic Configuration for a Bundle
+How to Expose a semantic Configuration for a Bundle
 ===================================================
 
 If you open your application configuration file (usually ``app/config/config.yml``),
@@ -330,7 +330,7 @@ information loaded from other bundles). The goal of the ``load()`` method
 is to manipulate the container, adding and configuring any methods or services
 needed by your bundle.
 
-Loading External Configuration Resources
+Loading external Configuration Resources
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 One common thing to do is to load an external configuration file that may
@@ -549,7 +549,7 @@ normalization and advanced merging. You can read more about this in
 You can also see it in action by checking out some of the core Configuration classes,
 such as the one from the `FrameworkBundle Configuration`_ or the `TwigBundle Configuration`_.
 
-Modifying the configuration of another Bundle
+Modifying the Configuration of another Bundle
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you have multiple bundles that depend on each other, it may be useful

cookbook/bundles/inheritance.rst

@@ -1,7 +1,7 @@
 .. index::
    single: Bundle; Inheritance
 
-How to use Bundle Inheritance to Override parts of a Bundle
+How to Use Bundle Inheritance to Override Parts of a Bundle
 ===========================================================
 
 When working with third-party bundles, you'll probably come across a situation

cookbook/bundles/installation.rst

@@ -1,7 +1,7 @@
 .. index::
    single: Bundle; Installation
 
-How to install 3rd party Bundles
+How to Install 3rd Party Bundles
 ================================
 
 Most bundles provide their own installation instructions. However, the

cookbook/bundles/override.rst

@@ -93,7 +93,7 @@ See :doc:`/cookbook/service_container/compiler_passes` for information on how to
 compiler passes. If you want to do something beyond just overriding the class -
 like adding a method call - you can only use the compiler pass method.
 
-Entities & Entity mapping
+Entities & Entity Mapping
 -------------------------
 
 Due to the way Doctrine works, it is not possible to override entity mapping
@@ -119,7 +119,7 @@ rather than::
 
 .. _override-validation:
 
-Validation metadata
+Validation Metadata
 -------------------
 
 Symfony loads all validation configuration files from every bundle and

cookbook/bundles/prepend_extension.rst

@@ -2,7 +2,7 @@
    single: Configuration; Semantic
    single: Bundle; Extension configuration
 
-How to simplify configuration of multiple Bundles
+How to Simplify Configuration of multiple Bundles
 =================================================
 
 When building reusable and extensible applications, developers are often

cookbook/bundles/remove.rst

@@ -1,7 +1,7 @@
 .. index::
     single: Bundle; Removing AcmeDemoBundle
 
-How to remove the AcmeDemoBundle
+How to Remove the AcmeDemoBundle
 ================================
 
 The Symfony2 Standard Edition comes with a complete demo that lives inside a
@@ -13,7 +13,7 @@ starting a project, but you'll probably want to eventually remove it.
     This article uses the AcmeDemoBundle as an example, but you can use
     these steps to remove any bundle.
 
-1. Unregister the bundle in the ``AppKernel``
+1. Unregister the Bundle in the ``AppKernel``
 ---------------------------------------------
 
 To disconnect the bundle from the framework, you should remove the bundle from
@@ -38,20 +38,20 @@ development environment and you can find it inside the if statement below::
         }
     }
 
-2. Remove bundle configuration
+2. Remove Bundle Configuration
 ------------------------------
 
 Now that Symfony doesn't know about the bundle, you need to remove any
 configuration and routing configuration inside the ``app/config`` directory
 that refers to the bundle.
 
-2.1 Remove bundle routing
+2.1 Remove Bundle Routing
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The routing for the AcmeDemoBundle can be found in ``app/config/routing_dev.yml``.
 Remove the ``_acme_demo`` entry at the bottom of this file.
 
-2.2 Remove bundle configuration
+2.2 Remove Bundle Configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Some bundles contain configuration in one of the ``app/config/config*.yml``
@@ -65,7 +65,7 @@ used in the configuration for the ``app/config/security.yml`` file. You can
 use it as a boilerplate for your own security, but you **can** also remove
 everything: it doesn't matter to Symfony if you remove it or not.
 
-3. Remove the bundle from the Filesystem
+3. Remove the Bundle from the Filesystem
 ----------------------------------------
 
 Now you have removed every reference to the bundle in your application, you
@@ -81,7 +81,7 @@ can remove the ``Acme`` directory as well.
 
         echo $this->container->get('kernel')->getBundle('AcmeDemoBundle')->getPath();
 
-4. Remove integration in other bundles
+4. Remove Integration in other Bundles
 --------------------------------------
 
 .. note::

cookbook/cache/varnish.rst

@@ -1,7 +1,7 @@
 .. index::
     single: Cache; Varnish
 
-How to use Varnish to speed up my Website
+How to Use Varnish to Speed up my Website
 =========================================
 
 Because Symfony2's cache uses the standard HTTP cache headers, the
@@ -62,7 +62,7 @@ Symfony2 adds automatically:
             // For Varnish < 3.0
             // esi;
         }
-        /* By default Varnish ignores Cache-Control: nocache 
+        /* By default Varnish ignores Cache-Control: nocache
         (https://www.varnish-cache.org/docs/3.0/tutorial/increasing_your_hitrate.html#cache-control),
         so in order avoid caching it has to be done explicitly */
         if (beresp.http.Pragma ~ "no-cache" ||

cookbook/configuration/apache_router.rst

@@ -1,7 +1,7 @@
 .. index::
     single: Apache Router
 
-How to use the Apache Router
+How to Use the Apache Router
 ============================
 
 Symfony2, while fast out of the box, also provides various ways to increase that speed with a little bit of tweaking.
@@ -49,7 +49,7 @@ Symfony2 to use the ``ApacheUrlMatcher`` instead of the default one:
     at the end of ``ApacheUrlMatcher::match()`` a call to ``parent::match()``
     is done).
 
-Generating mod_rewrite rules
+Generating mod_rewrite Rules
 ----------------------------
 
 To test that it's working, create a very basic route for the AcmeDemoBundle:
@@ -119,7 +119,7 @@ it should look like this:
 That's it!
 You're now all set to use Apache routes.
 
-Additional tweaks
+Additional Tweaks
 -----------------
 
 To save a little bit of processing time, change occurrences of ``Request``

cookbook/configuration/environments.rst

@@ -16,7 +16,7 @@ optimized for speed.
 .. index::
    single: Environments; Configuration files
 
-Different Environments, Different Configuration Files
+Different Environments, different Configuration Files
 -----------------------------------------------------
 
 A typical Symfony2 application begins with three environments: ``dev``,
@@ -125,7 +125,7 @@ activated by modifying the default value in the ``dev`` configuration file:
 .. index::
    single: Environments; Executing different environments
 
-Executing an Application in Different Environments
+Executing an Application in different Environments
 --------------------------------------------------
 
 To execute the application in each environment, load up the application using
@@ -147,7 +147,7 @@ If you open up one of these files, you'll quickly see that the environment
 used by each is explicitly set::
 
     // web/app.php
-    // ... 
+    // ...
 
     $kernel = new AppKernel('prod', false);
 
@@ -215,7 +215,7 @@ environment by using this code and changing the environment string.
 .. index::
    single: Environments; Creating a new environment
 
-Creating a New Environment
+Creating a new Environment
 --------------------------
 
 By default, a Symfony2 application has three environments that handle most
@@ -345,7 +345,7 @@ includes the following:
     You can easily change the directory location and name. For more information
     read the article :doc:`/cookbook/configuration/override_dir_structure`.
 
-Going Further
+Going further
 -------------
 
 Read the article on :doc:`/cookbook/configuration/external_parameters`.

cookbook/configuration/external_parameters.rst

@@ -1,7 +1,7 @@
 .. index::
     single: Environments; External parameters
 
-How to Set External Parameters in the Service Container
+How to Set external Parameters in the Service Container
 =======================================================
 
 In the chapter :doc:`/cookbook/configuration/environments`, you learned how

cookbook/configuration/front_controllers_and_kernel.rst

@@ -2,7 +2,7 @@
     single: How the front controller, ``AppKernel`` and environments
     work together
 
-Understanding how the Front Controller, Kernel and Environments work together
+Understanding how the Front Controller, Kernel and Environments Work together
 =============================================================================
 
 The section :doc:`/cookbook/configuration/environments` explained the basics