fix menu

Author: oblomov-dev

docs/.vitepress/config.mjs

@@ -172,13 +172,13 @@ export default defineConfig({
               { text: 'UI5 Freestyle', link: '/technical/technology/ui5' },
           ] },
             { text: 'Tools',  collapsed : "false" , items: [
-            { text: 'abapGit', link: '/advanced/tools/abapgit' },
-            { text: 'ajson', link: '/advanced/tools/ajson' },
-            { text: 's-rtti', link: '/advanced/tools/srtti' },
-            { text: 'abaplint', link: '/advanced/tools/abaplint' },
-            { text: 'open-abap', link: '/advanced/tools/open_abap' },
-            { text: 'abap-cleaner', link: '/advanced/tools/abap_cleaner' },
-            { text: 'abapmerge', link: '/advanced/tools/abapmerge' },
+            { text: 'abapGit', link: '/technical/tools/abapgit' },
+            { text: 'ajson', link: '/technical/tools/ajson' },
+            { text: 's-rtti', link: '/technical/tools/srtti' },
+            { text: 'abaplint', link: '/technical/tools/abaplint' },
+            { text: 'open-abap', link: '/technical/tools/open_abap' },
+            { text: 'abap-cleaner', link: '/technical/tools/abap_cleaner' },
+            { text: 'abapmerge', link: '/technical/tools/abapmerge' },
           ]
           }
         ]

docs/technical/tools/ajson.md

@@ -1,18 +1,27 @@
 # ajson
 
-abap2UI5 relies heavily on JSON handling for frontend/backend communication, initially using `/UI2/CL_JSON`. Over time, various issues arose because certain functionalities were not available in specific releases and its limited documentation.
+abap2UI5 handles all frontend-backend communication through JSON. Initially, the framework used SAP's `/UI2/CL_JSON`, but this approach proved problematic: critical functionality varied across releases, documentation was sparse, and compatibility issues emerged frequently.
 
-To address these challenges, abap2UI5 uses the open-source project [ajson](https://github.com/sbcgua/ajson) for JSON handling. 
+The solution: [ajson](https://github.com/sbcgua/ajson), a robust open-source JSON library that transformed abap2UI5's architecture.
 
-Using ajson significantly reduces dependencies on SAP APIs. Moreover, it provides a straightforward and reliable approach to JSON handling, thanks to its clear API, excellent documentation, quick support for issue resolution, and best of all — it is compatible from version 702 to ABAP Cloud.
+**Why ajson?**
+* **Zero SAP API Dependencies** - Eliminates reliance on release-specific SAP classes
+* **Universal Compatibility** - Works seamlessly from NW 7.02 to ABAP Cloud
+* **Developer-Friendly** - Intuitive API with comprehensive documentation
+* **Active Maintenance** - Responsive issue resolution and continuous improvements
+* **Battle-Tested** - Proven reliability across diverse ABAP environments
 
 #### Integration
 
-It is integrated into the project under the `z2ui5` namespace and automatically installed with every abap2UI5 installation. You can access it directly using:
+ajson integrates directly into the `z2ui5` namespace and installs automatically with abap2UI5. Access it anywhere in your code:
 ```abap
-z2ui5_cl_ajson=>
+DATA(json) = z2ui5_cl_ajson=>parse( json_string ).
+DATA(output) = z2ui5_cl_ajson=>create_empty( )->set( 
+  iv_path = '/name' 
+  iv_val  = 'value' 
+)->stringify( ).
 ```
 
-#### Updates
+#### Automatic Updates
 
-Every update and bug fix in ajson is automatically reflected in abap2UI5 via GitHub Actions and the [mirror-ajson](https://github.com/abap2UI5/mirror-ajson) repository, ensuring always using the latest version.
+Every ajson update and bug fix flows automatically into abap2UI5 via GitHub Actions and the [mirror-ajson](https://github.com/abap2UI5/mirror-ajson) repository. You're always running the latest stable version without manual intervention.