Fixed versioning URLs and other small fixes

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

Author: alexmerlin

docs/book/v4/transition-from-api-tools/discovery-phase.md

@@ -1,33 +1,32 @@
 # Discovery phase for a current system built using API Tools [WIP]
 
-In order to transition a system built using api-tools to Dotkernel API , we need to analyze the core components
-of it.
+To transition a system built using api-tools to Dotkernel API, we need to analyze the core components of it.
 
 ## Database
 
-- there is a database in the current API ?
-- which is the connection to database
-- which library is used for database interaction ( laminas-db, doctrine 2, eloquent, or else )
+- is there a database in the current API?
+- which is the connection to a database
+- which library is used for database interaction (laminas-db, doctrine 2, eloquent, or else)?
 
 ### Note
 
-> Dotkernel API is tested only with MariaDB version 10.6 and 10.11 LTS
+>  Dotkernel API is tested only with MariaDB version 10.6, 10.11 LTS, 11.4 LTS, and 11.8 LTS
 
 ## Authentication and Authorization
 
-- how authentication is done ? (basic, digest, oauth2, etc.)
-- how authorization is done ?  (acl, rbac)
+- how is authentication done? (basic, digest, oauth2, etc.)
+- how is authorization done? (acl, rbac)
 
 ## Modules
 
-- analyze configuration files of the modules (what needs to be configured in order to use a module)
-- analyze routes (which are the routes, protection rules, which one need auth, etc.)
-- analyze response format (content negotiation and validation, which ones are json, hal, views, etc.)
+- analyze configuration files of the modules (what needs to be configured to use a module)
+- analyze routes (which are the routes, protection rules, which one needs auth, etc.)
+- analyze a response format (content negotiation and validation, which ones are JSON, hal, views, etc.)
 - analyze input field validations
 
 ## Custom functionalities
 
-Analyze the custom code (code that cannot be generated through Admin UI and require manual implementation)
+Analyze the custom code (code that cannot be generated through Admin UI and requires manual implementation)
 
 For instance:
 

docs/book/v4/transition-from-api-tools/transition-approach.md

@@ -1,21 +1,14 @@
 # Transition approach  [WIP]
 
-Dotkernel API is not a one-to-one replacement of api-tools ( former Apigility), but is only a potential solution to
-migrate to.
+Dotkernel API is not a one-to-one replacement of api-tools (former Apigility), but is only a potential solution to migrate to.
 
 Functionalities, components and architecture are different.
 
-See
-the [Comparison between Dotkernel APi and api-tools](https://docs.dotkernel.org/api-documentation/v4/transition-from-api-tools/api-tools-vs-dotkernel-api/)
+See the [Comparison between Dotkernel APi and api-tools](https://docs.dotkernel.org/api-documentation/v4/transition-from-api-tools/api-tools-vs-dotkernel-api/).
 
 ## Business cases
 
-There are at least 2 approaches for this transition:
+There are at least two approaches for this transition:
 
-### Clone 1:1
-
-and recreate all endpoints and entities
-
-### Build a new version of the current API using Dotkernel API
-
-and keep it running as separate platforms until the sunset of the current version of api-tools
+- Clone 1:1 and recreate all endpoints and entities
+- Build a new version of the current API using Dotkernel API and keep it running as separate platforms until the sunset of the current version of api-tools

docs/book/v5/transition-from-api-tools/discovery-phase.md

@@ -114,8 +114,6 @@ nav:
           - "Find user by identity": v5/tutorials/find-user-by-identity.md
       - Transition from API Tools:
           - "Laminas API Tools vs Dotkernel API": v5/transition-from-api-tools/api-tools-vs-dotkernel-api.md
-          - "Transition Approach": v5/transition-from-api-tools/transition-approach.md
-          - "Discovery Phase": v5/transition-from-api-tools/discovery-phase.md
       - OpenAPI:
             - "Introduction": v5/openapi/introduction.md
             - "Initialized Components": v5/openapi/initialized-components.md
@@ -159,8 +157,6 @@ nav:
           - "Token authentication": v4/tutorials/token-authentication.md
       - Transition from API Tools:
           - "Laminas API Tools vs Dotkernel API": v4/transition-from-api-tools/api-tools-vs-dotkernel-api.md
-          - "Transition Approach": v4/transition-from-api-tools/transition-approach.md
-          - "Discovery Phase": v4/transition-from-api-tools/discovery-phase.md
 site_name: api
 site_description: "Dotkernel API"
 repo_url: "https://github.com/dotkernel/api"