Update hello_world.md

Author: oblomov-dev

docs/get_started/hello_world.md

@@ -3,25 +3,8 @@ outline: [2, 4]
 ---
 # Hello World
 
-abap2UI5 follows a thin-frontend model: the browser only renders UI5 views, while all logic, state, and data handling stay in ABAP on the server. Three ideas to keep in mind before writing code:
-
-- **One method, many calls.** The framework calls your app's `main` method on every roundtrip — on the initial start *and* after every user interaction (button press, input change, navigation).
-- **State lives in your class.** Public attributes of your app class hold data between roundtrips; abap2UI5 serializes and restores them for you, so you don't manage sessions manually.
-- **The `client` object is your only API.** Use it to display views, check which event fired, bind attributes to UI5 controls, and trigger navigation.
+Just copy the following class into your system:
 
-Every abap2UI5 app implements the `z2ui5_if_app` interface. It has a single method, `main`, with one parameter: `client` of type `z2ui5_if_client`:
-```abap
-INTERFACE z2ui5_if_app PUBLIC.
-  METHODS main
-    IMPORTING
-      client TYPE REF TO z2ui5_if_client.
-ENDINTERFACE.
-```
-The `client` object is your only entry point into the framework. Use it to show views, handle events, share data, and navigate between apps.
-
-→ *For a deeper look at the lifecycle and framework internals, see [How It All Works](/technical/how_it_all_works) and [Concept](/technical/concept).*
-
-### Basic Example
 Build a class:
 ```abap
 CLASS zcl_app_hello_world DEFINITION PUBLIC.
@@ -31,9 +14,7 @@ ENDCLASS.
 
 CLASS zcl_app_hello_world IMPLEMENTATION.
   METHOD z2ui5_if_app~main.
-
     client->message_box_display( `Hello World` ).
-
   ENDMETHOD.
 ENDCLASS.
 ```
@@ -43,6 +24,25 @@ Go back to the landing page in your browser and enter `ZCL_APP_HELLO_WORLD` to l
 While the HTTP handler has to distinguish between Standard ABAP and ABAP for Cloud, the apps themselves are independent. You're free to choose whether to build your apps with ABAP Cloud compatibility.
 :::
 
+### Idea
+abap2UI5 follows a thin-frontend model: the browser only renders UI5 views, while all logic, state, and data handling stay in ABAP on the server. Three ideas to keep in mind before writing code:
+
+- **One method, many calls.** The framework calls your app's `main` method on every roundtrip — on the initial start *and* after every user interaction (button press, input change, navigation).
+- **State lives in your class.** Public attributes of your app class hold data between roundtrips; abap2UI5 serializes and restores them for you, so you don't manage sessions manually.
+- **The `client` object is your only API.** Use it to display views, check which event fired, bind attributes to UI5 controls, and trigger navigation.
+
+Every abap2UI5 app implements the `z2ui5_if_app` interface. It has a single method, `main`, with one parameter: `client` of type `z2ui5_if_client`:
+```abap
+INTERFACE z2ui5_if_app PUBLIC.
+  METHODS main
+    IMPORTING
+      client TYPE REF TO z2ui5_if_client.
+ENDINTERFACE.
+```
+The `client` object is your only entry point into the framework. Use it to show views, handle events, share data, and navigate between apps.
+
+→ *For a deeper look at the lifecycle and framework internals, see [How It All Works](/technical/how_it_all_works) and [Concept](/technical/concept).*
+
 ### View Display
 Let's add a view to show some text:
 ```abap