linting fixes

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

Author: bidi47

docs/book/v7/core-features/authentication.md

@@ -141,18 +141,18 @@ The response contains a new `access_token` and `refresh_token`:
 
 ## Common Issues
 
-**"Invalid credentials" error**
+### "Invalid credentials" error
 
 - Check username/password are correct.
 - Verify client_id and client_secret match OAuth client in the database.
 - Confirm the user account exists and is active.
 
-**"Token has expired" error**
+### "Token has expired" error
 
 - Use refresh_token to get a new access_token.
 - If refresh_token is expired, re-authenticate with credentials.
 
-**"Invalid scope" error**
+### "Invalid scope" error
 
 - Verify `scope` field is set to `"api"` (the only configured scope)
 

docs/book/v7/installation/composer.md

@@ -21,9 +21,9 @@ The automatic setup script performs these tasks:
 - 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
+    - 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 `[...]`.
 

docs/book/v7/introduction/architecture-at-a-glance.md

@@ -21,7 +21,7 @@ Location: `src/Core/src/`
 
 You typically don't modify Core unless you're updating system behavior or adding shared infrastructure features.
 
-## App Layer
+### App Layer
 
 The **App** is where you build your project-specific features—the "business logic" of your application:
 
@@ -36,7 +36,7 @@ Location: `src/App/src/`
 
 You spend most development time here, implementing your API's features and business logic.
 
-# Headless CMS Architecture
+## Headless CMS Architecture
 
 Dotkernel API is built toward a Headless CMS architecture:
 
@@ -71,7 +71,7 @@ Dotkernel API is built toward a Headless CMS architecture:
                     └───────────────────────────────────┘
 ```
 
-# Modular Design
+## Modular Design
 
 Applications are organized into modules, each handling a specific domain.
 
@@ -85,7 +85,7 @@ Applications are organized into modules, each handling a specific domain.
 
 Custom Modules: You can create your own modules (e.g., Book, Product, Article) following the same pattern.
 
-## Request Flow
+### Request Flow
 
 Here's how a typical request flows through Dotkernel API:
 
@@ -112,9 +112,9 @@ Here's how a typical request flows through Dotkernel API:
 5. HTTP Response
 ```
 
-# Key Components
+## Key Components
 
-## Handlers (PSR-15)
+### Handlers (PSR-15)
 
 Single-action request handlers instead of multi-action controllers:
 
@@ -129,7 +129,7 @@ src/User/src/Handler/
 
 Benefits: Separation of concerns, easier testing, clearer intent.
 
-## Services
+### Services
 
 The Business logic layer sits between the handlers and repositories:
 
@@ -143,23 +143,23 @@ Services handle:
 - Data transformation
 - Cross-cutting concerns (caching, logging)
 
-## Repositories
+### Repositories
 
 Data access layer using Doctrine ORM:
 
 - Query building
 - Entity persistence
 - Database abstraction
 
-## Input Filters
+### Input Filters
 
 Request validation using Laminas InputFilter:
 
 ```quote
 Request → InputFilter → Validation → Handler
 ```
 
-## Entities
+### Entities
 
 Doctrine ORM entities representing database tables:
 
@@ -169,7 +169,7 @@ Doctrine ORM entities representing database tables:
 class User { ... }
 ```
 
-# Configuration Organization
+## Configuration Organization
 
 ```quote
 config/
@@ -184,7 +184,7 @@ config/
 └─ local.php                      (Environment-specific, ignored by VCS, private config)
 ```
 
-# Dependency Injection
+## Dependency Injection
 
 Dotkernel API uses constructor injection with attributes:
 
@@ -206,7 +206,7 @@ class UserHandler
 
 Services are automatically resolved and injected by AttributedServiceFactory.
 
-# Data Flow Architecture
+## Data Flow Architecture
 
 ```quote
 ┌─────────────────────────────────────────┐
@@ -248,7 +248,7 @@ Services are automatically resolved and injected by AttributedServiceFactory.
 └─────────────────────────────────────────┘
 ```
 
-# Standards & PSRs
+## Standards & PSRs
 
 Dotkernel API adheres to PHP standards for interoperability:
 
@@ -259,7 +259,7 @@ Dotkernel API adheres to PHP standards for interoperability:
 
 This ensures your code can integrate with other PSR-compliant libraries.
 
-# Security Layers
+## Security Layers
 
 ```quote
 ┌─────────────────────────────┐
