Update concept.md

Author: oblomov-dev

docs/advanced/technical/concept.md

@@ -1,32 +1,37 @@
 # Key Concept: UI5 Over-the-Wire?
 
-This page outlines the technical foundation of abap2UI5. At its core is an architectural model known as HTML Over-the-Wire, adapted to SAP-specific technologies. This approach streamlines UI5 app development by shifting both UI rendering and application logic to the ABAP backend.
+This page introduces the technical foundation of abap2UI5. At its core is an architectural model known as HTML Over-the-Wire, adapted to SAP-specific technologies. This approach streamlines UI5 app development by shifting both UI rendering and application logic to the ABAP backend.
 
 #### What is HTML Over-the-Wire?
 
-HTML Over-the-Wire describes a server-centric web architecture in which the user interface is rendered on the server and transmitted to the browser as ready-to-use HTML. This eliminates the need for OData data transfers, client-side MVC frameworks, and complex deployments. All application logic remains fully on the server [(1)](https://signalvnoise.com/svn3/html-over-the-wire/):
+HTML Over-the-Wire describes a server-centric web architecture in which the user interface is rendered on the server and transmitted to the browser as ready-to-use HTML. 
+
+Instead of building complex JavaScript frontends and dealing with APIs and JSON, the server takes care of everything: it renders the UI and sends HTML directly to the browser. No need for client-side MVC frameworks, no JSON conversions, and no complicated deployment processes [(1)](https://signalvnoise.com/svn3/html-over-the-wire/):
 
 > You can write fast, modern, responsive web applications by generating your HTML on the server, and delivering that directly to the browser. You don’t need JSON as an in-between format. You don’t need client-side MVC frameworks. You don’t need complicated bundling and transpiling pipelines.
 
 > This is what HTML Over The Wire is all about. It’s a celebration of the simplicity in HTML as the format for carrying data and presentation together, whether this is delivered on the first load or with subsequent dynamic updates.
 
-In contrast to client-side JavaScript frameworks, which offload most responsibilities to the browser, HTML Over-the-Wire keeps control on the backend. The initial request delivers all necessary JavaScript and CSS, and from then on, only partial HTML fragments are sent via AJAX, which the browser inserts without reloading the entire page.
+In this architecture:
+- The first request loads the basic JavaScript and CSS.
+- After that, the server only sends HTML fragments when needed.
+- The browser simply inserts those into the DOM. No full reloads required.
+
+This keeps the frontend clean and simple — just a rendering layer, while all logic stays in the backend:
 
 <img width="400" alt="image" src="https://github.com/user-attachments/assets/a9fde24a-c572-4e5c-b203-59a0667b9931" />
 
 _HTML "Over the Wire" Lifecycle [(2)](https://community.sap.com/t5/technology-blog-posts-by-members/fiori-like-web-app-development-in-pure-abap-with-htmx-and-fundamental/ba-p/13500763)_
 
-Several frameworks adopt this pattern:
+Several modern frameworks follow this pattern:
+* [htmx](https://htmx.org), Progressive enhancement via HTML partials, Any web stack
+* [Hotwire (Turbo)](https://hotwired.dev), HTML-over-the-wire for Rails apps, Ruby on Rails
+* [Phoenix LiveView](https://hexdocs.pm/phoenix_live_view), Real-time UI with server rendering,, Elixir / Phoenix
+* [Livewire](https://livewire.laravel.com), Server-driven UI components in PHP, Laravel / PHP
+* [Unpoly](https://unpoly.com), Simplified partial page updates, Any web stack
 
-| Framework             | Focus                                | Tech Stack           |
-|-----------------------|--------------------------------------|----------------------|
-| [htmx](https://htmx.org)                | Progressive enhancement via HTML partials  | Any web stack        |
-| [Hotwire (Turbo)](https://hotwired.dev) | HTML-over-the-wire for Rails apps          | Ruby on Rails        |
-| [Phoenix LiveView](https://hexdocs.pm/phoenix_live_view) | Real-time UI with server rendering         | Elixir / Phoenix     |
-| [Livewire](https://livewire.laravel.com)         | Server-driven UI components in PHP         | Laravel / PHP        |
-| [Unpoly](https://unpoly.com)            | Simplified partial page updates            | Any web stack        |
 
-#### Historical Context
+#### Isn't this just old-school server rendering?
 
 In the early days of web development, Server-Side Rendering (SSR) was the standard. Each user interaction triggered a full-page reload, with the server delivering the complete HTML response. In the SAP ecosystem, this approach was used by technologies such as ITS Mobile and SAP GUI for HTML.