[#2007] Proofreading the new prepend extension docs, adding some other links/notes to other sections

Author: weaverryan

components/dependency_injection/compilation.rst

@@ -248,9 +248,12 @@ but also load a secondary one only if a certain parameter is set::
 
 .. _components-dependency-injection-compiler-passes:
 
-Prepending configuration passed to the Extension
+Prepending Configuration passed to the Extension
 ------------------------------------------------
 
+.. versionadded:: 2.1
+    The ability to prepend the configuration of a bundle is new in Symfony 2.2.
+
 An Extension can prepend the configuration of any Bundle before the ``load()``
 method is called by implementing :class:`Symfony\\Component\\DependencyInjection\\Compiler\\PrependExtensionInterface`::
 
@@ -271,6 +274,9 @@ method is called by implementing :class:`Symfony\\Component\\DependencyInjection
         }
     }
 
+For more details, see :doc:`/cookbook/bundles/prepend_extension`, which is
+specific to the Symfony2 Framework, but contains more details about this feature.
+
 Creating a Compiler Pass
 ------------------------
 

cookbook/bundles/extension.rst

@@ -483,6 +483,16 @@ normalization and advanced merging. You can read more about this in :doc:`the Co
 You can also see it 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
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you have multiple bundles that depend on each other, it may be useful
+to allow one ``Extension`` class to modify the configuration passed to another
+bundle's ``Extension`` class, as if the end-developer has actually placed that
+configuration in his/her ``app/config/config.yml`` file.
+
+For more details, see :doc:`/cookbook/bundles/prepend_extension`.
+
 Default Configuration Dump
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 

cookbook/bundles/prepend_extension.rst

@@ -5,24 +5,24 @@
 How to simplify configuration of multiple Bundle
 ================================================
 
-Especially when building reusable and extensible applications developers are
-often faced with a choice, either create a single Bundle or create multiple
-Bundles. Creating a single Bundle has the draw back that its impossible for
+When building reusable and extensible applications, developers are often
+faced with a choice: either create a single large Bundle or multiple smaller
+Bundles. Creating a single Bundle has the draw back that it's impossible for
 users to choose to remove functionality they are not using. Creating multiple
 Bundles has the draw back that configuration becomes more tedious and settings
 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
+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 the
 user in the application configuration.
 
 For example, this could be used to configure the entity manager name to use in
-multiple Bundle. Or it can be used to enable an optional feature that depends
+multiple Bundles. Or it can be used to enable an optional feature that depends
 on another Bundle being loaded as well.
 
-In order for an Extension to be able to do this it needs to implement
+To give an Extension the power to do this, it needs to implement
 :class:`Symfony\\Component\\DependencyInjection\\Compiler\\PrependExtensionInterface`::
 
     // src/Acme/HelloBundle/DependencyInjection/AcmeHelloExtension.php
@@ -42,19 +42,19 @@ In order for an Extension to be able to do this it needs to implement
         }
     }
 
-Inside the :method:`Symfony\\Component\\DependencyInjection\\Compiler\\PrependExtensionInterface::prepend()`
-method developers have full access to the :class:`Symfony\Component\DependencyInjection\ContainerBuilder`
-instance just before the :method:`Symfony\Component\HttpKernel\DependencyInjection\ExtensionInterface:load()`
-method is called on the registered Bundle Extensions. In order to prepend settings
-to a Bundle extension developers can use the
-:method:`Symfony\Component\DependencyInjection\ContainerBuilder:prependExtensionConfig()`
-method on the :class:`Symfony\Component\DependencyInjection\ContainerBuilder`
+Inside the :method:`Symfony\\Component\\DependencyInjection\\Compiler\\PrependExtensionInterface::prepend`
+method, developers have full access to the :class:`Symfony\\Component\\DependencyInjection\\ContainerBuilder`
+instance just before the :method:`Symfony\\Component\\DependencyInjection\\Extension\\ExtensionInterface::load`
+method is called on each of the registered Bundle Extensions. In order to
+prepend settings to a Bundle extension developers can use the
+:method:`Symfony\\Component\\DependencyInjection\\ContainerBuilder::prependExtensionConfig`
+method on the :class:`Symfony\\Component\\DependencyInjection\\ContainerBuilder`
 instance. As this method only prepends settings, any other settings done explicitly
 inside the ``app/config/config.yml`` would override these prepended settings.
 
 The following example illustrates how to prepend
 a configuration setting in multiple Bundles as well as disable a flag in multiple Bundles
-in case specific other Bundle is not registered::
+in case a specific other Bundle is not registered::
 
     public function prepend(ContainerBuilder $container)
     {
@@ -92,7 +92,7 @@ in case specific other Bundle is not registered::
 
 The above would be the equivalent of writing the following into the ``app/config/config.yml``
 in case ``AcmeGoodbyeBundle`` is not registered and the ``entity_manager_name`` setting
-for ``acme_hello`` is set to ``non_default``::
+for ``acme_hello`` is set to ``non_default``:
 
 .. configuration-block::
 

cookbook/map.rst.inc

@@ -11,6 +11,7 @@
   * :doc:`/cookbook/bundles/inheritance`
   * :doc:`/cookbook/bundles/override`
   * :doc:`/cookbook/bundles/extension`
+  * :doc:`/cookbook/bundles/prepend_extension`
 
 * :doc:`/cookbook/cache/index`