ci fixes

Signed-off-by: Jurj-Bogdan <[email protected]>

Author: Jurj-Bogdan

docs/book/v5/openapi/write-documentation.md

@@ -107,4 +107,4 @@ To summarize, the typical scenario on working on your own instance of Dotkernel
 - create new module (example: `Book`)
 - add functionality to your new module (routes, entities, repositories, handlers, services, tests etc)
 - create file `OpenAPI.php` in the new module and describe each new endpoint
-- generate latest version of documentation file as described [here](./generate-documentation.md)
+- generate latest version of documentation file as described [in this tutorial](./generate-documentation.md)

docs/book/v6/extended-features/handler-structure.md

@@ -38,6 +38,6 @@ In this way, the developer can easily figure out the functionality of each handl
 
 ## Mapping of the handlers
 
-The full mapping of the handlers and their current paths and actions can be found [**here**](https://docs.dotkernel.org/img/api/v6/naming-convention.png).
+The full mapping of the handlers and their current paths and actions can be found in the full [naming convention table](https://docs.dotkernel.org/img/api/v6/naming-convention.png).
 
 [![naming-convention-thumbnail](https://docs.dotkernel.org/img/api/v6/naming-convention-thumbnail.png)](https://docs.dotkernel.org/img/api/v6/naming-convention.png)

docs/book/v6/openapi/write-documentation.md

@@ -107,4 +107,4 @@ To summarize, the typical scenario on working on your own instance of Dotkernel
 - create new module (example: `Book`)
 - add functionality to your new module (routes, entities, repositories, handlers, services, tests etc)
 - create file `OpenAPI.php` in the new module and describe each new endpoint
-- generate latest version of documentation file as described [here](./generate-documentation.md)
+- generate latest version of documentation file as described [in this tutorial](./generate-documentation.md)