Revised text and markup blocks

Signed-off-by: nati <[email protected]>

Author: PopNatanael

docs/book/v6/how-to/authorization.md

@@ -1,28 +1,27 @@
 # Authorization Guards
 
-The packages responsible for restricting access to certain parts of the application are [dot-rbac-guard](https://github.com/dotkernel/dot-rbac-guard) and [dot-rbac](https://github.com/dotkernel/dot-rbac).
-These packages work together to create an infrastructure that is customizable and diversified to manage user access to the platform by specifying the type of role the user has.
+The packages responsible for restricting access to certain parts of the application are [dot-rbac-guard](https://github.com/dotkernel/dot-rbac-guard) and [dot-rbac](https://github.com/dotkernel/dot-rbac). These packages work together to create an infrastructure that is customizable and diversified to manage user access to the platform by specifying the type of role the user has.
 
 The `authorization.global.php` file provides multiple configurations specifying multiple roles as well as the types of permissions to which these roles have access.
 
 ```php
 //example of a flat RBAC model that specifies two types of roles as well as their permission
     'roles' => [
-                'admin' => [
-                    'permissions' => [
-                        'authenticated',
-                        'edit',
-                        'delete',
-                        //etc..
-                    ]
-                ],
-                'user' => [
-                    'permissions' => [
-                        'authenticated',
-                        //etc..
-                    ]
-                ]
+        'admin' => [
+            'permissions' => [
+                'authenticated',
+                'edit',
+                'delete',
+                //etc..
             ]
+        ],
+        'user' => [
+            'permissions' => [
+                'authenticated',
+                //etc..
+            ]
+        ]
+    ]
 ```
 
 The `authorization-guards.global.php` file defines which permissions are required to access specific route handlers. These permissions must first be declared in the authorization.global.php (dot-rbac) configuration file.

docs/book/v6/how-to/creating-fixtures.md

@@ -2,8 +2,7 @@
 
 > Fixtures are used to seed the database with initial values and should only be executed ONCE each, after migrating the database.
 
-Seeding the database is done with the help of our custom package `dotkernel/dot-data-fixtures` built on top of `doctrine/data-fixtures`.
-See below on how to use our CLI command for listing and executing Doctrine data fixtures.
+Seeding the database is done with the help of our custom package `dotkernel/dot-data-fixtures` built on top of `doctrine/data-fixtures`. See below on how to use our CLI command for listing and executing Doctrine data fixtures.
 
 ## Working with fixtures
 
@@ -12,19 +11,19 @@ You can find an example of a fixtures class in `src/Core/src/App/src/Fixture/Adm
 To list all the available fixtures by order of execution run:
 
 ```shell
-php bin/doctrine fixtures:list
+php ./bin/doctrine fixtures:list
 ```
 
 To execute all fixtures run:
 
 ```shell
-php bin/doctrine fixtures:execute
+php ./bin/doctrine fixtures:execute
 ```
 
 To execute a specific fixture, use its class name, like in this example:
 
 ```shell
-php bin/doctrine fixtures:execute --class=AdminLoader
+php ./bin/doctrine fixtures:execute --class=AdminLoader
 ```
 
 Fixtures can and should be ordered to ensure database consistency.

docs/book/v6/how-to/creating-migrations.md

@@ -4,7 +4,7 @@ Migrations are used to create and/or edit the database structure.
 To generate a new migration file, use this command:
 
 ```shell
-php vendor/bin/doctrine-migrations migrations:generate
+php ./vendor/bin/doctrine-migrations migrations:generate
 ```
 
 It creates a PHP file like this one `src/Core/src/App/src/Migration/Version20240627134952.php` that can then be edited in the IDE.

docs/book/v6/how-to/csrf.md

@@ -23,7 +23,7 @@ Open the form's PHP class and append the following code to the method that initi
 
 ```php
 $this->add(
-    (new Csrf('exampleCsrf'))
+    (new \Laminas\Form\Element\Csrf('exampleCsrf'))
         ->setOptions([
             'csrf_options' => ['timeout' => 3600, 'session' => new Container()],
         ])
@@ -39,7 +39,7 @@ Open the InputFilter that validates the form fields and append the following cod
 fields (usually `init`):
 
 ```php
-$this->add(new CsrfInput('exampleCsrf'));
+$this->add(new \Admin\App\InputFilter\Input\CsrfInput('exampleCsrf'));
 ```
 
 where `exampleCsrf` must match the CSRF field's name in the form.
@@ -50,28 +50,23 @@ where `exampleCsrf` must match the CSRF field's name in the form.
 
 ### Render field
 
-Open the template that renders your form and add the following code somewhere between the form's opening and closing
-tags:
+Open the template that renders your form and add the following code somewhere between the form's opening and closing tags:
 
 ```text
 {{ formElement(form.get('exampleCsrf')) }}
 ```
 
 ## Test the implementation
 
-Access your form from the browser and view its source. You should see a new hidden field, called `exampleCsrf` (or
-however you named it). After filling out the form, submitting it should work as before.
+Access your form from the browser and view its source. You should see a new hidden field, called `exampleCsrf` (or however you named it). After filling out the form, submitting it should work as before.
 
-In order to make sure that the new CSRF field works as expected, you can inspect the form using your browser's
-`Developer tools` and modify its value in any way. Submitting a filled out form should result in a validation error:
+In order to make sure that the new CSRF field works as expected, you can inspect the form using your browser's `Developer tools` and modify its value in any way. Submitting a filled out form should result in a validation error:
 
 > This field is required and cannot be empty.
 
 ### Timeout
 
-Note the `timeout` option in your PHP form's `exampleCsrf` field, with its default value set to **3600**. This
-represents the value in seconds for how long the token is valid. Submitting a form that has been rendered for longer
-than this value will result in a validation error:
+Note the `timeout` option in your PHP form's `exampleCsrf` field, with its default value set to **3600**. This represents the value in seconds for how long the token is valid. Submitting a form that has been rendered for longer than this value will result in a validation error:
 
 > Invalid CSRF.
 

docs/book/v6/how-to/dependency-injection.md

@@ -35,8 +35,7 @@ class GetAccountLogoutHandler implements RequestHandlerInterface
 
 > If your class needs the value of a specific configuration key, you can specify the path using dot notation: `config.example`
 
-The next step is to register the class in the `ConfigProvider` under `factories` using
-`Dot\DependencyInjection\Factory\AttributedServiceFactory::class`.
+The next step is to register the class in the `ConfigProvider` under `factories` using `Dot\DependencyInjection\Factory\AttributedServiceFactory::class`.
 
 ```php
 public function getDependencies(): array

docs/book/v6/installation/composer.md

@@ -32,7 +32,7 @@ Package operations: 171 installs, 0 updates, 0 removals
 
 The setup script prompts for some configuration settings, for example the lines below:
 
-```shell
+```text
 Please select which config file you wish to inject 'Laminas\Validator\ConfigProvider' into:
   [0] Do not inject
   [1] config/config.php
@@ -46,7 +46,9 @@ Type `0` to select `[0] Do not inject`.
 
 The next question is:
 
-`Remember this option for other packages of the same type? (y/N)`
+```text
+Remember this option for other packages of the same type? (y/N)
+```
 
 Type `y` here, and hit `enter` to complete this stage.
 

docs/book/v6/installation/configuration-files.md

@@ -5,8 +5,7 @@
 > If you intend to send emails from your Frontend, make sure to fill in SMTP connection params.
 > This will be covered in the next section.
 
-> **optional**: in order to run/create tests, duplicate `config/autoload/local.test.php.dist` as `config/autoload/local.test.php`
-> this creates a new in-memory database that your tests will run on.
+> **optional**: in order to run/create tests, duplicate `config/autoload/local.test.php.dist` as `config/autoload/local.test.php` this creates a new in-memory database that your tests will run on.
 
 If you want your application to send mail, add valid credentials to the following keys in `config/autoload/mail.global.php`
 
@@ -15,13 +14,6 @@ Under `message_options` key:
 - `from` - email address that will send emails (required)
 - `from_name` - organization name for signing sent emails (optional)
 
-Under `smtp_options` key:
-
-- `host` - hostname or IP address of the mail server (required)
-- `connection_config` - add the `username` and `password` keys (required)
-
-In `config/autoload/local.php` edit the key `contact` => `message_receivers` => `to` with *string* values for emails that should receive contact messages.
-
 > **Please add at least 1 email address in order for contact message to reach someone**
 
-Also feel free to add as many CCs as you require under the `contact` => `message_receivers` => `cc` key.
+Also feel free to add as many CCs as you require under the `dot_mail` => `default` => `message_options` => `cc` key.

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

@@ -33,21 +33,21 @@ $databases = [
 Run the database migrations by using the following command:
 
 ```shell
-php vendor/bin/doctrine-migrations migrate
+php ./vendor/bin/doctrine-migrations migrate
 ```
 
-Note: If you have already run the migrations, you may get this message.
-You should double-check to make sure the new migrations are ok to run.
+> If you have already run the migrations, you may get this message.
+> You should double-check to make sure the new migrations are ok to run.
 
-```shell
+```text
 WARNING! You have x previously executed migrations in the database that are not registered migrations.
   {migration list}
 Are you sure you wish to continue? (y/n)
 ```
 
 When using an empty database, you will get this confirmation message instead.
 
-```shell
+```text
 WARNING! You are about to execute a migration in database "<your_database_name>" that could result in schema changes and data loss. Are you sure you wish to continue? (yes/no)
 ```
 
@@ -56,7 +56,7 @@ Each migration will be logged in the `migrations` table to prevent running the s
 
 If everything ran correctly, you will get this confirmation.
 
-```shell
+```text
 [OK] Successfully migrated to version: Core\App\Migration\Version20250407142911
 ```
 
@@ -67,7 +67,7 @@ If everything ran correctly, you will get this confirmation.
 Run this command to populate the admin tables with the default values:
 
 ```shell
-php bin/doctrine fixtures:execute
+php ./bin/doctrine fixtures:execute
 ```
 
 You should see our galloping horse in the command line.

docs/book/v6/installation/manage-geolite2.md

@@ -3,13 +3,13 @@
 You can download/update a specific GeoLite2 database, by running the following command where `{DATABASE}` can be `asn`, `city`, `country`:
 
 ```shell
-php bin/cli.php geoip:synchronize -d {DATABASE}
+php ./bin/cli.php geoip:synchronize -d {DATABASE}
 ```
 
 You can download/update all GeoLite2 databases at once, by running the following command:
 
 ```shell
-php bin/cli.php geoip:synchronize
+php ./bin/cli.php geoip:synchronize
 ```
 
 The output should be similar to the below, displaying per row: `database identifier`: `previous build datetime` -> `current build datetime`.
@@ -25,7 +25,7 @@ country: n/a -> 2024-11-01 02:25:09
 Get help for this command by running:
 
 ```shell
-php bin/cli.php help geoip:synchronize
+php ./bin/cli.php help geoip:synchronize
 ```
 
-**Tip**: If you set up the synchronizer command as a cronjob, you can add the `-q|--quiet` option, and it will output data only if an error has occurred.
+> If you set up the synchronizer command as a cronjob, you can add the `-q|--quiet` option, and it will output data only if an error has occurred.

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

@@ -4,18 +4,18 @@
 
 We recommend running your applications in WSL:
 
-- Make sure you have [WSL](https://github.com/dotkernel/development/blob/main/wsl/README.md) installed on your system.
-- Currently we provide a distro implementations for [AlmaLinux9](https://github.com/dotkernel/development/blob/main/wsl/os/almalinux9/README.md).
+- Make sure you have [WSL2](https://docs.dotkernel.org/development/v2/setup/system-requirements/) installed on your system.
+- Currently we provide a distro implementations for [AlmaLinux9](https://github.com/dotkernel/development/blob/main/wsl/README.md).
 - Install the application in a virtualhost as recommended by the chosen distro.
 - Set `$baseUrl` in **config/autoload/local.php** to the address of the virtualhost.
 - Run the application by opening the virtualhost address in your browser.
 
-You should see the `Dotkernel admin` login page.
+You should see the `Dotkernel Admin` login page.
 
 > If you are getting exceptions or errors regarding some missing services, try running the following command:
 
 ```shell
-sudo php bin/clear-config-cache.php
+sudo php ./bin/clear-config-cache.php
 ```
 
 > If `config-cache.php` is present that config will be loaded regardless of the `ConfigAggregator::ENABLE_CACHE` in `config/autoload/mezzio.global.php`
@@ -40,4 +40,4 @@ return [
 ];
 ```
 
-Do not change this in `local.php.dist` as well because this value should remain `true` on production.
+> Do not change this in `local.php.dist` as well because this value should remain `true` on production.