Update concept.md

Author: oblomov-dev

docs/advanced/technical/concept.md

@@ -10,7 +10,7 @@ HTML Over-the-Wire describes a server-centric web architecture in which the user
 
 > 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 delegate most responsibilities to the browser, HTML Over-the-Wire keeps control on the backend. UI updates are performed by sending partial HTML fragments via AJAX, which the browser inserts without reloading the entire page.
+In contrast to client-side JavaScript frameworks, which delegate most responsibilities to the browser, HTML Over-the-Wire keeps control on the backend. The first request sends all needed JS & CSS and then only UI updates are performed by sending partial HTML fragments via AJAX, which the browser inserts without reloading the entire page.
 
 <img width="400" alt="image" src="https://github.com/user-attachments/assets/a9fde24a-c572-4e5c-b203-59a0667b9931" />
 
@@ -28,14 +28,11 @@ Several frameworks adopt this pattern:
 
 #### Historical Context
 
-In early web development, **Server-Side Rendering (SSR)** was the norm. Each user interaction triggered a full-page reload, with the server returning the complete HTML content. In SAP context this is known from ITS Mobile or SAP GUI for HTML.
+In the early days of web development, Server-Side Rendering (SSR) was the standard. Every user interaction triggered a full-page reload, with the server returning the complete HTML. In the SAP world, this approach was familiar from ITS Mobile or SAP GUI for HTML.
 
-With the rise of Single Page Applications (SPAs), rendering responsibilities shifted to the browser. SPAs retrieve raw data—often via OData in SAP systems—and dynamically build UIs using JavaScript frameworks such as React, Angular, or Vue. SAP released UI5 in 2010 as client-side SPA JavaScript framweork.
+With the rise of Single-Page Applications (SPAs), rendering moved to the browser. SPAs fetch raw data—often via OData in SAP systems—and build UI dynamically using JavaScript frameworks like React, Angular, or Vue. SAP introduced UI5 in 2010 as a client-side SPA framework.
 
-However, SPAs brought along new complexities:
-- API layers and data contracts
-- Separate frontend-backend development workflows
-- Complex build and deployment pipelines
+However, SPAs brought new challenges, including complex API layers, separate frontend and backend development teams, and elaborate build and deployment pipelines.
 
 As a counter-approach, HTML Over-the-Wire reestablishes server-driven UI updates:
 - Servers send UI fragments, not full pages