Rename three sidebar entries for consistency

- Expression Binding -> Expressions
- Translation, i18n -> Translation
- follow_up_action -> Follow-up Action

H1 titles updated to match. Body references to the underlying UI5
concept and the obsolete method name are kept verbatim.

Author: claude

docs/.vitepress/config.mjs

@@ -141,7 +141,7 @@ export default defineConfig({
                 text: "Binding",
                 link: "/cookbook/model/binding",
                 items: [
-                  { text: "Expression Binding", link: "/cookbook/model/expression_binding" },
+                  { text: "Expressions", link: "/cookbook/model/expression_binding" },
                   { text: "Formatter", link: "/cookbook/model/formatter" },
                 ],
               },
@@ -187,7 +187,7 @@ export default defineConfig({
             items: [
               { text: "Message", link: "/cookbook/translation_messages/message" },
               { text: "Logging", link: "/cookbook/translation_messages/logging" },
-              { text: "Translation, i18n", link: "/cookbook/translation_messages/translation_i18n" },
+              { text: "Translation", link: "/cookbook/translation_messages/translation_i18n" },
             ],
           },
           {
@@ -284,7 +284,7 @@ export default defineConfig({
                 items: [
                   { text: "Custom Controls", link: "/cookbook/expert_more/custom_controls" },
                   { text: "Custom JS", link: "/cookbook/expert_more/custom_js" },
-                  { text: "follow_up_action", link: "/cookbook/expert_more/follow_up_action" },
+                  { text: "Follow-up Action", link: "/cookbook/expert_more/follow_up_action" },
                 ],
               },
             ],

docs/cookbook/expert_more/follow_up_action.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# follow_up_action (Obsolete)
+# Follow-up Action (Obsolete)
 
 ::: warning Do Not Use Anymore
 `client->follow_up_action( )` is obsolete. Use `client->action( )` instead. It works the same way, but **does not allow sending arbitrary JavaScript to the frontend** — which is exactly why `follow_up_action` was deprecated. See [Custom JS](/cookbook/expert_more/custom_js) for the full reasoning behind removing direct JS execution.

docs/cookbook/model/expression_binding.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Expression Binding
+# Expressions
 
 Expression Binding lets you compute values directly in XML views with JavaScript-like expressions. This is especially handy in abap2UI5, since it cuts server roundtrips by moving calculations, logical conditions, and string operations to the frontend.
 

docs/cookbook/translation_messages/translation_i18n.md

@@ -1,7 +1,7 @@
 ---
 outline: [2, 4]
 ---
-# Translation, i18n
+# Translation
 
 Standard UI5 apps handle translations with i18n files stored as frontend artifacts. Since abap2UI5 apps live entirely on the ABAP backend, use ABAP's built-in translation tools instead — text elements, message classes, or data element descriptions.