Merge pull request #6309 from kenjis/fix-docs-modules.rst

docs: fix module namespace definition

Author: kenjis

user_guide_src/source/general/modules.rst

@@ -30,11 +30,11 @@ directory in the main project root::
     /tests
     /writable
 
-Open **app/Config/Autoload.php** and add the **Acme** namespace to the ``psr4`` array property:
+Open **app/Config/Autoload.php** and add the ``Acme\Blog`` namespace to the ``psr4`` array property:
 
 .. literalinclude:: modules/001.php
 
-Now that this is set up, we can access any file within the **acme** folder through the ``Acme`` namespace. This alone
+Now that this is set up, we can access any file within the **acme/Blog** folder through the ``Acme\Blog`` namespace. This alone
 takes care of 80% of what is needed for modules to work, so you should be sure to familiarize yourself with namespaces
 and become comfortable with their use. Several file types will be scanned for automatically through all defined namespaces - a crucial ingredient for working with modules.
 
@@ -90,23 +90,18 @@ This is configured in the file **app/Config/Modules.php**.
 
 The auto-discovery system works by scanning for particular directories and files within psr4 namespaces that have been defined in **Config/Autoload.php**.
 
-To make auto-discovery work for our **Blog** namespace, we need to make one small adjustment.
-**Acme** needs to be changed to **Acme\\Blog** because each "module" within the namespace needs to be fully defined.
-
-.. literalinclude:: modules/003.php
-
-Once your module folder path is defined, the discovery process would look for discoverable items on that path and should, for example, find the routes file at **/acme/Blog/Config/Routes.php**.
+The discovery process would look for discoverable items on that path and should, for example, find the routes file at **/acme/Blog/Config/Routes.php**.
 
 Enable/Disable Discover
 =======================
 
-You can turn on or off all auto-discovery in the system with the **$enabled** class variable. False will disable
+You can turn on or off all auto-discovery in the system with the ``$enabled`` class variable. False will disable
 all discovery, optimizing performance, but negating the special capabilities of your modules.
 
 Specify Discovery Items
 =======================
 
-With the **$aliases** option, you can specify which items are automatically discovered. If the item is not
+With the ``$aliases`` option, you can specify which items are automatically discovered. If the item is not
 present, then no auto-discovery will happen for that item, but the others in the array will still be discovered.
 
 Discovery and Composer
@@ -173,12 +168,12 @@ with the ``new`` command:
 
 .. literalinclude:: modules/008.php
 
-Config files are automatically discovered whenever using the **config()** function that is always available.
+Config files are automatically discovered whenever using the ``config()`` function that is always available.
 
 .. note:: We don't recommend you use the same short classname in modules.
     Modules that need to override or add to known configurations in **app/Config/** should use :ref:`registrars`.
 
-.. note:: **config()** finds the file in **app/Config/** when there is a class with the same shortname,
+.. note:: ``config()`` finds the file in **app/Config/** when there is a class with the same shortname,
     even if you specify a fully qualified class name like ``config(\Acme\Blog\Config\Blog::class)``.
     This is because ``config()`` is a wrapper for the ``Factories`` class which uses ``preferApp`` by default. See :ref:`factories-options` for more information.
 

user_guide_src/source/general/modules/001.php

@@ -9,7 +9,7 @@ class Autoload extends AutoloadConfig
     public $psr4 = [
         APP_NAMESPACE => APPPATH, // For custom namespace
         'Config'      => APPPATH . 'Config',
-        'Acme'        => ROOTPATH . 'acme',
+        'Acme\Blog'   => ROOTPATH . 'acme/Blog',
     ];
 
     // ...