Update dx.md

Author: oblomov-dev

docs/technical/dx.md

@@ -229,22 +229,22 @@ A common frustration in frontend development is caching — especially with BSP
 
 There's often debate about which IDE to use — but why not let everyone choose the tool they prefer? abap2UI5 apps are developed entirely in ABAP. You can work in ADT, rely on the time-tested SE80, or even explore integration with VS Code:
 
-- No additional setup required — works in any ABAP IDE  
-- Ideal for teams with different tooling preferences  
+- No additional setup required — works in any IDE  
+- Ideal for teams with different tooling preferences
 
 ##### Pure ABAP Debugging
 
 Frontend-heavy applications often require switching between browser dev tools, JavaScript logs, and network inspectors. With abap2UI5, the UI is pure ABAP — no JavaScript, no additional layers. Just set a breakpoint in your ABAP method:
 
-- Backend-only debugging with the classic SE80 debugger or ADT  
-- No need for browser debugging tools  
+- Backend-only debugging with the classic SE80 debugger or ADT
+- No need for browser debugging tools
 
 ##### Easy Code Sharing
 
 Sharing your apps or code is simple. Since abap2UI5 apps are standard ABAP classes, they can be shared via abapGit or even copy-pasted. No configuration files, manifests, or build tools required:
 
-- Easy to clone and test other apps  
-- Great for collaboration and code reviews  
+- Easy to clone and test other apps
+- Great for collaboration and code reviews
 - Encourages modular, reusable components
 
 ### Summary