Fix METHOD indentation and keyword capitalization in ABAP code snippets

- Fixed METHOD declarations to have 2 spaces indentation (inside CLASS blocks)
- Fixed 11 METHOD statements across 5 documentation files
- Fixed capitalization: data→DATA, Z2UI5_→z2ui5_
- Ensures consistent indentation standards throughout documentation

Files updated:
- docs/development/view.md
- docs/advanced/extensibility/custom_js.md
- docs/advanced/fiori.md
- docs/development/specific/logging.md (4 methods)
- docs/development/navigation/navigation.md (4 methods)
- docs/development/popups.md (4 methods, from previous work)
- docs/development/specific/xlsx.md (keyword capitalization)

Author: claude

docs/advanced/extensibility/custom_js.md

@@ -10,7 +10,7 @@ The idea is to send the custom JavaScript function along with the view to the fr
 Below is a working example that you can use as a starting point:
 
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   IF client->check_on_init( ).
       DATA(view) = z2ui5_cl_xml_view=>factory( ).

docs/advanced/fiori.md

@@ -65,8 +65,8 @@ sap.ui.core.Component.create({
 ```
 
 5. Create ABAP2U5 app class
-```abap  
-METHOD z2ui5_if_app~main.
+```abap
+  METHOD z2ui5_if_app~main.
 
     IF check_initialized = abap_false.
       check_initialized = abap_true.

docs/development/navigation/navigation.md

@@ -10,7 +10,7 @@ In abap2UI5, each application is represented by a single ABAP class. While you c
 #### Backend
 To call an ABAP class, use the following code:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     DATA(lo_app) = NEW z2ui5_cl_new_app( ).
     client->nav_app_call( lo_app ).
@@ -19,15 +19,15 @@ ENDMETHOD.
 ```
 The framework maintains a call stack. In the newly called class, you can return to the previous application using:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     client->nav_app_leave( ).
 
 ENDMETHOD.
 ```
 If you need to access data from the previous application, use casting as follows:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     IF client->check_on_navigated( ).
         DATA(lo_called_app) = CAST z2ui5_cl_new_app( client->get_app_prev( ) ).
@@ -38,7 +38,7 @@ ENDMETHOD.
 ```
 To navigate to an application without adding it to the call stack, use:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     DATA(lo_app) = NEW z2ui5_cl_new_app( ).
     client->nav_app_leave( lo_app ).

docs/development/popups.md

@@ -11,20 +11,20 @@ UI5 offers functionality for displaying popups and popovers that overlay only sp
 
 To display a popup, use the method `client->popup_display` instead of `client->view_display`:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     DATA(lo_popup) = z2ui5_cl_xml_view=>factory_popup(
         )->dialog( `Popup - Info`
             )->text( `this is an information shown in a popup` ).
     client->popup_display( lo_popup->stringify( ) ).
 
-ENDMETHOD.
+  ENDMETHOD.
 ```
 
 #### Flow Logic
 A common flow for using popups typically involves displaying a normal view, then showing a popup, and finally closing it. Here’s how to structure this:
 ```abap
-METHOD Z2UI5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     IF client->check_on_init( ).
         DATA(lo_view) = z2ui5_cl_xml_view=>factory(
@@ -39,7 +39,7 @@ METHOD Z2UI5_if_app~main.
     CASE client->get( )-event.
 
       WHEN `POPUP_OPEN`.
-        DATA(lo_popup) = Z2UI5_cl_xml_view=>factory_popup(
+        DATA(lo_popup) = z2ui5_cl_xml_view=>factory_popup(
             )->dialog( `Popup`
                 )->text( `this is a text in a popup`
                 )->button(
@@ -49,39 +49,39 @@ METHOD Z2UI5_if_app~main.
 
       WHEN `POPUP_CLOSE`.
         client->popup_destroy( ).
-        
+
     ENDCASE.
 
-ENDMETHOD.
+  ENDMETHOD.
 ```
 
 #### Separated App
 For better source code structure, you can encapsulate popups in separate classes and call them through [navigation](/development/navigation/navigation).
 
 Check out the popup to confirm, for example:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
-  IF client->check_on_init( ).
-   client->nav_app_call( z2ui5_cl_pop_to_confirm=>factory( `Can you confirm this?` ) ).
- ENDIF.
+    IF client->check_on_init( ).
+      client->nav_app_call( z2ui5_cl_pop_to_confirm=>factory( `Can you confirm this?` ) ).
+    ENDIF.
 
-  CASE client->get( )-event.
-    WHEN z2ui5_cl_pop_to_confirm=>cs_event-confirmed.
-      client->message_box_display( `the result is confirmed` ).
-    WHEN z2ui5_cl_pop_to_confirm=>cs_event-canceled.
-      client->message_box_display( `the result is rejected` ).
-  ENDCASE.
+    CASE client->get( )-event.
+      WHEN z2ui5_cl_pop_to_confirm=>cs_event-confirmed.
+        client->message_box_display( `the result is confirmed` ).
+      WHEN z2ui5_cl_pop_to_confirm=>cs_event-canceled.
+        client->message_box_display( `the result is rejected` ).
+    ENDCASE.
 
-ENDMETHOD.
+  ENDMETHOD.
 ```
 
 If you need to manage a stack of multiple popups, remember that abap2UI5 displays only one popup at a time on the frontend. However, you can maintain a popup stack in your backend logic and re-display the previous popup as needed. Check out `Z2UI5_CL_DEMO_APP_161`.
 
 ### Popover
 To display a popover, use the method `client->popover_display` and specify the ID of the control where you want the popover to appear:
  ```abap
-METHOD Z2UI5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     IF client->check_on_init( ).
       DATA(view) = z2ui5_cl_xml_view=>factory(
@@ -98,7 +98,7 @@ METHOD Z2UI5_if_app~main.
     CASE client->get( )-event.
 
       WHEN `POPOVER_OPEN`.
-        DATA(popover) = Z2UI5_cl_xml_view=>factory_popup(
+        DATA(popover) = z2ui5_cl_xml_view=>factory_popup(
             )->popover( placement = `Left`
                 )->text( `this is a popover`
                 )->button(
@@ -113,7 +113,7 @@ METHOD Z2UI5_if_app~main.
         client->popover_destroy( ).
     ENDCASE.
 
-ENDMETHOD.
+  ENDMETHOD.
  ```
 
 ### Built-in Popups

docs/development/specific/logging.md

@@ -8,7 +8,7 @@ Logging is essential for developing end-user business processes. In ABAP systems
 ##### BAL Variables
 In ABAP classic, you can use the classic BAL function modules and display the BAL table with the popup `z2ui5_cl_pop_messages`:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   DATA(lt_bal) = VALUE bal_t_msgr(
     ( msgid = `Z001` msgno = `001` msgty = `S` time_stmp = `21354` msgnumber = `01` )
@@ -22,7 +22,7 @@ ENDMETHOD.
 ##### ABAP Cloud
 In ABAP Cloud, you can directly pass the logging object into the popup:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   DATA(lo_log) = cl_bali_log=>create( ).
   DATA(lo_msg) = cl_bali_message_setter=>create(
@@ -48,7 +48,7 @@ ENDMETHOD.
 ##### abap-logger
 You also have the option to use the fantastic open-source project [**abap-logger**](https://github.com/ABAP-Logger/ABAP-Logger). This tool simplifies working with BAL logs and integrates seamlessly with abap2UI5. Here’s an example:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   DATA(log) = zcl_logger_factory=>create_log( desc = `ABAP Logger` ).
   log->e( `This is an error...` ).
@@ -63,7 +63,7 @@ ENDMETHOD.
 Compared to message classes, BAL logs include more detailed information, such as timestamps. Use the specific BAL log popup to display this information. All the examples above can be used with the `z2ui5_cl_pop_bal` popup for a more detailed output, here’s an example for the abap-logger:
 
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
   DATA(lo_log) = zcl_logger_factory=>create_log( desc = `ABAP Logger` ).
   log->e( `This is an error...` ).

docs/development/specific/xlsx.md

@@ -35,7 +35,7 @@ CLASS z2ui5_cl_sample_upload IMPLEMENTATION.
 
     IF client->get( )-event = `UPLOAD`.
 
-        data(lr_itab) = lcl_help=>itab_get_by_xlsx( mv_value ).
+        DATA(lr_itab) = lcl_help=>itab_get_by_xlsx( mv_value ).
         "further process with itab...
         client->message_box_display( `xlsx uploaded` ).
     ENDIF.

docs/development/view.md

@@ -4,7 +4,7 @@ outline: [2, 4]
 # View
 In abap2UI5, the output is generated by importing a UI5 XML View. Here’s a basic example:
 ```abap
-METHOD z2ui5_if_app~main.
+  METHOD z2ui5_if_app~main.
 
     client->view_display( 
         |<mvc:View xmlns="sap.m" xmlns:core="sap.ui.core" xmlns:mvc="sap.ui.core.mvc" | &