@@ -277,12 +277,12 @@ This ensures your code can integrate with other PSR-compliant libraries.
 └─────────────────────────────┘
 ```
 
-# When to Use Each Layer
+## When to Use Each Layer
 
-| Layer       |          Purpose           |                              Example |
-|-------------|:--------------------------:|-------------------------------------:|
-| Core	       |   System infrastructure	   |       Authentication, database setup |
-| App	        |     Project features	      |   User CRUD operations, custom logic |
-| Handler     | 	Request/response mapping	 |        Extract user ID, call service |
-| Service	    |      Business rules	       | Validate user data, calculate totals |
-| Repository  |       Data queries	        |              Find users, save entity |
+| Layer      |         Purpose          |                              Example |
+|------------|:------------------------:|-------------------------------------:|
+| Core       |  System infrastructure   |       Authentication, database setup |
+| App        |     Project features     |   User CRUD operations, custom logic |
+| Handler    | Request/response mapping |        Extract user ID, call service |
+| Service    |      Business rules      | Validate user data, calculate totals |
+| Repository |       Data queries       |              Find users, save entity |

docs/book/v7/introduction/introduction.md

@@ -23,12 +23,12 @@ Below are some practical use cases (it's by no means an exhaustive list).
 
 Below is a quick overview of features in Dotkernel API and how they interconnect.
 
-| Feature	             | Purpose	                            | Configuration                                  |
-|----------------------|-------------------------------------|------------------------------------------------|
-| OAuth2	              | Authentication	                     | config/autoload/local.php                      |
-| RBAC	                | Authorization	                      | config/autoload/authorization.global.php       |
-| Content Negotiation	 | Request/response format validation	 | config/autoload/content-negotiation.global.php |
-| OpenAPI/Swagger	     | API documentation	                  | Auto-generated                                 |
+| Feature             | Purpose                            | Configuration                                  |
+|---------------------|------------------------------------|------------------------------------------------|
+| OAuth2              | Authentication                     | config/autoload/local.php                      |
+| RBAC                | Authorization                      | config/autoload/authorization.global.php       |
+| Content Negotiation | Request/response format validation | config/autoload/content-negotiation.global.php |
+| OpenAPI/Swagger     | API documentation                  | Auto-generated                                 |
 
 ## Doctrine 3 ORM
 

docs/book/v7/introduction/psr.md

@@ -8,15 +8,15 @@
 - **Long-Term Maintenance**: PSRs are stable standards maintained by the PHP community, ensuring longevity.
 - **Code Quality**: Following standards encourages best practices and makes code more maintainable.
 
-## PSRs (PHP Standards Recommendations)
+## PHP Standards Recommendations (PSRs)
 
 Dotkernel API adheres to PHP Standards Recommendations (PSRs) established by the PHP-FIG (Framework Interoperability Group). These standards ensure code interoperability and allow Dotkernel API to work seamlessly with other PSR-compliant libraries.
 
 Some PSRs are at the **core** of Dotkernel API's architecture, while others are installed as dependencies through third-party packages.
 
-# Core PSRs (Essential to Dotkernel API)
+## Core PSRs (Essential to Dotkernel API)
 
-## PSR-7: HTTP Message Interfaces
+### PSR-7: HTTP Message Interfaces
 
 **Repository**: [php-fig/http-message](https://github.com/php-fig/http-message)
 
@@ -29,7 +29,7 @@ Defines standardized interfaces for HTTP messages (requests and responses) and U
 - Allows middleware and handlers to work with consistent interfaces.
 - Implemented via `Laminas\Diactoros`.
 
-## PSR-15: HTTP Server Request Handlers and Middleware
+### PSR-15: HTTP Server Request Handlers and Middleware
 
 **Repository**: [php-fig/http-server-handler](https://github.com/php-fig/http-server-handler) and [php-fig/http-server-middleware](https://github.com/php-fig/http-server-middleware)
 
@@ -42,7 +42,7 @@ Defines the interface for HTTP request handlers and middleware components that p
 - Middleware pipeline processes requests in a chain.
 - Single-action handlers follow this pattern for clean separation of concerns.
 
-## PSR-11: Container Interface
+### PSR-11: Container Interface
 
 **Repository**: [php-fig/container](https://github.com/php-fig/container)
 
@@ -55,9 +55,9 @@ Defines the standard interface for dependency injection containers.
 - Enables loose coupling between components.
 - Implemented via `Laminas\ServiceManager`.
 
-# Supporting PSRs (Installed via Dependencies)
+## Supporting PSRs (Installed via Dependencies)
 
-## PSR-3: Logger Interface
+### PSR-3: Logger Interface
 
 **Repository**: [php-fig/log](https://github.com/php-fig/log)
 
@@ -66,7 +66,7 @@ Provides a standard interface for logging libraries.
 **Usage**: Error handling, debugging, audit trails
 **Implemented in**: `dotkernel/dot-errorhandler`
 
-## PSR-4: Autoloader
+### PSR-4: Autoloader
 
 **Repository**: [php-fig/log](https://github.com/php-fig/log)
 
@@ -75,7 +75,7 @@ Defines how PHP files are automatically loaded based on namespaces and file path
 **Usage**: Automatic class loading without manual `require` statements
 **Implemented in**: `Laminas\Loader`
 
-## PSR-6: Caching Interface
+### PSR-6: Caching Interface
 
 **Repository**: [php-fig/cache](https://github.com/php-fig/cache)
 
@@ -84,7 +84,7 @@ Defines standard interfaces for caching systems to improve application performan
 **Usage**: Caching query results, configuration, templates
 **Implemented in**: `dotkernel/dot-cache`
 
-## PSR-13: Link Definition Interfaces
+### PSR-13: Link Definition Interfaces
 
 **Repository**: [php-fig/link](https://github.com/php-fig/link)
 
@@ -93,7 +93,7 @@ Describes how to represent hypermedia links independently of serialization forma
 **Usage**: HAL (Hypertext Application Language) resource links
 **Implemented in**: `mezzio/mezzio-hal`
 
-## PSR-14: Event Dispatcher
+### PSR-14: Event Dispatcher
 
 **Repository**: [php-fig/event-dispatcher](https://github.com/php-fig/event-dispatcher)
 
@@ -102,7 +102,7 @@ Mechanism for event-based extension and collaboration between components.
 **Usage**: Triggering events on user actions, logging events, notifications
 **Implemented in**: Third-party packages as needed
 
-## PSR-17: HTTP Factories
+### PSR-17: HTTP Factories
 
 **Repository**: [php-fig/http-factory](https://github.com/php-fig/http-factory)
 
@@ -111,7 +111,7 @@ Standard for factories that create PSR-7 compliant HTTP objects.
 **Usage**: Creating requests, responses, and streams programmatically
 **Implemented in**: `Laminas\Diactoros`
 
-## PSR-18: HTTP Client
+### PSR-18: HTTP Client
 
 **Repository**: [php-fig/http-client](https://github.com/php-fig/http-client)
 
@@ -120,7 +120,7 @@ Interface for sending HTTP requests and receiving HTTP responses.
 **Usage**: Calling external APIs from your Dotkernel API
 **Implemented in**: `symfony/http-client` or similar packages
 
-## PSR-20: Clock
+### PSR-20: Clock
 
 **Repository**: [php-fig/clock](https://github.com/php-fig/clock)
 
@@ -129,7 +129,7 @@ Provides a standard interface for reading the system clock.
 **Usage**: Getting current time in a testable way
 **Implemented in**: Third-party packages as needed
 
-## PSR Implementation Hierarchy
+### PSR Implementation Hierarchy
 
 ```quote
 ┌───────────────────────────────────────────┐
