update

Author: oblomov-dev

docs/.vitepress/config.mjs

@@ -160,7 +160,7 @@ export default defineConfig({
           ] },
           { text: 'Technical Background',  collapsed : "false" , link: '/advanced/insights/insights' , items: [
             { text: 'General', link: '/advanced/insights/insights' },
-            { text: 'abaplint', link: '/advanced/insights/abaplint' },
+            { text: 'Linting', link: '/advanced/insights/linting' },
             { text: 'open-abap', link: '/advanced/insights/open_abap' },
           ]
           },

docs/advanced/insights/abaplint.md docs/advanced/insights/linting.mddocs/advanced/insights/abaplint.md renamed to docs/advanced/insights/linting.md

@@ -1,13 +1,20 @@
 ---
 outline: [2, 4]
 ---
-# abaplint
+# Linting
+
+The frontend JS code and the backend abap code are static code checked with every PR.
+
+### Backend - abaplint
 
 The project uses [abaplint](https://abaplint.app/) for static code analysis, ensuring code quality and adherence to ABAP best practices.
 
-### Configuration
+#### Configuration
 You can review the project-specific abaplint configuration [here.](https://github.com/abap2UI5/abap2UI5/blob/main/ci/abaplint/abaplint.jsonc)
 
-### Dashboard
+#### Dashboard
 All statistics and results from the abaplint analysis are available on the abaplint dashboard [here.](https://abaplint.app/stats/abap2UI5/abap2UI5)
 
+### Frontend - ui5lint
+
+The project uses the [ui5linter]((https://github.com/SAP/ui5-linter)) for static code analysis of frontend artifacts. The linter checks for issues such as deprecated API usage and ensures compatibility with UI5 2.x. The default configuration is applied.