Style / grammar fixes for the bundles chapter

Author: frne

cookbook/bundles/configuration.rst

@@ -210,7 +210,7 @@ The ``Configuration`` class to handle the sample configuration looks like::
     supporting "prototype" nodes, advanced validation, XML-specific normalization
     and advanced merging. You can read more about this in
     :doc:`the Config component documentation </components/config/definition>`. You
-    can also see it in action by checking out some of the core Configuration
+    can also see it in action by checking out some core Configuration
     classes, such as the one from the `FrameworkBundle Configuration`_ or the
     `TwigBundle Configuration`_.
 
@@ -227,7 +227,7 @@ thrown)::
     }
 
 The ``processConfiguration()`` method uses the configuration tree you've defined
-in the ``Configuration`` class to validate, normalize and merge all of the
+in the ``Configuration`` class to validate, normalize and merge all the
 configuration arrays together.
 
 .. tip::
@@ -253,7 +253,7 @@ configuration arrays together.
         }
 
     This class uses the ``getConfiguration()`` method to get the Configuration
-    instance, you should override it if your Configuration class is not called
+    instance. You should override it, if your Configuration class is not called
     ``Configuration`` or if it is not placed in the same namespace as the
     extension.
 

cookbook/bundles/installation.rst

@@ -7,11 +7,11 @@ How to Install 3rd Party Bundles
 Most bundles provide their own installation instructions. However, the
 basic steps for installing a bundle are the same:
 
-* `A) Add Composer Dependencies`_
-* `B) Enable the Bundle`_
-* `C) Configure the Bundle`_
+* `a) Add Composer Dependencies`_
+* `b) Enable the Bundle`_
+* `c) Configure the Bundle`_
 
-A) Add Composer Dependencies
+a) Add Composer Dependencies
 ----------------------------
 
 Dependencies are managed with Composer, so if Composer is new to you, learn
@@ -43,7 +43,7 @@ and download the library into the ``vendor/`` directory. If you need a specific
 version, add a ``:`` and the version right after the library name (see
 `composer require`_).
 
-B) Enable the Bundle
+b) Enable the Bundle
 --------------------
 
 At this point, the bundle is installed in your Symfony project (in
@@ -68,7 +68,7 @@ The only thing you need to do now is register the bundle in ``AppKernel``::
         }
     }
 
-C) Configure the Bundle
+c) Configure the Bundle
 -----------------------
 
 It's pretty common for a bundle to need some additional setup or configuration

cookbook/bundles/override.rst

@@ -90,8 +90,8 @@ In this example you fetch the service definition of the original service, and se
 its class name to your own class.
 
 See :doc:`/cookbook/service_container/compiler_passes` for information on how to use
-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.
+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
 -------------------------

cookbook/bundles/prepend_extension.rst

@@ -15,7 +15,7 @@ often need to be repeated for various bundles.
 Using the below approach, it is possible to remove the disadvantage of the
 multiple bundle approach by enabling a single Extension to prepend the settings
 for any bundle. It can use the settings defined in the ``app/config/config.yml``
-to prepend settings just as if they would have been written explicitly by
+to prepend settings just as if they had been written explicitly by
 the user in the application configuration.
 
 For example, this could be used to configure the entity manager name to use in

cookbook/bundles/remove.rst

@@ -56,7 +56,7 @@ Remove the ``_acme_demo`` entry at the bottom of this file.
 
 Some bundles contain configuration in one of the ``app/config/config*.yml``
 files. Be sure to remove the related configuration from these files. You can
-quickly spot bundle configuration by looking for a ``acme_demo`` (or whatever
+quickly spot bundle configuration by looking for an ``acme_demo`` (or whatever
 the name of the bundle is, e.g. ``fos_user`` for the FOSUserBundle) string in
 the configuration files.