diff --git a/docs/cookbook/event_navigation/life_cycle.md b/docs/cookbook/event_navigation/life_cycle.md
index 28469f8f..e01a8695 100644
--- a/docs/cookbook/event_navigation/life_cycle.md
+++ b/docs/cookbook/event_navigation/life_cycle.md
@@ -9,6 +9,10 @@ description: The abap2UI5 app life cycle - every request enters main( ), and che
 
 Every request enters the `main` method. One `IF` / `ELSEIF` chain dispatches between initialization, navigation returns, and user events using `` client->check_on_init( ) ``, `` client->check_on_event( `EVENT_NAME` ) ``, and `` client->check_on_navigated( ) ``. Each branch either does the work inline (tiny apps) or calls a named handler method (typical apps) — the **structure is always the same**.
 
+![One roundtrip in five steps: the app draft is loaded, the user's changes are applied, main( ) runs, the response is built and the app draft is saved under a new id](/get_started/roundtrip.svg)
+
+The picture shows one roundtrip. Your code is step 3: `main` runs once per click, on an instance the framework has just restored.
+
 ```abap
 CLASS zcl_sample_life_cycle DEFINITION PUBLIC.
 
diff --git a/docs/cookbook/model/binding.md b/docs/cookbook/model/binding.md
index 630f5e84..43ad2df5 100644
--- a/docs/cookbook/model/binding.md
+++ b/docs/cookbook/model/binding.md
@@ -68,6 +68,9 @@ framework has already synced the user's changes back to your ABAP attribute:
 
 ![The attribute is bound, appears as a path in the view and the model, the Input shows it, and what the user types travels back into the attribute before main( ) runs](/cookbook/model/bound-value.svg)
 
+The picture uses an attribute `quantity` as its example. The class below binds
+`name` the same way.
+
 ```abap
 CLASS zcl_app_hello_world DEFINITION PUBLIC.