Update over_the_wire.md

Author: oblomov-dev

docs/advanced/technical/over_the_wire.md

@@ -1,6 +1,6 @@
 # Over-the-Wire: An Introduction for Business Applications
 
-## Background: Why is this relevant again?
+### Background: Why is this relevant again?
 
 In the early days of web development, **all websites were server-rendered**.  
 Each user action, like clicking a link or submitting a form, triggered a full-page reload, with the server delivering the complete HTML response.
@@ -9,7 +9,7 @@ With the rise of **Single Page Applications (SPAs)**, this changed. SPAs moved U
 
 Today, **Over-the-Wire approaches revisit the original idea of server-side rendering**, but with modern techniques. Instead of sending entire pages, only small HTML fragments or UI updates are transferred, combining simplicity with interactivity.
 
-## What is "Over the Wire"?
+### What is "Over the Wire"?
 
 **Over-the-Wire** refers to a development approach where the server generates and sends **ready-to-render HTML fragments** directly to the client (browser).  
 Unlike modern Single Page Applications (SPAs), which rely on JSON data and complex client-side rendering, Over-the-Wire keeps the frontend logic minimal and leverages server-side rendering for both initial load and dynamic updates.
@@ -20,7 +20,7 @@ In simple terms:
 
 This approach reduces complexity and is especially suitable for applications where business logic resides on the server.
 
-## How does it differ from Single Page Applications (SPA)?
+### How does it differ from Single Page Applications (SPA)?
 
 In a typical SPA:
 - The client requests **raw data** (e.g., JSON) from the server.
@@ -32,29 +32,29 @@ In contrast, with Over-the-Wire:
 
 This shifts the responsibility for UI rendering back to the server, simplifying the frontend layer.
 
-## Benefits of Over-the-Wire for Business Applications
+### Benefits of Over-the-Wire for Business Applications
 
 - **Reduced Frontend Complexity**: No need for heavy JavaScript frameworks or complex build pipelines.
 - **Faster Time-to-Market**: Leveraging existing backend logic accelerates development.
 - **Better SEO & Accessibility**: Server-rendered HTML is immediately visible and indexable.
 - **Lower Maintenance Effort**: Fewer dependencies and simpler architecture.
 - **Efficient for CRUD Applications**: Ideal for forms, tables, dashboards, and admin tools.
 
-## Typical Use Cases
+### Typical Use Cases
 
 - Internal business applications
 - ERP, CRM, and administrative tools
 - Data entry forms and report views
 - Applications with limited interactivity requirements
 
-## Limitations to Consider
+### Limitations to Consider
 
 While Over-the-Wire offers significant advantages for backend-driven applications, it is less suitable for:
 - Highly interactive, real-time collaboration tools (e.g., design apps, chat platforms)
 - Applications requiring offline capabilities or rich client-side interactions
 - Scenarios where frontend and backend are developed by separate, independent teams
 
-## Popular Frameworks and Tools Following Over-the-Wire Principles
+### Popular Frameworks and Tools Following Over-the-Wire Principles
 
 | Framework | Primary Use | Technology Stack |
 |-----------|-------------|-----------------|
@@ -67,14 +67,14 @@ While Over-the-Wire offers significant advantages for backend-driven application
 | **[Inertia.js](https://inertiajs.com/)** | SPA-like experience without APIs | JavaScript + Laravel/Rails |
 
 
-## Conclusion
+### Conclusion
 
 Over-the-Wire represents a pragmatic approach for building web applications where the **server remains in control of UI rendering**.  
 It aligns well with business contexts that prioritize **simplicity, maintainability, and tight integration of backend and frontend logic**.
 
 For typical business applications—such as dashboards, forms, and administrative tools—Over-the-Wire offers a lean and efficient alternative to heavy SPA architectures.
 
-## Over-the-Wire and abap2UI5
+### Over-the-Wire and abap2UI5
 
 The **abap2UI5** framework adopts the fundamental idea of Over-the-Wire, but with a specific focus on SAP development environments.  
 Instead of sending raw data to a generic frontend application, abap2UI5 delivers a **view and corresponding view model** from the ABAP backend to the client.