fixes

Author: oblomov-dev

docs/development/general.md

@@ -1,6 +1,6 @@
 # General
 
-abap2UI5 offers great flexibility in developing your app. Most samples follow a process similar to the sequence shown below. Use it as a starting point, and feel free to create your own sequence or build a wrapper on top of abap2UI5. 
+abap2UI5 offers great flexibility in app development. Most sample applications follow a process similar to the sequence outlined below. You can use it as a starting point, but feel free to create your own sequence or build a wrapper on top of abap2UI5 for more customized behavior:
 
 ```abap
 CLASS z2ui5_cl_app DEFINITION PUBLIC.
@@ -47,4 +47,4 @@ CLASS z2ui5_cl_app IMPLEMENTATION.
   ENDMETHOD.
 ENDCLASS.
 ````
-Refer to the specific sections of this development guide for more details on implementation.
+Refer to the specific sections of this development guide for more details on the implementation process.

docs/development/messages.md

@@ -4,11 +4,11 @@ outline: [2, 4]
 
 # Messages, Errors
 
-Outputting messages and errors is an everyday requirement for ABAP developers. Functions are provided for the most common situations.
+Displaying messages and errors is an everyday requirement for ABAP developers. The following functions handle the most common scenarios.
 
 #### Message Toast
 
-Messages that are displayed for a short period, such as success notifications, can be shown with:
+For short-duration messages, such as success notifications, you can use the message toast:
 
 ```abap
 METHOD z2ui5_if_app~main.
@@ -20,7 +20,7 @@ ENDMETHOD.
 
 #### Message Box
 
-If you want to ensure that the user acknowledges the message, you can display a message box that requires a manual close:
+If you want the user to acknowledge the message, you can display a message box that requires manual closure:
 
 ```abap
 METHOD z2ui5_if_app~main.
@@ -43,7 +43,7 @@ ENDMETHOD.
 ```
 
 #### SY, BAPIRET, CX_ROOT
-Common message structures, objects, and variables can be passed directly to the functions:
+You can directly pass common message structures, objects, and variables to the functions:
 ###### SY
 ```abap
 METHOD z2ui5_if_app~main.
@@ -81,10 +81,10 @@ METHOD z2ui5_if_app~main.
 
 ENDMETHOD. 
 ```
-Many other imports are supported. Just import your message structure, and the message box will display it.
+Other imports are supported as well. Simply import your message structure, and the message box will display it.
 
 #### Popup Multi Message 
-The message box provides basic output, if you want to generate a detailed output, use the popup `z2ui5_cl_pop_messages`:
+The message box provides basic output. For a more detailed output, use the popup `z2ui5_cl_pop_messages`:
 ```abap
 METHOD z2ui5_if_app~main.
 
@@ -97,7 +97,7 @@ METHOD z2ui5_if_app~main.
 ENDMETHOD.
 ```
 #### Popup Error
-To show a detailed view of your exception:
+To show a detailed view of your exception, use the following code:
 ```abap
 METHOD z2ui5_if_app~main.
 
@@ -110,7 +110,7 @@ METHOD z2ui5_if_app~main.
 ENDMETHOD.
 ```
 #### Popup Confirm
-If interaction is required, the `z2ui5_cl_pop_to_confirm` can be used:
+If interaction is required, you can use `z2ui5_cl_pop_to_confirm`:
 ```abap
 METHOD z2ui5_if_app~main.
 
@@ -128,15 +128,15 @@ METHOD z2ui5_if_app~main.
 ENDMETHOD.
 ```
 #### Uncatched 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 need to refresh the browser. So only use this for unexpected behaviour:
+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.
 
     ASSERT 1 = `This is an error message!`.
 
 ENDMETHOD.
 ```
-Or achieve the same behavior with an uncaught exception:
+Alternatively, achieve the same behavior with an uncaught exception:
 ```abap
 METHOD z2ui5_if_app~main.
 
@@ -145,5 +145,5 @@ METHOD z2ui5_if_app~main.
 ENDMETHOD.
 ```
 ::: tip **Improvements**
-All these message functions are continually improved. Feel free to open an issue if you encounter errors or incompatibilities, or submit a PR to extend the functionality.
+These message functions are continually being improved. Feel free to open an issue if you encounter errors or incompatibilities, or submit a PR to extend the functionality.
 :::

docs/development/model.md

@@ -3,11 +3,11 @@ outline: [2, 4]
 ---
 # Model
 
-There are three ways to exchange data with the frontend in abap2UI5.
+In abap2UI5, there are three ways to exchange data with the frontend.
 
 #### One-Way Binding
+Use one-way binding when you need to display data on the frontend without allowing changes. The `client->_bind` method sends data to the frontend and connects it to the view:
 
-When you need to display data on the frontend without allowing any changes, use one-way binding. The `client->_bind` method sends the data to the frontend and connects it to the view:
 ```abap
 CLASS z2ui5_cl_app_hello_world DEFINITION PUBLIC.
 
@@ -29,10 +29,10 @@ CLASS z2ui5_cl_app_hello_world IMPLEMENTATION.
   ENDMETHOD.
 ENDCLASS.
 ```
-This method also works for tables, trees, and other complex data structures. For more details, refer to the samples repository and explore the table or tree samples.
+This method works with tables, trees, and other complex data structures. For more details, refer to the samples repository and explore the table or tree samples.
 
 #### Two-Way Binding
-If the user should be able to modify data, enable two-way binding to update data in the ABAP backend. Use the `client->_bind_edit` method so that after an event, the framework will synchronize the data with your ABAP class.
+If the user should be able to modify data, enable two-way binding to update the data in the ABAP backend. Use the `client->_bind_edit` method so that, after an event, the framework will synchronize the data with your ABAP class:
 
 ```abap
 CLASS z2ui5_cl_app_hello_world DEFINITION PUBLIC.
@@ -64,7 +64,7 @@ ENDCLASS.
 ```
 
 #### Local Binding
-When you only have local access to data but want to bind it for display (e.g., for a value help or lookup), use local binding. The `client->_bind_local` method copies the data and sends it to the frontend without impacting backend logic:
+When you only have local access to data but still want to bind it for display (e.g., for value help or lookups), use local binding. The `client->_bind_local` method copies the data and sends it to the frontend:
 
 ```abap
 CLASS z2ui5_cl_app_hello_world DEFINITION PUBLIC.
@@ -88,8 +88,8 @@ CLASS z2ui5_cl_app_hello_world IMPLEMENTATION.
   ENDMETHOD.
 ENDCLASS.
 ```
-For an example of local binding in action, see the value help use case in `Z2UI5_CL_DEMO_APP_002`.
+For an example of local binding in action, refer to the value help use case in `Z2UI5_CL_DEMO_APP_002`.
 
 ::: tip **Data in Public Attributes**
-When using One-Way or Two-Way binding, remember to store your data in public attributes of your class, as the framework needs to access it from outside. This is similar to the PBO/PAI screen days, where data needed to be stored in global variables.
+When using One-Way or Two-Way binding, ensure your data is stored in the public attributes of your class. This allows the framework to access it from outside. This is similar to the PBO/PAI screen days, where data had to be stored in global variables.
 :::

docs/development/popups.md

@@ -23,8 +23,7 @@ ENDMETHOD.
 ```
 
 #### Flow Logic
-Typically, a common flow for using popups involves displaying a normal view, then showing a popup, and finally closing it. Here’s how this can be structured:
-
+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.
 
@@ -62,12 +61,10 @@ ENDMETHOD.
 ```
 
 #### Separated App
-For better source code structure, it's possible to encapsulate the popups in separate classes and call them through navigation.
+For better source code structure, it's possible to encapsulate popups in separate classes and call them through navigation.
 
 ### Popover
-
-Use the method client->popover_display and specify the ID of the control where you want to display the 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.
 
@@ -108,7 +105,6 @@ ENDMETHOD.
  ```
 
 ### Built-in Popups
-
 Several pre-built popup classes are available for specific scenarios:
 
 * z2ui5_cl_pop_error
@@ -126,4 +122,4 @@ Several pre-built popup classes are available for specific scenarios:
 * z2ui5_cl_pop_textedit
 * z2ui5_cl_pop_to_confirm
 * z2ui5_cl_pop_to_inform
-* z2ui5_cl_pop_to_select
+* z2ui5_cl_pop_to_select

docs/development/translation.md

@@ -6,7 +6,7 @@ outline: [2, 4]
 In UI5 apps, translations are typically managed through i18n files, with translation content stored in frontend artifacts. In abap2UI5, since all apps reside on the ABAP backend, we can leverage ABAP's built-in translation mechanisms, such as text elements or message classes.
 
 ### Text Element
-The message can be translated using the ABAP text element mechanism, making it available in different languages without changing the code:
+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.
 
@@ -17,7 +17,7 @@ ENDMETHOD.
 ```
 
 ### Messages
-Messages are translated using message classes, which ensures that translations are managed centrally and can be maintained easily in different languages:
+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.
 
@@ -28,7 +28,7 @@ ENDMETHOD.
 ```
 
 ### Data Element
-You can also retrieve and display the short, medium, or long descriptions of data elements (DD04T). Here’s how to access these text types programmatically:
+You can also retrieve and display the short, medium, or long descriptions of data elements (DD04T). Here's how to access these text types programmatically:
 
 ::: code-group
 

docs/development/troubleshooting.md

@@ -17,6 +17,4 @@ Here, you can inspect the XML View and check the Data Model bound to the view.
 
 ##### UI5 Inspector
 
-Another useful option is SAP’s default debugging tool, the [UI5 Inspector.](https://chromewebstore.google.com/detail/ui5-inspector/bebecogbafbighhaildooiibipcnbngo?hl=es)
-
-
+Another useful option is SAP’s default debugging tool, the [UI5 Inspector.](https://chromewebstore.google.com/detail/ui5-inspector/bebecogbafbighhaildooiibipcnbngo?hl=es)

docs/development/view.md

@@ -2,8 +2,7 @@
 outline: [2, 4]
 ---
 # View
-Output in abap2UI5 is generated by importing a UI5 XML View. Here’s a basic example:
-
+In abap2UI5, the output is generated by importing a UI5 XML View. Here’s a basic example:
 ```abap
 METHOD z2ui5_if_app~main.
 
@@ -19,7 +18,7 @@ METHOD z2ui5_if_app~main.
 
 ENDMETHOD.
 ```
-You can use any UI5 control available in the UI5 SDK. However, working with XML can be cumbersome. The current best practice is to use the class `Z2UI5_CL_XML_VIEW`:
+You can use any UI5 control available in the UI5 SDK. However, working with XML can become cumbersome. A more efficient approach is to use the `Z2UI5_CL_XML_VIEW` class. Here's an improved version of the code using this class:
 ```abap
   METHOD z2ui5_if_app~main.
 
@@ -32,6 +31,6 @@ You can use any UI5 control available in the UI5 SDK. However, working with XML
 
   ENDMETHOD.
 ```
-Check the API of the class `Z2UI5_CL_XML_VIEW` and use code completion to easily find the right controls and properties. Additionally, it’s recommended to explore the sample repository, where pre-written XML examples for most use cases are available for easy copy, paste, and adjustment to fit your needs. 
+Check the API of the `Z2UI5_CL_XML_VIEW` class and leverage code completion to easily find the correct controls and properties. Additionally, it’s recommended to explore the sample repository, which contains pre-written XML examples for most use cases. These examples are available for easy copy-pasting and can be adjusted to suit your specific needs.
 
-Currently, this setup is quite static; we’ll explore how to bind and exchange data in the next section.
+Currently, this setup is quite static. In the next section, we will explore how to bind and exchange data between the view and the app logic.