Fix remaining METHOD indentation issues across documentation

- Fixed 20 METHOD declarations to have 2 spaces indentation
- Updated code snippets in 8 documentation files
- Also fixed code group label capitalization: LCL_HELP→lcl_help
- Ensures consistent ABAP code formatting throughout documentation

Files updated:
- docs/development/events.md (3 methods)
- docs/development/messages.md (9 methods)
- docs/development/model/odata.md (1 method)
- docs/development/specific/barcodes.md (1 method)
- docs/development/specific/cds.md (1 method)
- docs/development/specific/files.md (1 method)
- docs/development/specific/xlsx.md (1 method)
- docs/development/translation.md (3 methods + label fix)

Author: claude

docs/development/events.md

@@ -12,8 +12,8 @@ You can trigger backend processing when an event occurs using the `client->_even
 As an example, we will use the `press` property of a button. To trigger events in the backend, assign the result of `client->_event(`MY_EVENT_NAME`)` to the relevant UI5 control property. Once triggered, the backend can retrieve the event details with `client->get( )-event`.
 
 ```abap
-METHOD z2ui5_if_app~main.
- 
+  METHOD z2ui5_if_app~main.
+
     client->view_display( z2ui5_cl_xml_view=>factory(
         )->button(
             text  = `post`
@@ -32,8 +32,8 @@ If the backend needs additional information about the specific event, use parame
 #### Source
 Send properties of the event source control to the backend:
 ```abap
-METHOD z2ui5_if_app~main.
- 
+  METHOD z2ui5_if_app~main.
+
     client->view_display( z2ui5_cl_xml_view=>factory(
         )->button( text = `post` press = client->_event( 
             val = `BUTTON_POST` 
@@ -51,8 +51,8 @@ ENDMETHOD.
 #### Parameters
 Retrieve parameters of the event:
 ```abap
-METHOD z2ui5_if_app~main.
- 
+  METHOD z2ui5_if_app~main.
+
     client->view_display( z2ui5_cl_xml_view=>factory(
         )->button( text = `post` id = `button_id` press = client->_event( 
             val = `BUTTON_POST` 
@@ -71,8 +71,8 @@ ENDMETHOD.
 #### Event
 Retrieve specific properties of the event:
 ```abap
-METHOD z2ui5_if_app~main.
- 
+  METHOD z2ui5_if_app~main.
+
     client->view_display( z2ui5_cl_xml_view=>factory(
         )->button( text = `post` press = client->_event( 
             val = `BUTTON_POST` 
@@ -102,8 +102,8 @@ CLASS z2ui5_cl_app_hello_world DEFINITION PUBLIC CREATE PUBLIC.
 
 ENDCLASS.
 
-METHOD z2ui5_if_app~main.
- 
+  METHOD z2ui5_if_app~main.
+
     client->view_display( z2ui5_cl_xml_view=>factory(
          )->input( client->_bind_edit( name )
         )->button( text = `post` press = client->_event( 
@@ -144,8 +144,8 @@ If you don't want to process the event in the backend, you can also directly tri
 ```
 For example, to open a new tab with the corresponding event:
 ```abap
-METHOD z2ui5_if_app~main.
- 
+  METHOD z2ui5_if_app~main.
+
     client->view_display( z2ui5_cl_xml_view=>factory(
         )->button(
             text = `post`
@@ -160,7 +160,7 @@ ENDMETHOD.
 ### Follow Up Action
 Sometimes, you might want to first call a backend function and then immediately perform an action in the frontend. This is possible with the follow-up action event:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     client->follow_up_action( client->_event_client( 
         val   = client->cs_event-open_new_tab 

docs/development/messages.md

@@ -11,7 +11,7 @@ Displaying messages and errors is an everyday requirement for ABAP developers. T
 For short-duration messages, such as success notifications, you can use the message toast:
 
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   client->message_toast_display( `this is a message` ).
 
@@ -23,7 +23,7 @@ ENDMETHOD.
 Want the user to acknowledge the message? You can display a message box that requires manual closure:
 
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   client->message_box_display( `this is a message` ).
 
@@ -33,7 +33,7 @@ ENDMETHOD.
 For error messages, simply change the type:
 
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   client->message_box_display(
     text = `This is an error message`
@@ -46,16 +46,16 @@ ENDMETHOD.
 You can directly pass common message structures, objects, and variables to the functions:
 ###### SY
 ```abap
-METHOD z2ui5_if_app~main.
-  
+  METHOD z2ui5_if_app~main.
+
   MESSAGE ID `NET` TYPE `I` NUMBER `001` INTO DATA(lv_dummy).
   client->message_box_display( sy ).
 
 ENDMETHOD.
 ```
 ###### BAPIRET
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   DATA lt_bapiret TYPE STANDARD TABLE OF bapiret2.
   CALL FUNCTION `BAPI_USER_GET_DETAIL`
@@ -71,7 +71,7 @@ ENDMETHOD.
 ```
 ###### CX_ROOT
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   TRY.
     DATA(lv_val) = 1 / 0.
@@ -83,10 +83,10 @@ ENDMETHOD.
 ```
 Other imports are supported as well. Just import your message structure, and the message box will display it.
 
-#### Popup Multi Message 
+#### Popup Multi Message
 The message box provides basic output. For a more detailed output, use the popup `z2ui5_cl_pop_messages`:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   DATA(lt_msg) = VALUE bapirettab(
     ( type = `E` id = `MSG1` number = `001` message = `An empty Report field causes an empty XML Message to be sent` )
@@ -99,7 +99,7 @@ ENDMETHOD.
 #### Popup Error
 To show a detailed view of your exception, use the following code:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   TRY.
     DATA(lv_val) = 1 / 0.
@@ -113,15 +113,15 @@ ENDMETHOD.
 #### Uncaught Errors
 What happens if errors are uncaught? In this case, the default HTTP handler exception output is used. The processing is interrupted, and the user will need to refresh the browser. Use this only for unexpected behavior:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     ASSERT 1 = `This is an error message!`.
 
 ENDMETHOD.
 ```
 Alternatively, achieve the same behavior with an uncaught exception:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     RAISE EXCEPTION NEW cx_sy_itab_line_not_found( ).
 

docs/development/model/odata.md

@@ -36,10 +36,10 @@ tab->items( )->column_list_item( )->cells(
 By using the growing property we can make use of the feature that not all data is loaded at once, leveraging performance.
 
 #### Full Example
-Here’s the complete source code:
+Here's the complete source code:
 ```abap
-METHOD z2ui5_if_app~main.
-  
+  METHOD z2ui5_if_app~main.
+
     DATA(tab) = z2ui5_cl_xml_view=>factory( )->page( )->table(
         items   = `{FLIGHT>/Airport}`
         growing = abap_true ).

docs/development/specific/barcodes.md

@@ -16,7 +16,7 @@ This section provides all the information you need to get started easily.
 Since UI5 version 1.102, the `sap.ndc.BarcodeScannerButton` control is part of the UI5 library, making barcode scanning simple and straightforward. You can use the barcode scanner control like any other UI5 control with abap2UI5. Below is an example demonstrating basic functionality. You can customize the handling after the scanning event is triggered:
 
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     DATA(lo_view) = z2ui5_cl_xml_view=>factory(
         )->page(

docs/development/specific/cds.md

@@ -87,7 +87,7 @@ ENDCLASS.
 The following example demonstrates how to create a sales order using `MODIFY` in an abap2UI5 application:
 
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     MODIFY ENTITIES OF i_salesordertp
            ENTITY salesorder

docs/development/specific/files.md

@@ -42,7 +42,7 @@ ENDCLASS.
 #### Download
 See also `Z2UI5_CL_DEMO_APP_186`
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     client->view_display( z2ui5_cl_xml_view=>factory(
         )->page(

docs/development/specific/xlsx.md

@@ -183,7 +183,7 @@ Instead of using the above XLSX API (which may change between releases), conside
 ::: code-group
 
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   client->view_display( z2ui5_cl_xml_view=>factory(
     )->page(

docs/development/translation.md

@@ -8,7 +8,7 @@ In UI5 apps, translations are typically managed through i18n files, with transla
 ### Text Element
 Messages can be translated using the ABAP text elements, making them available in different languages without changing the code:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   DATA(lv_msg_translated) = `this is a translatable message in english`(001).
   client->message_box_display( lv_msg_translated ).
@@ -19,7 +19,7 @@ ENDMETHOD.
 ### Messages
 Messages are translated using message classes, ensuring that translations are managed centrally and can be maintained easily in different languages:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   MESSAGE ID `NET` TYPE `I` NUMBER `001` INTO DATA(lv_msg_translated).
   client->message_box_display( lv_msg_translated ). 
@@ -33,15 +33,15 @@ You can also retrieve and display the short, medium, or long descriptions of dat
 ::: code-group
 
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   DATA(ls_product_label) = lcl_help=>get_data_element_text( `PRODUCT` ).
   client->message_box_display( |{ ls_product_label-short }: 100 | ).
 
 ENDMETHOD.
 ```
 
-```abap [LCL_HELP]
+```abap [lcl_help]
 CLASS lcl_help DEFINITION
   CREATE PUBLIC.