docs: Improve guide (#10109)

* docs: Update "Managing your Applications"

* docs: Update "Composer Installation"

* docs: Update "Worker Mode"

* docs: Update "Testing"

* fix: Move next line

Author: neznaika0

user_guide_src/source/general/managing_apps.rst

@@ -20,7 +20,7 @@ Renaming or Relocating the Application Directory
 If you would like to rename your application directory or even move
 it to a different location on your server, other than your project root, open
 your main **app/Config/Paths.php** and set a *full server path* in the
-``$appDirectory`` variable (at about line 44):
+``$appDirectory`` variable (at about line 45):
 
 .. literalinclude:: managing_apps/001.php
 
@@ -46,26 +46,26 @@ If you would like to share a common CodeIgniter framework installation, to manag
 several different applications, simply put all of the directories located
 inside your application directory into their own (sub)-directory.
 
-For example, let's say you want to create two applications, named **foo**
-and **bar**. You could structure your application project directories like this:
+For example, let's say you want to create two applications, named **blog**
+and **shop**. You could structure your application project directories like this:
 
 .. code-block:: text
 
-    foo/
+    blog/
         app/
         public/
         tests/
         writable/
         env
-        phpunit.xml.dist
+        phpunit.dist.xml
         spark
-    bar/
+    shop/
         app/
         public/
         tests/
         writable/
         env
-        phpunit.xml.dist
+        phpunit.dist.xml
         spark
     vendor/
         autoload.php
@@ -77,25 +77,26 @@ and **bar**. You could structure your application project directories like this:
 
     .. code-block:: text
 
-        foo/
-        bar/
+        blog/
+        shop/
         codeigniter4/system/
 
-This would have two apps, **foo** and **bar**, both having standard application directories
+This would have two apps, **blog** and **shop**, both having standard application directories
 and a **public** folder, and sharing a common **codeigniter4/framework**.
 
 The ``$systemDirectory`` variable in **app/Config/Paths.php** inside each
 of those would be set to refer to the shared common **codeigniter4/framework** folder:
 
 .. literalinclude:: managing_apps/005.php
 
-.. note:: If you install CodeIgniter from the Zip file, the ``$systemDirectory`` would be ``__DIR__ . '/../../../codeigniter4/system'``.
-
 And modify the ``COMPOSER_PATH`` constant in **app/Config/Constants.php** inside each
 of those:
 
 .. literalinclude:: managing_apps/004.php
 
+.. note:: If you install CodeIgniter from the Zip file, the ``$systemDirectory`` would be ``__DIR__ . '/../../../codeigniter4/system'``.
+    If you don't use Composer, you don't have to edit the ``COMPOSER_PATH``.
+
 Only when you change the Application Directory, see :ref:`renaming-app-directory` and modify the paths in the **index.php** and **spark**.
 
 Changing the Location of the .env File

user_guide_src/source/general/managing_apps/001.php

@@ -6,7 +6,7 @@ class Paths
 {
     // ...
 
-    public $appDirectory = '/path/to/your/app';
+    public string $appDirectory = '/path/to/your/app';
 
     // ...
 }

user_guide_src/source/installation/installing_composer.rst

@@ -166,11 +166,15 @@ Latest Dev
 The App Starter repo comes with a ``builds`` scripts to switch Composer sources between the
 current stable release and the latest development branch of the framework. Use this script
 for a developer who is willing to live with the latest unreleased changes, which may be unstable.
+This way you can help find bugs and improve new features.
 
 The `development user guide <https://codeigniter4.github.io/CodeIgniter4/>`_ is accessible online.
 Note that this differs from the released user guide, and will pertain to the
 develop branch explicitly.
 
+Before running the script, check ``$files``, which is the list of files to be changed.
+This is useful if you have additional places in the code that mention the directory with the framework.
+
 .. note:: You should not rely on the version of the framework in your project
     - the development code may contain an incorrect number.
 
@@ -247,7 +251,7 @@ Setting Up
 ----------
 
     1. Copy the **app**, **public**, **tests** and **writable** folders from **vendor/codeigniter4/framework** to your project root
-    2. Copy the **env**, **phpunit.xml.dist** and **spark** files, from **vendor/codeigniter4/framework** to your project root
+    2. Copy the **env**, **phpunit.dist.xml** and **spark** files, from **vendor/codeigniter4/framework** to your project root
     3. You will have to adjust the ``$systemDirectory`` property in **app/Config/Paths.php** to refer to the vendor one, e.g., ``__DIR__ . '/../../vendor/codeigniter4/framework/system'``.
 
 Initial Configuration
@@ -322,4 +326,5 @@ From the command line inside your project root:
 
     composer require codeigniter4/translations
 
+Copy the **vendor/codeigniter4/translations/Language** folder contents in it to your **app/Language** folder.
 These will be updated along with the framework whenever you do a ``composer update``.

user_guide_src/source/installation/worker_mode.rst

@@ -110,6 +110,8 @@ Installation
 3. Configure your worker settings in **app/Config/WorkerMode.php** if needed.
    The defaults are recommended for most applications.
 
+.. note:: When changing the project directory, see the section :ref:`renaming-app-directory` and update your **public/frankenphp-worker.php**.
+
 Running the Worker
 ==================
 

user_guide_src/source/testing/overview.rst

@@ -60,7 +60,7 @@ Testing Your Application
 PHPUnit Configuration
 =====================
 
-In your CodeIgniter project root, there is the ``phpunit.xml.dist`` file. This
+In your CodeIgniter project root, there is the ``phpunit.dist.xml`` file. This
 controls unit testing of your application. If you provide your own ``phpunit.xml``,
 it will over-ride this.