vendor and bundle naming consistency

Author: yceruto

bundles/best_practices.rst

@@ -504,12 +504,12 @@ The ``composer.json`` file should include at least the following metadata:
         {
             "autoload": {
                 "psr-4": {
-                    "SomeVendor\\BlogBundle\\": "src/"
+                    "Acme\\BlogBundle\\": "src/"
                 }
             },
             "autoload-dev": {
                 "psr-4": {
-                    "SomeVendor\\BlogBundle\\Tests\\": "tests/"
+                    "Acme\\BlogBundle\\Tests\\": "tests/"
                 }
             }
         }
@@ -522,15 +522,15 @@ Resources
 
 If the bundle references any resources (config files, translation files, etc.),
 don't use physical paths (e.g. ``__DIR__/config/services.xml``) but logical
-paths (e.g. ``@FooBundle/config/services.xml``).
+paths (e.g. ``@AcmeBlogBundle/config/services.xml``).
 
 The logical paths are required because of the bundle overriding mechanism that
 lets you override any resource/file of any bundle. See :ref:`http-kernel-resource-locator`
 for more details about transforming physical paths into logical paths.
 
 Beware that templates use a simplified version of the logical path shown above.
 For example, an ``index.html.twig`` template located in the ``templates/Default/``
-directory of the FooBundle, is referenced as ``@Foo/Default/index.html.twig``.
+directory of the AcmeBlogBundle, is referenced as ``@AcmeBlog/Default/index.html.twig``.
 
 Learn more
 ----------