updated installation pages

Signed-off-by: bidi <bidi@apidemia.com>

Author: bidi47

docs/book/v7/installation/composer.md

@@ -14,19 +14,30 @@ Run this command in the command prompt.
 composer install
 ```
 
+The automatic setup script performs these tasks:
+
+- Installs the packages listed in the `composer.json` file and their dependencies into the `vendor` folder.
+- Creates the `composer.lock` file that locks all dependencies to exact versions (you can still run `composer update` to replace them with newer versions, if available).
+- Configures PHP CodeSniffer, a utility to detect code style errors in PHP code.
+- Generate and save the OAuth2 keys in the `data/oauth` folder.
+- Creates the initial `config/autoload` configuration files:
+  - config/autoload/local.php
+  - config/autoload/local.test.php
+  - config/autoload/mail.global.php
+
 You should see this text below, along with a long list of packages to be installed instead of the `[...]`.
-In this example there are 164 packages, though the number can change in future updates.
-You will find the packages in the newly-created `vendor` folder.
+
+> In this example there are 146 packages, though the number can change in future updates.
 
 ```shell
 No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.
 Loading composer repositories with package information
 Updating dependencies
-Lock file operations: 164 installs, 0 updates, 0 removals
+Lock file operations: 146 installs, 0 updates, 0 removals
 [...]
 Writing lock file
 Installing dependencies from lock file (including require-dev)
-Package operations: 164 installs, 0 updates, 0 removals
+Package operations: 146 installs, 0 updates, 0 removals
 [...]
 ```
 
@@ -60,6 +71,12 @@ Enable development mode by running:
 composer development-enable
 ```
 
+The confirmation message should read:
+
+```shell
+You are now in development mode.
+```
+
 If you ever need to disable the development mode, run:
 
 ```shell

docs/book/v7/installation/doctrine-orm.md

@@ -170,4 +170,22 @@ To execute fixtures, run:
 php ./bin/doctrine fixtures:execute
 ```
 
+If everything ran correctly, you will get this confirmation:
+
+```shell
+Executing Core\App\Fixture\AdminRoleLoader
+Executing Core\App\Fixture\OAuthClientLoader
+Executing Core\App\Fixture\OAuthScopeLoader
+Executing Core\App\Fixture\UserRoleLoader
+Executing Core\App\Fixture\AdminLoader
+Executing Core\App\Fixture\UserLoader
+Fixtures have been loaded.
+                .''
+      ._.-.___.' (`\
+     //(        ( `'
+    '/ )\ ).__. )
+    ' <' `\ ._/'\
+       `   \     \
+```
+
 More details on how fixtures work can be found on [dot-data-fixtures documentation](https://github.com/dotkernel/dot-data-fixtures#usage)

docs/book/v7/installation/test-the-installation.md

@@ -2,18 +2,29 @@
 
 > If you are getting server error 500, make sure to check the folder permissions covered in the [FAQ page](https://docs.dotkernel.org/api-documentation/v7/installation/faq/)
 
-Sending a GET request to the [home page](http://0.0.0.0:8080/) should output the following message:
+Sending a GET request to the home page for your virtual host should output the following message:
 
 ```json
 {"message": "Dotkernel API version 7"}
 ```
 
+From this point on, you are ready to add custom code to your application.
+
 ## Old way of doing things, using PHP built-in server
 
+This is an alternative way of accessing the API, without using a virtual host.
+Run this command from the project root:
+
 ```shell
 php -S 0.0.0.0:8080 -t public
 ```
 
+You should see something like this:
+
+```shell
+[Mon Mar 30 14:53:50 2026] PHP 8.4.15 Development Server (http://0.0.0.0:8080) started
+```
+
 ## Running tests
 
 The project has two types of tests: functional and unit tests, you can run both types at the same type by executing this command: