docs: improve clarity and fix inconsistencies across all sections

Sweep of the whole documentation for understandability, fixing
contradictions, stale references, and unclear wording:

- get_started: resolve 7.02/7.50 release contradiction, explain the
  extensibility tiers, unify "startup page" naming, explain the NS
  operator and the empty edit-button column in the full example
- cookbook: fix wrong method/event names (bind_edit, download_b),
  correct the OData metadata-binding example (entity type name and
  sap:label value), align the soft-lock example table name, repair
  numbered-heading anchors, explain nav_app_leave's two modes and the
  $event prefix exception, remove a stray demo button, fix the EML
  double backslash
- configuration: update the outdated default CSP, clarify SAPUI5 vs
  the OpenUI5 bootstrap default, use get_form_field for the app_start
  URL parameter, neutral handler class name, clearer launchpad and
  transport guidance
- advanced/technical: fix broken clone path and name the three config
  files, align dispatcher order in agent.md with the canonical
  template, promote H5 headings in how_it_all_works so the outline
  works, consistent "Over-the-Wire" spelling and backend-system
  terminology, complete truncated code snippets

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EC2cWJafPETwcMbh3NCsgH

Author: claude

docs/advanced/addons.md

@@ -5,7 +5,7 @@ outline: [2, 4]
 
 abap2UI5 focuses on core capabilities — rendering views, handling events, and exchanging data. This keeps the framework lean and easy to maintain. The real strength lies in the ecosystem: **ready-to-use add-ons and community projects** that extend abap2UI5 for specific needs.
 
-#### Add-ons
+#### Available Add-ons
 
 Browse the [abap2UI5-addons](https://github.com/abap2UI5-addons) organization to find what you need. Features include:
 - Layout variant handling, similar to classic SAP GUI selection screens or ALV reports

docs/advanced/agent.md

@@ -54,10 +54,10 @@ ENDCLASS.
 ```abap
 IF client->check_on_init( ).            " first call
   " load data + render view
-ELSEIF client->check_on_event( `POST` ). " user fired event 'POST'
-  " handle it
 ELSEIF client->check_on_navigated( ).   " returned from sub-app / popup
   " refresh state
+ELSEIF client->check_on_event( `POST` ). " user fired event 'POST'
+  " handle it
 ENDIF.
 ```
 
@@ -101,8 +101,8 @@ Translate any UI5 XML example from the [UI5 SDK](https://sapui5.hana.ondemand.co
 | UI5 XML | ABAP with `z2ui5_cl_util_xml` |
 |---|---|
 | `<Button text="Send" />` | `->__( n = `Button` a = `text` v = `Send` )` |
-| `press="onPress"` | `v = client->_event( `BUTTON_POST` )` |
-| `value="{/name}"` | `v = client->_bind_edit( name )` |
+| `press="onPress"` | `a = `press` v = client->_event( `BUTTON_POST` )` |
+| `value="{/name}"` | `a = `value` v = client->_bind_edit( name )` |
 | `<FeedInput><actions>…</actions></FeedInput>` | `->_( `FeedInput` )->_( `actions` )->__( … )` |
 
 Builder methods:

docs/advanced/builds.md

@@ -3,12 +3,12 @@ outline: [2, 4]
 ---
 # Builder
 
-For heavy abap2UI5 use, consider building your own version by defining a custom namespace and including the add-ons you need:
+If you run abap2UI5 in production or across several systems, consider building your own version — a release under a custom namespace that includes exactly the add-ons and frontend components you need:
 - Use abap2UI5 in the `z2ui5` namespace for improvements and pull requests, and keep a separate namespace for your production version.
 - Install multiple instances of abap2UI5 and upgrade each one at its own pace.
 - Build a custom abap2UI5 release with frontend components and add-ons matched to your needs.
 
-#### Builder
+#### The Builder Tool
 Make your own abap2UI5 build with the [builder](https://github.com/abap2UI5/builder).
 
 <img width="700" alt="abap2UI5 builder interface for generating custom namespaced builds" src="https://github.com/user-attachments/assets/7c7f55d4-6667-4036-bc71-4cd7472f2ae9" />

docs/advanced/extensibility/custom_control.md

@@ -9,7 +9,7 @@ First, set up your VS Code environment with the abap2UI5 frontend artifacts, fol
 
 #### Frontend
 
-Write the JS code for your new custom control. Copy an existing control from [App.controller.js](https://github.com/abap2UI5/abap2UI5/blob/main/app/webapp/controller/App.controller.js) and adapt it.
+Write the JavaScript for your new custom control. Each custom control lives in its own file under [app/webapp/cc/](https://github.com/abap2UI5/abap2UI5/tree/main/app/webapp/cc) — copy an existing one (e.g. `Timer.js`) and adapt it to your needs.
 
 #### Backend
 Extend the custom control view class by adding a method and defining the new control's properties:

docs/advanced/extensibility/frontend.md

@@ -9,15 +9,14 @@ The abap2UI5 frontend artifacts live in the `app` folder. To adjust them:
 Open VS Code (or your editor of choice), then run in the terminal:
 ```sh
 git clone https://github.com/abap2UI5/abap2UI5
-cd app
+cd abap2UI5/app
 ```
-Next replace `<<system>>` and let all three files point to your ABAP backend system:
+Next replace `<<system>>` in the three config files — `ui5.yaml`, `ui5-local.yaml` and `ui5-mock.yaml` — so they all point to your ABAP backend system:
 
 <img width="400" alt="Frontend config files where the backend system URL must be replaced" src="https://github.com/user-attachments/assets/155c9a3f-8a0a-494b-8fc4-a4bba2bf0e90">
 
 #### Build & Test
-Set the backend system in the YAML files.<br>
-Replace `/sap/bc/z2ui5` with your endpoint in the manifest, then run:
+If your HTTP service uses a different path, also replace `/sap/bc/z2ui5` with your endpoint in the manifest. Then run:
 ```sh
 npm i
 npm run start-noflp

docs/advanced/fiori.md

@@ -42,7 +42,7 @@ sap.ui.core.Component.create({
 				oVBox.addItem(oCompContainer);
 
 				//Overwrite default height of object page section
-				var oSection = that.getView().byId("[This is the ID of your object page section::Section]");
+				var oSection = that.getView().byId("<your-object-page-section-id>"); // replace with the ID of your object page section
 				oSection.addStyleClass("customSectionHeight");
 
 			});
@@ -66,15 +66,21 @@ sap.ui.core.Component.create({
 
 5. Create abap2UI5 app class
 
-On the ABAP side, the app receives the Fiori startup parameters (like the app class name and any custom key-value pairs) via `client->get( )-t_comp_params`. The `check_initialized` flag ensures the parameters are read only once, on the first roundtrip. Setting `backgrounddesign = 'List'` gives the page a white background matching the Fiori object page:
+On the ABAP side, the app receives the Fiori startup parameters (like the app class name and any custom key-value pairs) via `client->get( )-t_comp_params`. The `check_initialized` flag — a public `abap_bool` attribute of the app class — ensures the parameters are read only once, on the first roundtrip. Setting `backgrounddesign = 'List'` gives the page a white background matching the Fiori object page:
 ```abap
+  " class definition:
+  " PUBLIC SECTION.
+  "   INTERFACES z2ui5_if_app.
+  "   DATA check_initialized TYPE abap_bool.
+
   METHOD z2ui5_if_app~main.
 
     IF check_initialized = abap_false.
       check_initialized = abap_true.
 
 * ---------- Get startup parameters ---------------------------------------------------------------
       DATA(lt_startup_params) = client->get( )-t_comp_params.
+      " ... evaluate the startup parameters here
 
     ENDIF.
 

docs/advanced/http.md

@@ -18,12 +18,12 @@ The system that calls the app (the frontend system) ships with the UI5 library a
 
 #### Installation
 
-_Prerequisite: Set up an SM59 HTTP destination pointing to the source system. Install abap2UI5 on both systems._
+_Prerequisite: Set up an SM59 HTTP destination pointing to the backend system (the system that runs the apps). Install abap2UI5 on both systems._
 
 Steps:
 1. Install the [abap2UI5 HTTP Connector](https://github.com/abap2UI5-addons/http-connector) via abapGit on both systems
-2. In the HTTP handler, configure the destination to point to your source system
-3. In your browser, call the endpoint of the HTTP Connector
+2. In the HTTP handler, configure the destination to point to the backend system
+3. In your browser, call the HTTP Connector's endpoint on the frontend system (the ICF service installed with the connector — analogous to `.../sap/bc/2ui5_rfc` for the RFC Connector)
 
 #### Further Information
 For the latest details, source code, and updates, see the [HTTP Connector repository on GitHub](https://github.com/abap2UI5-addons/http-connector).

docs/advanced/local.md

@@ -3,6 +3,6 @@ outline: [2, 4]
 ---
 # Local
 
-abap2UI5-local is a special build that bundles all artifacts into a single HTTP handler. Create one extra database table, and you can run abap2UI5 independently of any other installation on the system.
+abap2UI5-local is a special build that bundles all framework classes into a single HTTP handler class. Besides that, you only need to create one additional database table. This gives you a self-contained copy of abap2UI5 that runs independently of any other abap2UI5 installation on the same system.
 
 For full details, see the repository: [abap2UI5-local](https://github.com/abap2UI5/abap2UI5-local)

docs/advanced/rfc.md

@@ -19,11 +19,11 @@ The system that calls the app (the frontend system) ships with the UI5 library a
 
 #### Installation
 
-_Prerequisite: Set up an SM59 destination to call the source system over RFC. Install abap2UI5 on both systems._
+_Prerequisite: Set up an SM59 destination to call the backend system (the system that runs the apps) over RFC. Install abap2UI5 on both systems._
 
 Steps:
 1. Install the [abap2UI5 RFC Connector](https://github.com/abap2UI5-addons/rfc-connector) via abapGit on both systems
-2. In the HTTP handler, replace the destination `NONE` with your Source System Destination
+2. In the HTTP handler, replace the destination `NONE` with the RFC destination pointing to the backend system
 3. In your browser, call the endpoint `.../sap/bc/2ui5_rfc`
 
 #### UI5 Bootstrapping

docs/configuration/authorization.md

@@ -6,23 +6,23 @@ outline: [2, 4]
 abap2UI5 gives you flexibility in managing authorization. It has no built-in authorization mechanism, so you can build your own solution at either the service or the app level.
 
 ### Service-Level
-An easy way to manage access to different apps: add checks in the HTTP handler. This approach restricts access to individual apps based on the APP_START parameter, directly in the ICF service handler class.
+The easiest way to manage access to different apps is to add authorization checks in the HTTP handler. This approach restricts access to individual apps based on the `app_start` URL parameter, directly in the ICF service handler class.
 
 #### Example: Restricting Access Based on URL Parameters
-In this example, we use the ICF handler class to control which apps users can access, based on the APP_START parameter in the HTTP request. The `get_header_field( 'APP_START' )` method reads the URL query parameter that names the abap2UI5 app class to launch. If the user requests an unauthorized app, the handler refuses access.
+In this example, we use the ICF handler class to control which apps users can access. The `get_form_field( `app_start` )` call reads the `app_start` URL parameter that names the abap2UI5 app class to launch (e.g. `...?app_start=my_app`). If the user requests an unauthorized app, the handler refuses access.
 ```abap
-CLASS z2ui5_cl_launchpad_handler DEFINITION PUBLIC.
+CLASS z2ui5_cl_my_http_handler DEFINITION PUBLIC.
 
   PUBLIC SECTION.
     INTERFACES if_http_extension.
 
 ENDCLASS.
 
-CLASS z2ui5_cl_launchpad_handler IMPLEMENTATION.
+CLASS z2ui5_cl_my_http_handler IMPLEMENTATION.
 
   METHOD if_http_extension~handle_request.
     " Read the app name from the request
-    DATA(lv_app) = server->request->get_header_field( `APP_START` ).
+    DATA(lv_app) = to_upper( server->request->get_form_field( `app_start` ) ).
 
     " Restrict access to a specific app
     IF lv_app <> `MY_APP`.
@@ -38,18 +38,18 @@ ENDCLASS.
 #### Example: Authorization Objects in Service Handlers
 You can also pair this with SAP authorization objects. The example below uses a custom authorization object `Z_APP_AUTH` with an `APP` field — define the object in transaction `SU21` and assign it to the matching roles on your system:
 ```abap
-CLASS z2ui5_cl_launchpad_handler DEFINITION PUBLIC.
+CLASS z2ui5_cl_my_http_handler DEFINITION PUBLIC.
 
   PUBLIC SECTION.
     INTERFACES if_http_extension.
 
 ENDCLASS.
 
-CLASS z2ui5_cl_launchpad_handler IMPLEMENTATION.
+CLASS z2ui5_cl_my_http_handler IMPLEMENTATION.
 
   METHOD if_http_extension~handle_request.
     " Read the app name from the request
-    DATA(lv_app) = server->request->get_header_field( `APP_START` ).
+    DATA(lv_app) = to_upper( server->request->get_form_field( `app_start` ) ).
 
     " Run an authorization check
     AUTHORITY-CHECK OBJECT `Z_APP_AUTH`