Align page H1 titles with cookbook menu entries

Update the H1 of each cookbook page so it matches the sidebar
entry that links to it: Follow-up -> Action, Inner/Cross App
-> Navigation, Errors -> Exception, Built-In Popups ->
Built-In, Geolocation, Maps -> Geolocation, Timer,
Auto-Refresh -> Timer, Messages -> Message, Logging, BAL ->
Logging, Locks -> Lock, App State, Share, Bookmark -> App
State, Share, CL_DEMO_OUTPUT -> Demo Output, Smart Controls
-> Smart Control.

Author: claude

docs/advanced/experimental/smart_control.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Smart Controls
+# Smart Control
 
 Smart Controls are metadata-driven UI5 controls that build the UI automatically from OData annotations. abap2UI5 supports them on an experimental basis.
 

docs/cookbook/browser_interaction/timer.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Timer, Auto-Refresh
+# Timer
 
 abap2UI5 offers a custom control `z2ui5.Timer` that fires events after a set delay. This is handy for dashboards, status monitors, or any case that needs periodic data updates without user interaction.
 

docs/cookbook/device_capabilities/geolocation.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Geolocation, Maps
+# Geolocation
 
 abap2UI5 offers a custom control for reading geolocation data from the user's device — longitude, latitude, altitude, and speed. This is handy for logistics apps, field service tools, or any scenario where location matters.
 

docs/cookbook/event_navigation/action.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Follow-up
+# Action
 
 Sometimes you need to call a backend function and then act on the frontend right afterward. The follow-up action event covers this:
 ```abap

docs/cookbook/event_navigation/exception.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Errors
+# Exception
 
 Beyond plain messages, abap2UI5 ships dedicated popups and fallbacks for handling exceptions and unexpected failures.
 

docs/cookbook/event_navigation/navigation.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Inner/Cross App
+# Navigation
 
 In abap2UI5, each app is a single ABAP class. You can pack all logic into one class, but keeping classes at a reasonable size is better practice. Splitting functionality into multiple interacting classes lets you build reusable apps and popups that work in different contexts.
 

docs/cookbook/expert_more/app_state_share.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# App State, Share, Bookmark
+# App State, Share
 
 abap2UI5 saves the current app state so you can return to it later — like how standard UI5 apps manage state. This opens up several useful options, like sharing and bookmarking the current state of your app.
 

docs/cookbook/expert_more/demo_output.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# CL_DEMO_OUTPUT
+# Demo Output
 
 Familiar with `CL_DEMO_OUTPUT` from classic ABAP? You can show its HTML output inside an abap2UI5 app too. This is handy for quick data visualization or when porting existing demos.
 

docs/cookbook/expert_more/lock.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Locks
+# Lock
 
 In classic SAP GUI, a transaction like `VA02` calls `ENQUEUE_EVVBAK` and the lock lives as long as the dialog session. Web apps are different: each roundtrip is a fresh ABAP session by default, so a lock set in one roundtrip is gone by the next. Locking in abap2UI5 means picking a deliberate strategy for two questions:
 

docs/cookbook/popup_popover/built_in.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Built-In Popups
+# Built-In
 
 A few pre-built popup classes cover the most common cases: