adjust to symfony-cmf/menu-bundle#121

Author: dbu

bundles/menu.rst

@@ -29,7 +29,7 @@ provide your own implementations, this bundle also depends on:
   is not loaded. See the
   :doc:`documentation of the cmf routing bundle <routing>` for more information.
 * :doc:`PHPCR-ODM <phpcr_odm>` - to load route documents from the content
-  repository when using the ``PHPCRMenuProvider``.
+  repository when using the ``PhpcrMenuProvider``.
 
 Configuration
 -------------
@@ -94,9 +94,9 @@ Menu Provider
 
 A menu provider is responsible to load a menu when it is requested. KnpMenu
 supports having several providers. The CmfMenuBundle provides the
-``PHPCRMenuProvider`` to load menu items from PHPCR-ODM.
+``PhpcrMenuProvider`` to load menu items from PHPCR-ODM.
 
-Every menu has a name and is loaded by that name. The ``PHPCRMenuProvider``
+Every menu has a name and is loaded by that name. The ``PhpcrMenuProvider``
 locates menus by looking at ``persistence.phpcr.menu_basepath``/``<menuname>``.
 You can use custom document classes for menu nodes if needed, as long as they
 implement ``Knp\Menu\NodeInterface`` to integrate with KnpMenuBundle. The
@@ -107,7 +107,7 @@ default ``MenuNode`` class discards children that do not implement the
 
     There is currently no support for Doctrine ORM or other persistence
     managers. This is not by design, but only because nobody built that yet.
-    We would be glad for a pull request refactoring ``PHPCRMenuProvider`` into
+    We would be glad for a pull request refactoring ``PhpcrMenuProvider`` into
     a base class suitable for all doctrine implementations, and storage
     specific providers.
 

getting_started/menu.rst

@@ -55,12 +55,12 @@ this specific section.
 The Provider
 ~~~~~~~~~~~~
 
-The core of the MenuBundle is ``PHPCRMenuProvider``, a
+The core of the MenuBundle is ``PhpcrMenuProvider``, a
 ``MenuProviderInterface`` implementation that's responsible for dynamically
 loading menus from a PHPCR database. The default provider service is
 configured with a ``menu_basepath`` to know where in the PHPCR tree it will
 find menus. The menu ``name`` is given when rendering the menu and must be a
-direct child of the menu base path. This allows the ``PHPCRMenuProvider`` to
+direct child of the menu base path. This allows the ``PhpcrMenuProvider`` to
 handle several menu hierarchies using a single storage mechanism.
 
 To give a concrete example, if we have the configuration as given below and
@@ -91,7 +91,7 @@ render the menu ``simple``, the menu root node must be stored at
             'menu_basepath' => '/cms/menu',
         ));
 
-If you need multiple menu roots, you can create further PHPCRMenuProvider
+If you need multiple menu roots, you can create further ``PhpcrMenuProvider``
 instances and register them with KnpMenu - see the CMF MenuBundle
 ``DependencyInjection`` code for the details.
 

getting_started/simplecms.rst

@@ -304,7 +304,7 @@ can be used to generate a ``MenuItem`` that will, in turn, be rendered into HTML
 menus.
 
 To do so, the default ``MenuBundle`` mechanisms are used, only a custom
-``basepath`` is provided to the ``PHPCRMenuProvider`` instance. This is
+``basepath`` is provided to the ``PhpcrMenuProvider`` instance. This is
 defined in the SimpleCMSBundle configuration options, and used when handling
 content storage to support functionality as described in :doc:`menu`
 documentation. This parameter is optional, and can be configured as follows: