docs: post improvements

docs/blog/posts/0011-SAP-Fiori-custom-app-identification.md

@@ -21,14 +21,15 @@ SAP Fiori standard apps are easily identifiable by a unique App ID, which helps
 
 ## Reason 1: Finding and maintaining documentation
 
-Having a list of apps with IDs already serves as documentation. Although it takes time to specify the requirements and features of custom apps, maintaining an official list of the apps is a quick yet fundamental long-term step. Initially, the App IDs provide an understanding of the extent of custom solutions for the project. Additionally, unique App IDs can facilitate live documentation by linking the names of objects stored outside your app directory. For instance, if the git repository's name matches the app ID, every project member can effortlessly locate it and utilize the information stored there (commit descriptions).
-Another example is naming transport packages with all ABAP dictionary objects created for the custom app. By following the contents of such a transport package, it is possible to gain insight into how the app is built without the need to reiterate it in technical documents. Keeping a list of the apps with their IDs will also remind you to update your documentation constantly.
+A list of custom apps with IDs is already a foundation of technical documentation. Although it takes time to specify the requirements and features of custom apps, maintaining an official list of the apps is a quick yet fundamental long-term step. Initially, the app list provides an understanding of the extent of custom solutions for the project. Additionally, unique App IDs can facilitate live documentation by linking the names of objects stored outside your app directory. For instance, if the git repository's name matches the app ID, every project member can effortlessly locate it and utilize the information stored there (commit descriptions).
+Another example is naming transport packages with all ABAP dictionary objects created for the custom app. By following the contents of such a transport package, project members gain insight into how developers built the app without restating it in technical documents. Keeping a list of the apps with their IDs will also remind you to update your documentation constantly.
 
 ## Reason 2: Communication in Projects
-Clear identification of the applications in scope helps address the following challenges: How can users identify the correct app when contacting the support center agent? How can project members indicate the applications that require: Status tracking during the development, testing, and documentation process Assignment to a specific business area to establish responsibility during the development, testing, and support of applications.
+Identifying the applications in scope is crucial. It helps with several challenges. First, users can find the right app when contacting support. Next, project members can easily track the status of apps during development, testing, and documentation. Finally, assigning apps to specific business areas clarifies responsibility throughout the project.
 
 ## Reason 3: Scope management
-The list custom apps and SAP standard apps enabled in FLP determine the project's scope. Adding a new app to the Fiori launchpad, especially a custom one, has a major cost impact thus, you should track it. By keeping the rule of including the app entry in the documentation before implementing it, you will gain scope control, together with documentation accuracy.
+
+The apps enabled in the Fiori Launchpad, whether custom or standard, define the project’s scope. Adding a new app, especially a custom one, can be costly. So, it’s crucial to track it. To maintain scope control and accurate documentation, always include the app in your documentation before implementing it. This simple step ensures clarity and avoids surprises.
 
 ## Proper identification