@@ -155,9 +155,8 @@ Provides a standard interface for reading the system clock.
 └───────────────────────────────────────────┘
 ```
 
-# Next Steps
+## Next Steps
 
 - Review PSR-7 and PSR-15 in detail—these are essential for understanding Dotkernel API.
 - Check individual PSR pages for implementation examples.
 - Consider how PSRs apply to your custom code and modules.
-

docs/book/v7/introduction/server-requirements.md

@@ -23,8 +23,8 @@ Windows is supported for development via WSL2.
 
 ### Apache >= 2.2
 
-* mod_rewrite
-* .htaccess support `(AllowOverride All)`
+- mod_rewrite
+- .htaccess support `(AllowOverride All)`
 
 > The repository includes a default `.htaccess` file in the `public` folder.
 
@@ -95,20 +95,20 @@ When creating databases, use:
 
 ## Recommended extensions
 
-* `opcache`
-* `pdo_mysql`, `pdo_pgsql` or `mysqli` (if using MariaDB or PostgreSQL as RDBMS)
-* `dom` - if working with markup files structure (HTML, XML, etc.)
-* `simplexml` - working with XML files
-* `gd`, `exif` - if working with images
-* `zlib`, `zip`, `bz2` - if compressing files
-* `curl` (required if APIs are used)
-* `sqlite3` - for tests
+- `opcache`
+- `pdo_mysql`, `pdo_pgsql` or `mysqli` (if using MariaDB or PostgreSQL as RDBMS)
+- `dom` - if working with markup files structure (HTML, XML, etc.)
+- `simplexml` - working with XML files
+- `gd`, `exif` - if working with images
+- `zlib`, `zip`, `bz2` - if compressing files
+- `curl` (required if APIs are used)
+- `sqlite3` - for tests
 
-# Composer
+## Composer
 
 Dotkernel API requires Composer >= 2.0 for managing PHP dependencies.
 
-# Security Considerations
+## Security Considerations
 
 - **Firewall**: Only expose ports 80 (HTTP) and 443 (HTTPS)
 - **PHP**: Disable dangerous functions: exec, shell_exec, passthru, system