diff --git a/docs/Developing-an-Application/configure-page-elements-047507c.md b/docs/Developing-an-Application/configure-page-elements-047507c.md
index d3de756..a94374c 100644
--- a/docs/Developing-an-Application/configure-page-elements-047507c.md
+++ b/docs/Developing-an-Application/configure-page-elements-047507c.md
@@ -6,7 +6,7 @@
 
 Developers can configure the SAP Fiori elements applications by using manifest settings and SAPUI5 flexibility changes \(`OData V2`\) in the *Page Editor*. The configuration properties available for UI-based maintenance are provided by the <code><a href="https://www.npmjs.com/package/@sap/ux-specification">@sap/ux-specification</a></code> node module, which is installed in the application's root folder.
 
-There are different module versions that correspond to the different SAPUI5 versions. You can find the right version by checking the UI5-\* tags at [@sap/ux-specification](https://www.npmjs.com/package/@sap/ux-specification?activeTab=versions). In case you need to change the **minUI5version** please see, [Application Minimum SAPUI5 Version](../Project-Functions/application-minimum-sapui5-version-009f43e.md).
+There are different module versions that correspond to the different SAPUI5 versions. You can find the right version by checking the UI5-\* tags at [@sap/ux-specification](https://www.npmjs.com/package/@sap/ux-specification?activeTab=versions). In case you need to change the **minUI5version** please see, [Application SAPUI5 Version](../Project-Functions/application-sapui5-version-009f43e.md).
 
 An overview of the available manifest and **UI5** flexibility properties can be accessed in the [Application Information](../Project-Functions/application-information-c3e0989.md) page. In addition, you can access the Configuration Documentation by right-clicking on your project in the tree view of the application modeler.
 
diff --git a/docs/Project-Functions/application-minimum-sapui5-version-009f43e.md b/docs/Project-Functions/application-minimum-sapui5-version-009f43e.md
deleted file mode 100644
index a35d94e..0000000
--- a/docs/Project-Functions/application-minimum-sapui5-version-009f43e.md
+++ /dev/null
@@ -1,8 +0,0 @@
-<!-- loio009f43e381234626b41e542dd7335672 -->
-
-# Application Minimum SAPUI5 Version
-
-The minimum SAPUI5 version declares the version, which is required at runtime to support all the features used in application development. If the target system for deployment doesn’t have the required minimum, the [deployed application](../Deploying-an-Application/deploying-an-application-1b7a3be.md) in SAP Fiori tools shows a warning. The version must be defined by the developer. This can be done during generation when selecting a version for the project. Later changes can be done with the command `Fiori: Change Minimum SAPUI5 Version`.
-
-The application's minimum version is also used to determine which corresponding version of [@sap/ux-specification](https://www.npmjs.com/package/@sap/ux-specification) is installed along the project to provide the matching feature set in application modeler and guided development.
-
diff --git a/docs/Project-Functions/application-sapui5-version-009f43e.md b/docs/Project-Functions/application-sapui5-version-009f43e.md
new file mode 100644
index 0000000..cf40f67
--- /dev/null
+++ b/docs/Project-Functions/application-sapui5-version-009f43e.md
@@ -0,0 +1,120 @@
+<!-- loio009f43e381234626b41e542dd7335672 -->
+
+# Application SAPUI5 Version
+
+
+
+<a name="loio009f43e381234626b41e542dd7335672__section_dk3_c11_cdc"/>
+
+## Minimum SAPUI5 Version
+
+The minimum SAPUI5 version declares the version which is required at runtime to support the features used in application development. It is set via the `minUI5Version` property in the `manifest.json` file:
+
+> ### Sample Code:  
+> JSON
+> 
+> ```
+> {
+>   "sap.ui5": {
+>     "dependencies": {
+>       "minUI5Version": "1.120.4"
+>     }
+>   }
+> }
+> ```
+
+If the target system does not have the required minimum SAPUI5 version, a warning message appears when deploying your application. For more information, see [Deploying an Application](../Deploying-an-Application/deploying-an-application-1b7a3be.md). The minimum SAPUI5 version is set during generation when selecting a version for the project and can also be changed using the *Fiori: Change Minimum SAPUI5 Version* command.
+
+It is also used to determine which version of the [@sap/ux-specification](https://www.npmjs.com/package/@sap/ux-specification) module is installed to provide the matching feature set in Application Modeler and Guided Development. Changing the minimum SAPUI5 version with the *Fiori: Change Minimum SAPUI5 Version* command will update the `@sap/ux-specification` module if needed.
+
+
+
+<a name="loio009f43e381234626b41e542dd7335672__section_m1n_3c1_cdc"/>
+
+## SAPUI5 Preview Version
+
+The application's minimum SAPUI5 version is used by default for previewing an application in the development environment. You can use a different version by creating a run configuration. For more information, see [Previewing an Application](../Previewing-an-Application/previewing-an-application-b962685.md).
+
+The SAPUI5 preview version is fetched by default from `https://ui5.sap.com`. If the requested version is not found, the next higher available version is used. You can set different source paths and different default SAPUI5 preview versions by configuring `@sap/ux-ui5-tooling`. For more information, see [@sap/ux-ui5-tooling](https://www.npmjs.com/package/@sap/ux-ui5-tooling?activeTab=readme).
+
+
+
+<a name="loio009f43e381234626b41e542dd7335672__section_tbd_gd1_cdc"/>
+
+## SAPUI5 Deployed Version
+
+The SAPUI5 version used for a deployed application depends on the target platform and whether an application is running standalone or embedded in the SAP Fiori launchpad.
+
+
+
+### ABAP Environment
+
+**SAP Fiori launchpad** 
+
+SAP Fiori applications deployed to an ABAP environment and embedded in SAP Fiori launchpad will use the SAPUI5 version deployed in the backend.
+
+**Standalone** 
+
+If the application is running standalone using a deployed `index.html`, then the version depends on the configuration in the `index.html` file. Applications generated with the SAP Fiori generator contain an `index.html` file with a relative path to the host:
+
+> ### Sample Code:  
+> HTML
+> 
+> ```
+> <script id="sap-ui-bootstrap" src="resources/sap-ui-core.js">
+> ```
+
+These applications will also use the SAPUI5 version installed in the backend system. Their path can be modified to load resources directly from `https://ui5.sap.com` or a specific SAPUI5 version:
+
+> ### Sample Code:  
+> HTML
+> 
+> ```
+> <script id="sap-ui-bootstrap" src="https://ui5.sap.com/1.114.12/resources/sap-ui-core.js">
+> ```
+
+
+
+### Cloud Foundry Environment
+
+**Launchpad Service** 
+
+SAP Fiori applications deployed to Cloud Foundry run in an iFrame using the SAPUI5 version of the backend. For more information about the launchpad service. For more information, see [SAP Build Work Zone](https://help.sap.com/docs/build-work-zone-standard-edition/sap-build-work-zone-standard-edition/what-is-sap-build-work-zone-standard-edition).
+
+**Standalone** 
+
+If the application is running standalone, the *Fiori: Add Deployment Configuration* command adds a route to a destination for SAPUI5 resources to the `xs-app.json`:
+
+> ### Sample Code:  
+> JSON
+> 
+> ```
+> {
+>   "routes": [
+>     {
+>       "source": "^/resources/(.*)$",
+>       "target": "/resources/$1",
+>       "authenticationType": "none",
+>       "destination": "ui5"
+>     }
+>   ]
+> }
+> ```
+
+Also, an instance based destination pointing to `https://ui5.sap.com` is added to the `mta.yaml`:
+
+> ### Sample Code:  
+> YAML
+> 
+> ```
+> instance:
+>   destinations:
+>     - Authentication: NoAuthentication
+>       Name: ui5
+>       ProxyType: Internet
+>       Type: HTTP
+>       URL: https://ui5.sap.com
+> ```
+
+By default, the application uses the latest SAPUI5 version. This can be changed in the `mta.yaml` or by configuring the generated destination service using SAP Business Technology Platform \(SAP BTP\). You can also replace the instance based destination with an account level destination. For more information, see [SAP Cloud Portal Service on Cloud Foundry](https://help.sap.com/docs/cloud-portal-service/sap-cloud-portal-service-on-cloud-foundry/configure-application-routing-xs-app-json).
+
diff --git a/docs/adapt-the-ui-af9747f.md b/docs/adapt-the-ui-af9747f.md
index 40d39c5..5afbe87 100644
--- a/docs/adapt-the-ui-af9747f.md
+++ b/docs/adapt-the-ui-af9747f.md
@@ -29,26 +29,28 @@ Make changes to the UI elements of the adaptation project.
 
 SAPUI5 adaptation project uses the editing capabilities of the SAPUI5 Visual Editor tool. The SAPUI5 Visual Editor is a design-time editor that provides an intuitive user interface to modify SAPUI5 adaptation project applications. For example, you can add, remove, or move fields and groups. You can also view all properties of the controls in the application and change the configurable properties.
 
-If you have created your project with Safe Mode switched on, you will not be able to do some of the actions described in this section. More specifically you will not be able to change properties, add fragments, or add controller extensions. If you think you want to turn Safe Mode off, so you can use these features, you can do this by selecting the switch named *Safe Mode* in the Visual Editor. Be aware that if you switch it off once, it is not possible to switch it on again.
+If you have created your project with Safe Mode, you cannot change properties, add fragments, or add controller extensions. To turn off Safe Mode, deselect the *Safe Mode* switch in the Visual Editor. Note once you switch it off, you cannot switch it on again.
 
 > ### Tip:  
-> The SAPUI5 Visual Editor will show you your project using the SAPUI5 version that you have set during its generation. If you want, you can preview your project using another SAPUI5 version, but you need to set it in the project\`s settings prior the next launch of the SAPUI5 Visual Editor. It can be easily done following these steps:
+> The SAPUI5 Visual Editor will show you your project using the SAPUI5 version that you have set during generation. You can preview your project using another SAPUI5 version by setting it in the project\`s settings and relaunch SAPUI5 Visual Editor. Perform the following steps:
 > 
-> 1.  Open the `ui5.yaml` file placed in the root of your project.
+> 1.  Open the `ui5.yaml` file in the root of your project.
 > 
-> 2.  Find the `framework/version` parameter and change their value to point to the desired SAPUI5 version.
-> 3.  Find the `ui5/version` property, and change its value to the same desired SAPUI5 version.
+> 2.  Find the `framework/version` parameter and change its value to point to the desired SAPUI5 version.
+> 3.  Find the `ui5/version` property and change its value to the same desired SAPUI5 version.
 > 4.  Find the `ui5/url` property and change its value to point to the URL for the same desired SAPUI5 version.
 > 
-> Have in mind that changing other settings in this file will result in undesirable changes in the behavior of your project, and it is strongly advised not to make such changes.
+> Do not change other settings in this file because it will cause errors in your project.
 
 The editor has an Outline pane, a Canvas \(application preview\), and a Properties pane.
 
+If the application page is based on an SAP Fiori elements list report or an object page floorplan, a quick actions list is displayed above the Properties pane. This quick actions list provides an easy way for you to create the most commonly used adaptation changes. The available actions depend on the page floorplan and the SAPUI5 version.
+
 The buttons on the SAPUI5 Visual Editor toolbar allow you to:
 
--   Navigate through and preview the application using the *Preview* mode.
+-   Navigate through and preview the application using the *Navigation* mode.
 
--   Change the application using the *Edit* mode. In this mode, if you click a UI element in the Canvas, the element is selected and highlighted in the Outline pane and vice versa. You can deselect the UI element by clicking it again in the Canvas. The Properties pane displays the properties of the UI element.
+-   Change the application using the *Edit* mode. In this mode, if you click a UI element in the Canvas, the element is selected and highlighted in the Outline pane and the same if you click a UI element in the Canvas. You can deselect the UI element by clicking it again in the Canvas. The Properties pane displays the properties of the UI element.
 
 -   Change the device format of the canvas to smartphone, tablet, or desktop view.
 
@@ -64,9 +66,9 @@ The buttons on the SAPUI5 Visual Editor toolbar allow you to:
 
 ## Procedure
 
-1.  In your workspace, еxpand the `webapp` folder and right click the `manifest.appdescr_variant` file and choose *Open SAPUI5 Visual Editor*. SAPUI5 Visual Editor launches and the application loads in the editor for you to make the changes when you switch to Edit mode from Preview mode.
+1.  In your workspace, еxpand the `webapp` folder and right click the `manifest.appdescr_variant` file and choose *Open SAPUI5 Visual Editor*. SAPUI5 Visual Editor launches and the application loads in the editor for you to make the changes when you switch to Edit mode from *Navigation* mode.
 2.  Navigate to the page containing the UI element you want to change.
-3.  From the editor header, select *Edit*.
+3.  From the editor header, click *Edit*.
 
 
 
@@ -102,12 +104,12 @@ The buttons on the SAPUI5 Visual Editor toolbar allow you to:
 </td>
 <td valign="top">
 
-1.  Hover over or select a group or a field and choose *Add Field* from the context menu.
+1.  Hover over or select a group or a field and click *Add Field* from the context menu.
 2.  Select the fields from the list of available fields that you want to add to the UI.
 
     You can also search for field labels and tooltips, or sort the fields in alphabetical order.
 
-3.  To apply your adaptations, choose *OK*.
+3.  To apply your adaptations, click *OK*.
 
 
 
@@ -121,11 +123,11 @@ The buttons on the SAPUI5 Visual Editor toolbar allow you to:
 </td>
 <td valign="top">
 
-1.  Hover over or select a group or select the form it’s contained in and choose *Add Group* from the context menu.
+1.  Hover over or select a group or select the form it’s contained in and click *Add Group* from the context menu.
 
     The default group title is *New Group*, and you can rename it to whatever you want.
 
-2.  To apply your adaptations, press [ENTER\] or select another element.
+2.  To apply your adaptations, press [Enter\] or select another element.
 
 
 
@@ -139,7 +141,7 @@ The buttons on the SAPUI5 Visual Editor toolbar allow you to:
 </td>
 <td valign="top">
 
-1.  Hover over or select a section and choose *Add Section* from the context menu.
+1.  Hover over or select a section and click *Add Section* from the context menu.
 
     > ### Note:  
     > If all available sections are already on the object page, you cannot use this function and it’s grayed out in the context menu.
@@ -148,7 +150,7 @@ The buttons on the SAPUI5 Visual Editor toolbar allow you to:
 
     You can also search for sections or sort them in alphabetical order.
 
-3.  To apply your adaptations, choose *OK*.
+3.  To apply your adaptations, click *OK*.
 
 
 
@@ -162,9 +164,9 @@ The buttons on the SAPUI5 Visual Editor toolbar allow you to:
 </td>
 <td valign="top">
 
-1.  Double-click a field or group. You can also hover over or select it and choose *Rename Field* or *Rename Group* from the context menu.
+1.  Double-click a field or group. You can also hover over or select it and click *Rename Field* or *Rename Group* from the context menu.
 2.  Rename the field label or group title.
-3.  To apply your adaptations, press [ENTER\]; to quit, press [ESC\].
+3.  To apply your adaptations, press [Enter\]. To quit, press [ESC\].
 
 
 
@@ -181,7 +183,7 @@ The buttons on the SAPUI5 Visual Editor toolbar allow you to:
 1.  Drag a field, group, or section.
 2.  Drop the field, group, or section on its new location.
 
-    A space appears where you can drop it. You can drop a field above or below any of the highlighted fields or in any group marked with a dashed box; you can drop a group or section on any of the highlighted groups or sections.
+    A space appears where you can drop it. You can drop a field above or below any of the highlighted fields or in any group marked with a dashed box. You can drop a group or section on any of the highlighted groups or sections.
 
 
 
@@ -196,8 +198,8 @@ The buttons on the SAPUI5 Visual Editor toolbar allow you to:
 </td>
 <td valign="top">
 
-1.  Hover over or select a field or group and choose *Cut* from the context menu. The cut field or group gets highlighted. Also, the groups where you can paste the cut field or the forms where you can paste the cut group get highlighted using dashed boxes. Move fields, groups, and object page sections.
-2.  To paste a cut field, hover over or select a highlighted group or a field in a highlighted group and choose *Paste*. To paste a cut group, hover over or select a group in the highlighted forms and choose *Paste* from the context menu.
+1.  Hover over or select a field or group and clicke *Cut* from the context menu. The cut field or group gets highlighted. Also, the groups where you can paste the cut field or the forms where you can paste the cut group get highlighted using dashed boxes. Move fields, groups, and object page sections.
+2.  To paste a cut field, hover over or select a highlighted group or a field in a highlighted group and click *Paste*. To paste a cut group, hover over or select a group in the highlighted forms and click *Paste* from the context menu.
 
 > ### Note:  
 > To remove the highlighting and exit pasting, press [ESC\].
@@ -218,7 +220,7 @@ You can combine up to three fields so that they’re displayed in a single line.
 
 1.  Select a field.
 2.  Press and hold [CTRL\]. Move fields, groups, and object page while selecting the other fields you want to combine with this field.
-3.  Choose *Combine* from the context menu of one of the selected fields where you want the combined fields to be displayed.
+3.  Click *Combine* from the context menu of one of the selected fields where you want the combined fields to be displayed.
 
 
 
@@ -233,7 +235,7 @@ You can combine up to three fields so that they’re displayed in a single line.
 <td valign="top">
 
 1.  Hover over or select the combined fields.
-2.  Choose *Split* from the context menu.
+2.  Click *Split* from the context menu.
 
 
 
@@ -248,7 +250,7 @@ You can combine up to three fields so that they’re displayed in a single line.
 <td valign="top">
 
 1.  Hover over or select the field, group, or section that you want to remove from the UI.
-2.  Choose *Remove Field*, *Remove Group*, or *Remove Section* from the context menu or press [DEL\].
+2.  Click *Remove Field*, *Remove Group*, or *Remove Section* from the context menu or press [DEL\].
 
     The fields and sections are only removed from the UI, not permanently deleted. They're still available in the list of available fields or sections, and you can add them again at any point. You cannot remove mandatory fields \(also those contained in groups\) by accident as the system will ask you to confirm.
 
@@ -265,7 +267,7 @@ You can combine up to three fields so that they’re displayed in a single line.
 
 ## Embedding Content
 
-Embedding content is done the same way, as in the key user scenario. You can follow the procedure described in [Embedding Content](https://help.sap.com/viewer/0f8b49c4dfc94bc0bda25a19aa93d5b2/latest/en-US/bfdf15154f16419fb60ce598b21fe515.html).
+To embed content, perform the following steps in [Embedding Content](https://help.sap.com/viewer/0f8b49c4dfc94bc0bda25a19aa93d5b2/latest/en-US/bfdf15154f16419fb60ce598b21fe515.html).
 
 
 
@@ -273,5 +275,5 @@ Embedding content is done the same way, as in the key user scenario. You can fol
 
 ## Preview in a Separate Browser Tab
 
-See [Preview the Adaptation Project](preview-the-adaptation-project-64cc15b.md).
+You can preview your project in a separate browser tab. For more information, see [Preview the Adaptation Project](preview-the-adaptation-project-64cc15b.md).
 
diff --git a/docs/adapting-the-ui-9c1e7b4.md b/docs/adapting-the-ui-9c1e7b4.md
index c496dc4..292c2f7 100644
--- a/docs/adapting-the-ui-9c1e7b4.md
+++ b/docs/adapting-the-ui-9c1e7b4.md
@@ -2,6 +2,8 @@
 
 # Adapting the UI
 
+Learn how to adapt the UI of applications using the Adaption Editor .
+
 
 
 <a name="loio9c1e7b438d2f48038d8870c55d75770a__section_tkz_f34_xlb"/>
@@ -34,11 +36,13 @@ SAPUI5 adaptation projects use the editing capabilities of the Adaptation Editor
 
 The editor has an Outline pane, a Canvas \(application preview\), and a Properties pane.
 
+If the application page is based on an SAP Fiori elements list report or an object page floorplan, a quick actions list is displayed above the Properties pane. This quick actions list provides an easy way for you to create the most commonly used adaptation changes. The available actions depend on the page floorplan and the SAPUI5 version.
+
 The buttons on the Adaptation Editor toolbar allow you to:
 
 -   Navigate through and preview the application using the *Navigation* mode.
 
--   Change the application using the *UI Adaptation Mode* mode. In this mode, if you click a UI element in the Canvas, the element is selected and highlighted in the Outline pane and the other way around. You can deselect the UI element by clicking it again in the Canvas. The Properties pane displays the properties of the UI element.
+-   Change the application using the *Adaptation Mode* mode. In this mode, if you click a UI element in the Canvas, the element is selected and highlighted in the Outline pane and the other way around. You can deselect the UI element by clicking it again in the Canvas. The Properties pane displays the properties of the UI element.
 
 -   Change the device format of the canvas to smartphone, tablet, or desktop view.
 
@@ -52,15 +56,14 @@ The buttons on the Adaptation Editor toolbar allow you to:
 
 ## Procedure
 
-1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Preview Application*.
-2.  Click *start-editor*.
+1.  In your workspace, еxpand the `webapp` folder, right click the `manifest.appdescr_variant` file and choose *Open Adaptation Editor*..
 
-    The Adaptation Editor launches in a browser window and the application loads in the editor for you to make the changes when you switch to UI Adaptation mode or to navigate and preview the application when you switch to Navigation mode.
+    The Adaptation Editor launches in a browser window and the application loads in the editor for you to make the changes when you switch to Adaptation mode or to navigate and preview the application when you switch to Navigation mode.
 
     > ### Remember:  
-    > VS Code needs to be kept running in order for the editor to work.
+    > Visual Studio Code \(VS Code\) needs to be kept running in order for the editor to work.
 
-3.  If you want to change to a different view,, switch to Navigation mode,navigate to the new video, and then switch back to UI Adaptation Mode.
+2.  If you want to change to a different view, switch to Navigation mode, navigate to the new view, and then switch back to Adaptation Mode.
 
 
 
@@ -117,7 +120,7 @@ The buttons on the Adaptation Editor toolbar allow you to:
 
 1.  Hover over or select a group or select the form it’s contained in and click *Add Group* from the context menu.
 
-    The default group title is *New Group*, but you can rename it.
+    The default group title is *New Group* but you can rename it.
 
 2.  To apply your adaptations, press [Enter\] or select another element.
 
@@ -158,7 +161,7 @@ The buttons on the Adaptation Editor toolbar allow you to:
 
 1.  Double-click a field or group. You can also hover over or select it and click *Rename Field* or *Rename Group* from the context menu.
 2.  Rename the field label or group title.
-3.  To apply your adaptations, press [Enter\]; to quit, press [Esc\].
+3.  To apply your adaptations, press [Enter\]. To quit, press [Esc\].
 
 
 
@@ -175,7 +178,7 @@ The buttons on the Adaptation Editor toolbar allow you to:
 1.  Drag a field, group, or section.
 2.  Drop the field, group, or section on its new location.
 
-    A space appears where you can drop it. You can drop a field above or below any of the highlighted fields or in any group marked with a dashed box; you can drop a group or section on any of the highlighted groups or sections.
+    A space appears where you can drop it. You can drop a field above or below any of the highlighted fields or in any group marked with a dashed box. You can drop a group or section on any of the highlighted groups or sections.
 
 
 
diff --git a/docs/add-fragments-to-an-aggregation-or-extension-point-6033d56.md b/docs/add-fragments-to-an-aggregation-or-extension-point-6033d56.md
index 8868797..c173be1 100644
--- a/docs/add-fragments-to-an-aggregation-or-extension-point-6033d56.md
+++ b/docs/add-fragments-to-an-aggregation-or-extension-point-6033d56.md
@@ -2,7 +2,7 @@
 
 # Add Fragments to an Aggregation or Extension Point
 
-You have the possibility to add fragments to an aggregation of your choice, or to an extension point.
+You can add fragments to an aggregation or to an extension point.
 
 
 
@@ -25,13 +25,13 @@ You have the possibility to add fragments to an aggregation of your choice, or t
 
 ### Procedure
 
-1.  In your workspace, from the project context menu, choose *SAPUI5 Visual Editor*.
+1.  In your workspace, from the project context menu, click *SAPUI5 Visual Editor*.
 
     The application opens in the canvas in preview mode.
 
-2.  From the editor header, choose *Edit*.
+2.  From the editor header, click *Edit*.
 
-3.  On the UI, select a control \(such as a smart-filter bar or an overflow toolbar\), and from its context menu, choose *Add Fragment*.
+3.  On the UI, select a control \(such as a smart filter bar or an overflow toolbar\), and from its context menu, click *Add Fragment*.
 
     In the dialog box that opens, the default target aggregation and last index are selected. A list displays the fragments available for the selected target aggregation. You can also create fragments. Choose the target aggregation and the index from the list where you want to add the fragment. You cannot reuse the same fragment multiple times.
 
@@ -40,22 +40,22 @@ You have the possibility to add fragments to an aggregation of your choice, or t
 
 4.  To create a fragment:
 
-    1.  Choose *Create New*.
+    1.  Click *Create New*.
 
         The default target aggregation is the one you selected in the previous step.
 
-    2.  Enter a name for the fragment and choose *Create*.
+    2.  Enter a name for the fragment and click *Create*.
 
-        A fragment.xml file is created in the folder: *Your project name* \> *webapp* \> *changes* \> *fragments* and opens in the editor.
+        A `fragment.xml` file is created in the folder: *Your project name* \> *webapp* \> *changes* \> *fragments* and opens in the editor.
 
-    3.  Define the fragment. Save and close the .xml file. For more information, see [SAPUI5 documentation](https://sapui5.hana.ondemand.com/#/topic/2c677b574ea2486a8d5f5414d15e21c5).
+    3.  Define the fragment. Save and close the `.xml` file. For more information, see [SAPUI5 documentation](https://sapui5.hana.ondemand.com/#/topic/2c677b574ea2486a8d5f5414d15e21c5).
 
-        An associated `addXML.change` file is created for every fragment in the folder: *Your project name* \> *webapp* \> *changes*. This change file contains the reference to the fragment.xml file, selected target aggregation, and index.
+        An associated `addXML.change` file is created for every fragment in the folder: *Your project name* \> *webapp* \> *changes*. This change file contains the reference to the `fragment.xml` file, selected target aggregation, and index.
 
 
 5.  To choose an existing fragment from the list:
 
-    1.  Select a fragment from the list and choose *Add*.
+    1.  Select a fragment from the list and click *Add*.
 
     2.  Double click the `fragment.xml` file from the workspace to open it in the editor.
 
@@ -67,7 +67,7 @@ You have the possibility to add fragments to an aggregation of your choice, or t
     After adding fragments, you'll be prompted to reload the SAPUI5 Visual Editor to see your changes.
 
     > ### Note:  
-    > Have in mind that you should add definition of the namespace of the controls you are going to use inside of the fragment. Also, you should use stable and unique IDs for the controls you define.
+    > You must add the definition of the namespace of the controls you are going to use inside of the fragment. Also, you must use stable and unique IDs for the controls you define.
     > 
     > Example:
     > 
@@ -77,10 +77,10 @@ You have the possibility to add fragments to an aggregation of your choice, or t
     > </core:FragmentDefinition>
     > ```
     > 
-    > Also, each control might have its own specific rules for its definition and they should be followed in order for everything to work fine.
+    > Also, follow the specific rule each control has for its definition.
 
     > ### Remember:  
-    > You can delete the fragments that you create. For a seamless experience, first delete the change files associated to a fragment and then delete the fragment. If you don't delete them, you might not be able to add further fragments to the adaptation project.
+    > You can delete the fragments that you create. Delete the change files associated to a fragment and then delete the fragment. If you do not, you will not be able to add fragments to the adaptation project.
 
 
 
@@ -93,40 +93,40 @@ You have the possibility to add fragments to an aggregation of your choice, or t
 
 ### Prerequisites
 
--   You are using freestyle SAPUI5 application that has extension points for basis of your adaptation project.
+-   You are using a freestyle SAPUI5 application that has extension points for basis of your adaptation project.
 
 
 
 ### Procedure
 
-1.  In your workspace, from the project context menu, choose *SAPUI5 Visual Editor*.
+1.  In your workspace, from the project context menu, click *SAPUI5 Visual Editor*.
 
     The application opens in the canvas in preview mode.
 
-2.  From the editor header, choose *Edit*.
+2.  From the editor header, click *Edit*.
 
-3.  If you expand the outline tree you will be able to see which element is a possible extension point. Then you can select the element in the tree and you will see its parent marked and highlighted in the visual part of the editor. You can then right click on that highlighted element and choose *Add fragment at extension point*.
+3.  If you expand the outline tree, you will be able to see which element is a possible extension point. Then you can select the element in the tree and you will see its parent marked and highlighted in the visual part of the editor. You can then right click on that highlighted element and click *Add fragment at extension point*.
 
     In the dialog box that opens, the default extension point is selected. A list displays the fragments available for the selected extension point. You can also create fragments. Choose the target extension point and the index from the list where you want to add the fragment. You cannot reuse the same fragment multiple times.
 
 4.  To create a fragment:
 
-    1.  Choose *Create New*.
+    1.  Click *Create New*.
 
         The default extension point is the one you selected in the previous step.
 
-    2.  Enter a name for the fragment and choose *Create*.
+    2.  Enter a name for the fragment and click *Create*.
 
-        A fragment.xml file is created in the folder, *Your project name* \> *webapp* \> *changes* \> *fragments* and opens in the editor.
+        A `fragment.xml` file is created in the folder: *Your project name* \> *webapp* \> *changes* \> *fragments* and opens in the editor.
 
     3.  Define the fragment. Save and close the `.xml` file. For more information, see [SAPUI5 documentation](https://sapui5.hana.ondemand.com/#/topic/2c677b574ea2486a8d5f5414d15e21c5).
 
-        An associated `addXML.change` file is created for every fragment in the folder, *Your project name* \> *webapp* \> *changes*. This change file contains the reference to the fragment.xml file, selected target aggregation, and index.
+        An associated `addXML.change` file is created for every fragment in the folder: *Your project name* \> *webapp* \> *changes*. This change file contains the reference to the`fragment.xml` file, selected target aggregation, and index.
 
 
 5.  To choose an existing fragment from the list:
 
-    1.  Select a fragment from the list and choose *Add*.
+    1.  Select a fragment from the list and click *Add*.
 
     2.  Double click the `fragment.xml` file from the workspace to open it in the editor.
 
@@ -138,7 +138,7 @@ You have the possibility to add fragments to an aggregation of your choice, or t
     After adding fragments, you'll be prompted to reload the SAPUI5 Visual Editor to see your changes.
 
     > ### Note:  
-    > Have in mind that you should add definition of the namespace of the controls you are going to use inside of the fragment. Also, you should use stable and unique IDs for the controls you define.
+    > You must add the definition of the namespace of the controls you are going to use inside of the fragment. You must use stable and unique IDs for the controls you define.
     > 
     > Example:
     > 
@@ -148,9 +148,9 @@ You have the possibility to add fragments to an aggregation of your choice, or t
     > </core:FragmentDefinition>
     > ```
     > 
-    > Also, each control might have its own specific rules for its definition and they should be followed in order for everything to work fine.
+    > Also, follow the rules each control has for its definition.
 
     > ### Remember:  
-    > You can delete the fragments that you create. For a seamless experience, first delete the change files associated to a fragment and then delete the fragment. If you don't delete them, you might not be able to add further fragments to the adaptation project.
+    > You can delete the fragments that you create. Delete the change files associated to a fragment and then delete the fragment. If you do not delete them, you will not be able to add further fragments to the adaptation project.
 
 
diff --git a/docs/add-fragments-to-an-aggregation-or-extension-point-bdb6561.md b/docs/add-fragments-to-an-aggregation-or-extension-point-bdb6561.md
index c4295e9..0a2b79b 100644
--- a/docs/add-fragments-to-an-aggregation-or-extension-point-bdb6561.md
+++ b/docs/add-fragments-to-an-aggregation-or-extension-point-bdb6561.md
@@ -2,6 +2,8 @@
 
 # Add Fragments to an Aggregation or Extension Point
 
+Learn how to add fragments to an aggregation or extension point using UI Adaption mode.
+
 
 
 <a name="loiobdb6561e8c554b29bb6f6ebe0279e5c5__section_ygx_xd4_2mb"/>
@@ -27,12 +29,12 @@
 
     The application opens in the canvas in UI Adaptation mode.
 
-2.  On the UI, select a control \(such as a smart-filter bar or an overflow toolbar\), and from its context menu, click *Add Fragment*.
+2.  On the UI, select a control \(such as a smart filter bar or an overflow toolbar\), and from its context menu, click *Add Fragment*.
 
     In the dialog box that opens, the default target aggregation and last index are selected. Choose the target aggregation and the index from the list where you want to add the fragment. You cannot reuse the same fragment multiple times.
 
     > ### Note:  
-    > The index is disabled for `controlConfiguration` aggregation in the control Smart Filter Bar. This aggregation currently does not support positioning at a specific index.
+    > The index is disabled for `controlConfiguration` aggregation in the control Smart Filter Bar. This aggregation does not support positioning at a specific index.
 
 3.  To create a fragment:
 
@@ -47,10 +49,10 @@
 
 4.  Navigate to the canvas to see the changes that you made.
 
-    In order to load the added change you need to reload the browser tab in which the adaptation project editor is opened. If you have opened the application preview in a separate browser tab, it also needs to be refreshed.
+    To load the added change, you need to reload the browser tab for the adaptation project editor and application preview \(if opened in a separate tab\).
 
     > ### Note:  
-    > You should add the definition of the namespace of the controls you are going to use inside of the fragment. Also, you should use stable and unique IDs for the controls you define.
+    > Add the definition of the namespace for the controls you are going to use inside of the fragment. Also, use stable and unique IDs for the controls you define.
     > 
     > Example:
     > 
@@ -60,10 +62,10 @@
     > </core:FragmentDefinition>
     > ```
     > 
-    > Each control might have its own specific rules for its definition.
+    > Follow the definition rules for your controls. Each control can have its own specific rules.
 
     > ### Remember:  
-    > You can delete the fragments that you create. For a seamless experience, first delete the change files associated to a fragment and then delete the fragment. If you don't delete them, you might not be able to add further fragments to the adaptation project.
+    > You can delete the fragments that you create. Delete the change files associated to a fragment first and then delete the fragment. If you do not, you will not be able to add further fragments to the adaptation project.
 
 
 
@@ -78,26 +80,26 @@
 
 -   You are using SAPUI5 version 1.78 or above.
 
--   You are using SAP\_UI version 7.55 or above.
--   You are using freestyle application that has extension points for basis of your adaptation project.
+-   You are using `SAP_UI` version 7.55 or above.
+-   You are using a freestyle application that has extension points for basis of your adaptation project.
 
 
 
 ### Procedure
 
-1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file an choose *Preview Application*. Choose *start-editor*.
+1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Preview Application*. Click *start-editor*.
 
     The application opens in the canvas in UI Adaptation mode.
 
-2.  If you expand the outline tree you will be able to see which element is a possible extension point. Then you can select the element in the tree and you will see its parent marked and highlighted in the visual part of the editor. You can then right click on that highlighted element and choose *Add fragment at extension point*.
+2.  Expand the outline tree. You can see which element is a possible extension point. Then, select the element in the tree and you will see its parent marked and highlighted in the visual part of the editor. Right click on the highlighted element and click *Add fragment at extension point*.
 
-    In the dialog box that opens, the default extension point is selected. Choose the target extension point and the index from the list where you want to add the fragment. You cannot reuse the same fragment multiple times.
+    In the dialog box, the default extension point is selected. Choose the target extension point and the index from the list where you want to add the fragment. You cannot reuse the same fragment multiple times.
 
 3.  To create a fragment:
 
-    1.  Enter a name for the fragment and choose *Create*.
+    1.  Enter a name for the fragment and click *Create*.
 
-        A fragment.xml file is created in the folder, *Your project name* \> *webapp* \> *changes* \> *fragments* and opens in the editor.
+        A `fragment.xml` file is created in the folder, *Your project name* \> *webapp* \> *changes* \> *fragments* and opens in the editor.
 
     2.  Define the fragment. Save and close the `.xml` file. For more information, see [SAPUI5 documentation](https://sapui5.hana.ondemand.com/#/topic/2c677b574ea2486a8d5f5414d15e21c5).
 
@@ -106,12 +108,10 @@
 
 4.  Navigate to the canvas to see the changes that you made.
 
-    In order to load the added change you need to reload the browser tab in which the adaptation project editor is opened. If you have opened Preview of the application in a separate browser tab, it also needs to be refreshed.
-
-    .
+    To load the added change, you need to reload the browser tab for the adaptation project editor and application preview \(if opened in a separate tab\).
 
     > ### Note:  
-    > Have in mind that you should add definition of the namespace of the controls you are going to use inside of the fragment. Also, you should use stable and unique IDs for the controls you define.
+    > Add the definition of the namespace for the controls you are going to use inside of the fragment. Also, use stable and unique IDs for the controls you define.
     > 
     > Example:
     > 
@@ -121,9 +121,9 @@
     > </core:FragmentDefinition>
     > ```
     > 
-    > Also, each control might have its own specific rules for its definition and they should be followed in order for everything to work fine.
-
-    > ### Remember:  
-    > You can delete the fragments that you create. For a seamless experience, first delete the change files associated to a fragment and then delete the fragment. If you don't delete them, you might not be able to add further fragments to the adaptation project.
+    > Follow the definition rules for your controls. Each control can have its own specific rules.
+    > 
+    > > ### Remember:  
+    > > You can delete the fragments that you create. Delete the change files associated to a fragment first and then delete the fragment. If you do not, you will not be able to add further fragments to the adaptation project.
 
 
diff --git a/docs/adding-app-descriptor-changes-115ad56.md b/docs/adding-app-descriptor-changes-115ad56.md
index 3e8c414..1fb8af5 100644
--- a/docs/adding-app-descriptor-changes-115ad56.md
+++ b/docs/adding-app-descriptor-changes-115ad56.md
@@ -2,9 +2,9 @@
 
 # Adding App Descriptor Changes
 
-Adaptation project gives you the opportunity to add the following types of changes to your application variant.
+Adaptation projects give you the opportunity to add the following types of changes to your application variant.
 
-When extending Fiori Elements-based applications, additional manifest changes are available, for more information, see [Extending the Delivered Apps Manifest Using an Adaptation Project](https://ui5.sap.com/#/topic/a2b24a69baef4b91af2293ccc6b5871f).
+When extending Fiori Elements based applications, additional manifest changes are available. For more information, see [Extending the Delivered Apps Manifest Using an Adaptation Project](https://ui5.sap.com/#/topic/a2b24a69baef4b91af2293ccc6b5871f).
 
 
 
diff --git a/docs/adding-local-annotation-files-392a056.md b/docs/adding-local-annotation-files-392a056.md
index 52231c2..55ee14f 100644
--- a/docs/adding-local-annotation-files-392a056.md
+++ b/docs/adding-local-annotation-files-392a056.md
@@ -2,24 +2,26 @@
 
 # Adding Local Annotation Files
 
+Learn how to add local annotation files.
+
 
 
 <a name="loio392a0560ddef495c905b078edaafd318__prereq_aw4_j1x_l4b"/>
 
 ## Prerequisites
 
-For adaptation project for an On-Premise System: You have the ABAP Platform 2020 SP00 installed.
+For adaptation projects for an On-Premise System: Ensure you have ABAP Platform 2020 SP00 installed.
 
 
 
 ## Procedure
 
-1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and choose *Add Local Annotation File*.
+1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Add Local Annotation File*.
 
-2.  From the *Target*OData*Service* dropdown choose to which service from the manifest of the base application you want to add annotation file.
+2.  From the *Target OData Service* dropdown, choose which service from the manifest of the base application you want to add a annotation file for.
 
-3.  Choose if you want to create an empty annotation file that you can edit later, or to select already existing annotation file from a workspace.
+3.  Choose if you want to create an empty annotation file that you can edit later or select already existing annotation file from a workspace.
 
-4.  Choose *Finish* to create the change.
+4.  Click *Finish* to save your changes.
 
 
diff --git a/docs/adding-local-annotation-files-c5d62ca.md b/docs/adding-local-annotation-files-c5d62ca.md
index b08c482..e5139c1 100644
--- a/docs/adding-local-annotation-files-c5d62ca.md
+++ b/docs/adding-local-annotation-files-c5d62ca.md
@@ -10,12 +10,12 @@ This guide describes how to add annotation files to an adaptation project withou
 
 1.  Right click the `manifest.appdescr_variant` file of your adaptation project and select the *Adaptation Project* \> *Add Local Annotation File*.
 
-2.  After the wizard starts you may be asked to enter the credentials for the system that you created your adaptation project.
+2.  After the wizard starts, you may be asked to enter the credentials for the system that you created your adaptation project.
 
-3.  From the *Target OData Service* dropdown choose to which service from the manifest of the base application you want to add annotation file.
+3.  From the *Target OData Service* dropdown, choose to which service from the manifest of the base application you want to add annotation file.
 
-4.  Choose if you want to create an empty annotation file that you can edit later, or to select already existing annotation file from a workspace.
+4.  Choose if you want to create an empty annotation file that you can edit later or to select already existing annotation file from a workspace.
 
-5.  Choose *Finish* to create the change.
+5.  Click *Finish* to save your changes.
 
 
diff --git a/docs/adding-odata-service-and-new-sapui5-model-71eaa3f.md b/docs/adding-odata-service-and-new-sapui5-model-71eaa3f.md
index 2fda528..1fbb95c 100644
--- a/docs/adding-odata-service-and-new-sapui5-model-71eaa3f.md
+++ b/docs/adding-odata-service-and-new-sapui5-model-71eaa3f.md
@@ -2,19 +2,21 @@
 
 # Adding OData Service and New SAPUI5 Model
 
+Learn how to add a new OData service and SAPUI5 model.
+
 
 
 ## Context
 
-To add V2 service using annotations also the new annotation data source needs to be added.
+To add an OData V2 service using annotations, the new annotation data source has to be added.
 
 
 
 ## Procedure
 
-1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file an choose *Add*OData*Service* \> *Model*.
+1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Add OData Service* \> *Model*.
 
-2.  After the wizard starts enter the OData Service name for the service you want to add.
+2.  After the wizard appears, enter the OData Service name for the service you want to add.
 
 3.  Enter the OData Service URI.
 
@@ -22,9 +24,9 @@ To add V2 service using annotations also the new annotation data source needs to
 
 5.  Enter the OData Service SAPUI5 Model name of the model you want to add.
 
-6.  \(Optional\) Enter settings for the OData Service SAPUI5. Model in the format of `"key1":"value1","key2":"value2", …`.
+6.  \(Optional\) Enter settings for the OData Service SAPUI5 Model in the format: `"key1":"value1","key2":"value2",`.
 
-7.  \(Optional\) Choose whether to add annotation or not.
+7.  \(Optional\) Choose whether to add an annotation.
 
     If you choose yes, provide the following information:
 
@@ -32,9 +34,9 @@ To add V2 service using annotations also the new annotation data source needs to
 
     2.  Enter the OData Annotation Data Source URI.
 
-    3.  \(Optional\) Enter settings for the annotation in the format of `"key1":"value1","key2":"value2", …`.
+    3.  \(Optional\) Enter settings for the annotation in the format: `"key1":"value1","key2":"value2",`.
 
 
-8.  Choose *Finish* to create the change.
+8.  Click *Finish* to save your changes.
 
 
diff --git a/docs/adding-odata-service-and-new-sapui5-model-886e83b.md b/docs/adding-odata-service-and-new-sapui5-model-886e83b.md
index 1bf4dc4..23e99c5 100644
--- a/docs/adding-odata-service-and-new-sapui5-model-886e83b.md
+++ b/docs/adding-odata-service-and-new-sapui5-model-886e83b.md
@@ -2,13 +2,13 @@
 
 # Adding OData Service and New SAPUI5 Model
 
-This guide describes how to add OData service with the option to also add new SAPUI5 model.
+This guide describes how to add an OData service with the option to add a new SAPUI5 model.
 
 
 
 ## Context
 
-When adding a V2 OData service using annotations, it's necessary to add the new annotation data source. This requirement doesn't apply to V4 OData services
+When adding a OData V2 service using annotations, it's necessary to add the new annotation data source. This requirement doesn't apply to OData V4 services.
 
 
 
@@ -16,7 +16,7 @@ When adding a V2 OData service using annotations, it's necessary to add the new
 
 1.  Right click the `manifest.appdescr_variant` file of your adaptation project and select the *Adaptation Project* \> *Add OData Service And SAPUI5 Model*.
 
-2.  After the wizard starts enter the OData Service name for the service you want to add.
+2.  After the wizard starts, enter the OData Service name for the service you want to add.
 
 3.  Enter the OData Service URI.
 
@@ -24,9 +24,9 @@ When adding a V2 OData service using annotations, it's necessary to add the new
 
 5.  Enter the OData Service SAPUI5 Model name of the model you want to add.
 
-6.  \(Optional\) Enter settings for the OData Service SAPUI5 Model in the format of `"key1":"value1","key2":"value2", …`.
+6.  \(Optional\) Enter settings for the OData Service SAPUI5 Model in the format: `"key1":"value1","key2":"value2",`.
 
-7.  \(Optional\) Choose whether to add annotation or not.
+7.  \(Optional\) Choose whether to add an annotation.
 
     If you choose yes, provide the following information:
 
@@ -34,9 +34,9 @@ When adding a V2 OData service using annotations, it's necessary to add the new
 
     2.  Enter the OData Annotation Data Source URI.
 
-    3.  \(Optional\) Enter settings for the annotation in the format of `"key1":"value1","key2":"value2", …`.
+    3.  \(Optional\) Enter settings for the annotation in the format: `"key1":"value1","key2":"value2",`.
 
 
-8.  Choose *Finish* to create the change.
+8.  Click *Finish* to save your changes.
 
 
diff --git a/docs/adding-sapui5-component-usages-dd4b6e4.md b/docs/adding-sapui5-component-usages-dd4b6e4.md
index 729cbdf..abe3560 100644
--- a/docs/adding-sapui5-component-usages-dd4b6e4.md
+++ b/docs/adding-sapui5-component-usages-dd4b6e4.md
@@ -2,7 +2,7 @@
 
 # Adding SAPUI5 Component Usages
 
-In this guide you can find information how to add SAPUI5 component usages in your adaptation project without tooling support.
+In this guide you can find information on how to add SAPUI5 component usages in your adaptation project without tooling support.
 
 
 
@@ -10,7 +10,7 @@ In this guide you can find information how to add SAPUI5 component usages in you
 
 ## Context
 
-For more information on component usages, see Reuse Components section in the [Using and Nesting Components](https://sapui5.hana.ondemand.com/#/topic/346599f0890d4dfaaa11c6b4ffa96312).
+For more information on component usages, see the Reuse Components section in [Using and Nesting Components](https://sapui5.hana.ondemand.com/#/topic/346599f0890d4dfaaa11c6b4ffa96312).
 
 
 
@@ -24,14 +24,14 @@ For more information on component usages, see Reuse Components section in the [U
 
 3.  Enter the Component name.
 
-4.  Choose if you want to set it as lazy, or not.
+4.  Choose if you want to set it as lazy.
 
-5.  \(Optional\) Enter settings for the Component in the format of `"key1":"value1","key2":"value2", …`.
+5.  \(Optional\) Enter settings for the Component in the format: `"key1":"value1","key2":"value2",`.
 
-6.  \(Optional\) Enter any additional Component Data in the format of `key1":"value1","key2":"value2", …`.
+6.  \(Optional\) Enter any additional Component Data in the format: `key1":"value1","key2":"value2",`.
 
-7.  Choose if you want to add library reference. If yes, enter the library reference needed, and choose if you want to set it as lazy, or not.
+7.  Choose if you want to add library reference. If yes, enter the library reference needed and choose if you want to set it as lazy.
 
-8.  Choose *Finish* to create the change.
+8.  Click *Finish* to save your changes.
 
 
diff --git a/docs/adding-sapui5-component-usages-manually-12be091.md b/docs/adding-sapui5-component-usages-manually-12be091.md
index 200f7e9..64eee74 100644
--- a/docs/adding-sapui5-component-usages-manually-12be091.md
+++ b/docs/adding-sapui5-component-usages-manually-12be091.md
@@ -2,13 +2,15 @@
 
 # Adding SAPUI5 Component Usages Manually
 
+Learn how to add SAPUI5 component usages manually.
+
 
 
 <a name="loio12be0918c01e4f42b14d937db81994f4__context_ezk_2cc_4qb"/>
 
 ## Context
 
-For more information on component usages, see Reuse Components section in the [Using and Nesting Components](https://sapui5.hana.ondemand.com/#/topic/346599f0890d4dfaaa11c6b4ffa96312).
+For more information on component usages, see the Reuse Components section in [Using and Nesting Components](https://sapui5.hana.ondemand.com/#/topic/346599f0890d4dfaaa11c6b4ffa96312).
 
 
 
@@ -16,20 +18,20 @@ For more information on component usages, see Reuse Components section in the [U
 
 ## Procedure
 
-1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file an choose *Add*SAPUI5*Component Usages*.
+1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Add SAPUI5 Component Usages*.
 
-2.  After the wizard starts, enter the Component Usage ID you want to add.
+2.  After the wizard appears, enter the Component Usage ID you want to add.
 
 3.  Enter the Component name.
 
-4.  Choose if you want to set it as lazy, or not.
+4.  Choose if you want to set it as lazy.
 
-5.  \(Optional\) Enter settings for the Component in the format of `"key1":"value1","key2":"value2", …`.
+5.  \(Optional\) Enter settings for the Component in the format: `"key1":"value1","key2":"value2",`.
 
-6.  \(Optional\) Enter any additional Component Data in the format of `key1":"value1","key2":"value2", …`.
+6.  \(Optional\) Enter any additional Component Data in the format: `key1":"value1","key2":"value2",`.
 
-7.  Choose if you want to add library reference. If yes, enter the library reference needed, and choose if you want to set it as lazy, or not.
+7.  Choose if you want to add a library reference. If yes, enter the library reference, and choose if you want to set it as lazy.
 
-8.  Choose *Finish* to create the change.
+8.  Click *Finish* to save your changes.
 
 
diff --git a/docs/change-inbound-4ce1920.md b/docs/change-inbound-4ce1920.md
index 851c0cc..cde4511 100644
--- a/docs/change-inbound-4ce1920.md
+++ b/docs/change-inbound-4ce1920.md
@@ -2,7 +2,7 @@
 
 # Change Inbound
 
-This guide describes how to change the title and subtitle of existing intent for your adaptation project.
+This guide describes how to change the title and subtitle of an existing intent for your adaptation project.
 
 
 
@@ -14,8 +14,8 @@ This guide describes how to change the title and subtitle of existing intent for
 
 2.  Choose the *Inbound ID* which you would like to change.
 
-3.  Entert the title, subtitle and icon path that you would like to use.
+3.  Enter the title, subtitle and icon path that you would like to use.
 
-4.  Choose *Finish* to generate the project.
+4.  Click *Finish* to generate the project.
 
 
diff --git a/docs/check-consistency-of-release-state-1f91cd4.md b/docs/check-consistency-of-release-state-1f91cd4.md
index 23700ca..ad44fb2 100644
--- a/docs/check-consistency-of-release-state-1f91cd4.md
+++ b/docs/check-consistency-of-release-state-1f91cd4.md
@@ -2,20 +2,23 @@
 
 # Check Consistency of Release State
 
+Learn how to use the SAPUI5 Component Consistency ATC check to verfy the consistency of your release state.
 
 
-This section is only relevant for developers who release their apps to be consumed in adaptation projects in SAP S/4HANA Cloud and SAP BTP, Cloud Foundry environment.
+
+> ### Tip:  
+> This section is only relevant for developers who release their apps to be consumed in adaptation projects in SAP S/4HANA Cloud and SAP BTP, Cloud Foundry environment.
 
 Such apps need to be released with an `Extend (C0)` contract and must keep their OData services stable \(`Use System Internally (C1)` contract\). The release state of the app is also indicated in the app's `manifest.json` file, under `sap.fiori/cloudDevAdaptationStatus`.
 
-The ATC check *SAPUI5 Component Consistency* \(`CI_UI5_COMP`\) verifies the consistency of the release state. The following checks are performed:
+The ATC check, *SAPUI5 Component Consistency* \(`CI_UI5_COMP`\) verifies the consistency of the release state. The following checks are performed:
 
 -   Verify that the `sap.fiori/cloudDevAdaptationStatus` of the UI5 app in the SAPUI5 ABAP repository \(based on the BSP repository\) is the same as in the back-end system. This is relevant due to issues during the deployment or due to manual adjustments of the `manifest.json` file.
 
 -   Verify the consistency of release states of the UI5 app and the services it uses \(C0 and C1 contracts\).
 
 
-The ATC check `CI_UI5_COMP` also performs some other checks. For more information on these, see [ATC Check SAPUI5 Component Consistency](https://ui5.sap.com/#/topic/a71400bc82284449bb6c680a4516cc63).
+The ATC check, `CI_UI5_COMP` also performs some other checks. For more information, see [ATC Check SAPUI5 Component Consistency](https://ui5.sap.com/#/topic/a71400bc82284449bb6c680a4516cc63).
 
 For more information, see the following documentation:
 
diff --git a/docs/check-whether-your-adaptation-project-is-up-to-date-with-base-app-upgrades-c6ef105.md b/docs/check-whether-your-adaptation-project-is-up-to-date-with-base-app-upgrades-c6ef105.md
index f47a8b7..964462f 100644
--- a/docs/check-whether-your-adaptation-project-is-up-to-date-with-base-app-upgrades-c6ef105.md
+++ b/docs/check-whether-your-adaptation-project-is-up-to-date-with-base-app-upgrades-c6ef105.md
@@ -2,14 +2,14 @@
 
 # Check Whether Your Adaptation Project Is Up-To-Date with Base App Upgrades
 
-To ensure that your adaptation project is up-to-date, you need to check whether the adaptation project is still using the newest version of the base app. For this purpose the ATC check *Compare Used and Current Version of Base App* \(`UI5_BASE_APP_VERS`\) is available.
+To ensure that your adaptation project is up-to-date, you need to check whether the adaptation project is still using the newest version of the base app using the ATC check, *Compare Used and Current Version of Base App* \(`UI5_BASE_APP_VERS`\).
 
-Create an ATC check variant, and add the ATC check `UI5_BASE_APP_VERS` to it. For more information, see [Working with ATC Checks](https://help.sap.com/docs/SAP_S4HANA_CLOUD/25cf71e63940453397a32dc2b7676947/438842e71bfa4ff09443562f5ce2282d.html).
+Create an ATC check variant and add the ATC check, `UI5_BASE_APP_VERS` to it. For more information, see [Working with ATC Checks](https://help.sap.com/docs/SAP_S4HANA_CLOUD/25cf71e63940453397a32dc2b7676947/438842e71bfa4ff09443562f5ce2282d.html).
 
-To identify any adaptation project where the base app currently has a higher version than the version used in the adaptation project, you can run this check for your packages.
+To identify any adaptation project where the base app has a higher version than the version used in the adaptation project, run this check for your packages.
 
 > ### Note:  
-> SAP will provide fixes only for the latest version of the base application. Therefore it is necessary to upgrade adaptation projects whenever the base application is updated. To avoid any conflicts and ease the upgrade, follow the [Upgrade Safe Compatibility Rules](upgrade-safe-compatibility-rules-53706e2.md).
+> SAP will only provide fixes for the latest version of the base application. Therefore, it is necessary to upgrade adaptation projects whenever the base application is updated. To avoid any conflicts, follow the [Upgrade Safe Compatibility Rules](upgrade-safe-compatibility-rules-53706e2.md).
 
 To check if an adaptation project needs to be updated, you can use the *ABAP Test Cockpit* in the *ABAP Development Tools*. For more information, see [ATC Quality Checking](https://help.sap.com/docs/SAP_S4HANA_CLOUD/25cf71e63940453397a32dc2b7676947/4ec1a1126e391014adc9fffe4e204223.html) and [Checking Quality of ABAP Code with ATC](https://help.sap.com/docs/SAP_S4HANA_CLOUD/25cf71e63940453397a32dc2b7676947/4ec5711c6e391014adc9fffe4e204223.html).
 
@@ -46,11 +46,11 @@ For the used base app *<base app ID\>* a new version is available, please update
 To find out what changed in a base app provided by SAP S/4HANA Cloud, check the [What's New in SAP S/4HANA Cloud](https://help.sap.com/whats-new/7d3d11840a6543329e72391cf4d48e2d).
 
 > ### Tip:  
-> In the What's New Viewer, you can filter the *Category* column for *App*, and search the *Technical Objects Name* column for the SAP Fiori app ID of the base app, for example `F3331`.
+> In the What's New Viewer, you can filter the *Category* column for *App* and search the *Technical Objects Name* column for the SAP Fiori app ID of the base app. For example, `F3331`.
 
 To update the adaptation project, proceed as follows:
 
-1.  In SAP Business Application Studio, open *Visual Editor* and test and check that everything is still working with the new base version.
+1.  In SAP Business Application Studio, open *Visual Editor* and test that everything is still working with the new base version.
 
     *Visual Editor* automatically fetches the latest version of the base app.
 
@@ -71,7 +71,7 @@ The base app *<base app ID\>* was deleted, please check the successor app
 </td>
 <td valign="top">
 
-If you do not re-deploy your adaptation project, this will not affect anything. But we recommend that you create a new adaptation project based on the successor app.
+If you do not re-deploy your adaptation project, this will not affect anything. We recommend that you create a new adaptation project based on the successor app.
 
 </td>
 </tr>
diff --git a/docs/controller-extensions-ad7b4ae.md b/docs/controller-extensions-ad7b4ae.md
index 173b7d6..22ae04f 100644
--- a/docs/controller-extensions-ad7b4ae.md
+++ b/docs/controller-extensions-ad7b4ae.md
@@ -2,49 +2,51 @@
 
 # Controller Extensions
 
+Learn how to add a controller extension.
+
 
 
 <a name="loioad7b4ae4bc7249e4b9cc5625bc978ab9__context_jns_z13_tdb"/>
 
 ## Context
 
-Controller extensions allow you to enhance the functionality of a controller. You can create a controller extension specific to the view, for example, one controller extension for the list report view and one controller extension for the object page view. Additionally a controller extension can be delivered with an adaptation project and is dynamically added to an existing controller. Controller extensions that an adaptation project delivers are added to the reserved ".extension" namespace of the controller to avoid name clashes with existing functionality.
+Controller extensions allow you to enhance the functionality of a controller. You can create a controller extension specific to the view, for example, one controller extension for the list report view and one controller extension for the object page view. Additionally, a controller extension can be delivered with an adaptation project and is dynamically added to an existing controller. Controller extensions that an adaptation project delivers are added to the reserved `.extension` namespace of the controller to avoid name clashes with existing functionality.
 
-Controller extensions let the developer to add new methods and override methods. These override methods are optional callback methods that override, or are alled before or after the existing methods using a special override member. For more information on defining an extension, see [SAPUI5 Documentation](https://sapui5.hana.ondemand.com/#/topic/21515f09c0324218bb705b27407f5d61).
+Controller extensions allow you to add new methods and override methods. These override methods are optional callback methods that override, or are called before or after the existing methods using a special override member. For more information on defining an extension, see [SAPUI5 Documentation](https://sapui5.hana.ondemand.com/#/topic/21515f09c0324218bb705b27407f5d61).
 
 > ### Remember:  
-> You can add a controller extension only if:
+> You can only add a controller extension if:
 > 
 > -   You use an SAP Fiori elements-based application, or a freestyle SAPUI5 application.
-> -   You use application with asynchronous views.
+> -   You use an application with asynchronous views.
 
 
 
 ## Procedure
 
-1.  Right-click on the project main folder, the `webapp` folder, or the`manifest.appdescr_variant` file and choose *Preview Application*. Choose *start-editor*.
+1.  Right-click on the project main folder, the `webapp` folder, or the`manifest.appdescr_variant` file and click *Preview Application*. Click *start-editor*.
 
     The application opens in the canvas in UI Adaptation mode.
 
-2.  On the canvas, select a view or element in the view you want to extend and choose *Extend with Controller* from the project context menu.
+2.  On the canvas, select a view or element in the view you want to extend and click *Extend with Controller* from the project context menu.
 
-3.  In the dialog box that appears, provide a name for the controller extension.
+3.  In the dialog box, provide a name for the controller extension.
 
     The controller extension file \(`.js`\) is created in the folder, *Your project name* \> *webapp* \> *changes* \> *coding*. The `.js` file opens in the editor.
 
-    When you create a controller extension file, an associated **controllerExtension.change** file having reference to the `.js` file is created in the folder, *Your project name* \> *webapp* \> *changes*.
+    When you create a controller extension file, an associated `controllerExtension.change` file having reference to the `.js` file is created in the folder, *Your project name* \> *webapp* \> *changes*.
 
     For list report, object page, and over view page applications, in addition to the lifecycle methods, this `.js` file contains new methods that come from the templates provided by SAP Fiori elements. These methods can be used to override the base methods in the applications. For analytical list page applications, the `.js` file contains only the lifecycle methods. Reuse the methods to write extensions.
 
     > ### Note:  
-    > If you need to add your own separate custom business logic files, they have to be located in the folder `changes/coding`, the same folder that is used for the controller extension files. You should not create additional folders for such additional files on upper levels, because it will invalidate the project structure and you will not be able to deploy.
+    > If you need to add your own separate custom business logic files, they have to be located in the `changes/coding` folder. Do not create additional folders at higher levels because it will invalidate the project structure and you will not be able to deploy your application.
 
 4.  Define a method in the controller extension file for the new fragment or override any lifecycle methods in the override section. Save the file.
 
     The lifecycle methods are defined within the override section. Make sure that you define the new methods outside the override section.
 
-5.  To assign event handlers from .xml fragment to the controller extension, manually associate the methods with the respective fragments. In the .xml file for the fragment, prefix the method with <code>.extension.<i class="varname">&lt;controller extension namespace&gt;</i>.</code>, and save the file.
+5.  To assign event handlers from `.xml` fragment to the controller extension, manually associate the methods with the respective fragments. In the `.xml` file for the fragment, prefix the method with <code>.extension.<i class="varname">&lt;controller extension namespace&gt;</i>.</code>, and save the file.
 
-6.  In order to load the added change you need to reload the browser tab in which the adaptation project editor is opened. If you have opened Preview of the application in a separate browser tab, it also needs to be refreshed.
+6.  To load the added change, you need to reload the browser tab for the adaptation project editor and application preview \(if opened in a separate tab\).
 
 
diff --git a/docs/controller-extensions-f43630d.md b/docs/controller-extensions-f43630d.md
index 6ef66b3..0cef268 100644
--- a/docs/controller-extensions-f43630d.md
+++ b/docs/controller-extensions-f43630d.md
@@ -2,7 +2,7 @@
 
 # Controller Extensions
 
-Controller extensions allow you to add functionality to a fragment that you add to the SAPUI5 application. You can also override the functionality of the base methods inherited from the source application and lifecycle methods such as onInit, onBeforeRendering, onAfterRendering, and onExit.
+Controller extensions allow you to add functionality to a fragment that you add to the SAPUI5 application. You can also override the functionality of the base methods inherited from the source application and lifecycle methods such as `onInit`, `onBeforeRendering`, `onAfterRendering`, and `onExit`.
 
 
 
@@ -10,38 +10,38 @@ Controller extensions allow you to add functionality to a fragment that you add
 
 ## Context
 
-Controller extensions allow you to enhance the functionality of a controller. You can create a controller extension specific to the view, for example, one controller extension for the list report view and one controller extension for the object page view. Additionally a controller extension can be delivered with an adaptation project and is dynamically added to an existing controller. Controller extensions that an adaptation project delivers are added to the reserved ".extension" namespace of the controller to avoid name clashes with existing functionality.
+Controller extensions allow you to enhance the functionality of a controller. You can create a controller extension specific to the view, for example, one controller extension for the list report view and one controller extension for the object page view. Additionally, a controller extension can be delivered with an adaptation project and is dynamically added to an existing controller. Controller extensions that an adaptation project delivers are added to the reserved `.extension` namespace of the controller to avoid name clashes with existing functionality.
 
 Controller extensions let the developer add new methods and override methods. These override methods are optional callback methods that override the existing methods using a special override member. For more information on defining an extension, see [SAPUI5 Documentation](https://sapui5.hana.ondemand.com/#/topic/21515f09c0324218bb705b27407f5d61).
 
 > ### Remember:  
 > You can add a controller extension only if:
 > 
-> -   You use an SAP Fiori elements-based application, or a freestyle SAPUI5 application.
+> -   You use an SAP Fiori elements based application or a freestyle SAPUI5 application.
 > -   You use application with asynchronous views.
 
 
 
 ## Procedure
 
-1.  In your workspace expand the `webapp` folder and right click the `manifest.appdescr_variant` file and choose *Open SAPUI5 Visual Editor*.
+1.  In your workspace, expand the `webapp` folder, right click the `manifest.appdescr_variant` file and click *Open SAPUI5 Visual Editor*.
 
     The application opens in the canvas in preview mode.
 
-2.  From the Editor Header, select *Edit*.
+2.  From the Editor Header, click *Edit*.
 
-3.  On the canvas, select a view or element in the view you want to extend and choose *Extend with Controller* from the project context menu.
+3.  On the canvas, select a view or element in the view you want to extend and click *Extend with Controller* from the project context menu.
 
 4.  In the dialog box that appears, provide a name for the controller extension.
 
-    The controller extension file \(.js\) is created in the folder, *Your project name* \> *webapp* \> *changes* \> *coding*. The .js file opens in the editor.
+    The controller extension file \(`.js`\) is created in the folder, *Your project name* \> *webapp* \> *changes* \> *coding*. The `.js` file opens in the editor.
 
-    When you create a controller extension file, an associated **...codeExt.change** file having reference to the .js file is created in the folder, *Your project name* \> *webapp* \> *changes*.
+    When you create a controller extension file, an associated `...codeExt.change` file having reference to the `.js` file is created in the folder, *Your project name* \> *webapp* \> *changes*.
 
-    For list report, object page, and overview page applications, in addition to the lifecycle methods, this .js file contains new methods that come from the templates provided by Fiori elements. These methods can be used to override the base methods in the applications. For analytical list page applications, the `.js` file contains only the lifecycle methods. Reuse the methods to write extensions.
+    For list report, object page, and overview page applications, in addition to the lifecycle methods, this `.js` file contains new methods that come from the templates provided by Fiori elements. These methods can be used to override the base methods in the applications. For analytical list page applications, the `.js` file contains only the lifecycle methods. Reuse the methods to write extensions.
 
     > ### Note:  
-    > Have in mind that if you need to add your own separate custom business logic files, they have to be located in the folder `changes/coding`, the same folder that is used for the controller extension files. You should not create additional folders for such additional files on upper levels, because it will invalidate the project structure and you will not be able to deploy.
+    > If you need to add your own separate custom business logic files, they have to be located in the `changes/coding` folder. The same folder that is used for the controller extension files. Do not create additional folders for such additional files on upper levels, because it will invalidate the project structure and you will not be able to deploy your application.
 
 5.  Define a method in the controller extension file for the new fragment or override any lifecycle methods in the override section. Save the file.
 
@@ -51,7 +51,7 @@ Controller extensions let the developer add new methods and override methods. Th
 
 7.  Navigate to the canvas. You are prompted to reload the project for the controller changes to be applied.
 
-    A loading indicator appears with the message, *Loading SAPUI5 Visual Editor with Controller Extension changes*.
+    A loading indicator appears with the message: *Loading SAPUI5 Visual Editor with Controller Extension changes*.
 
 
 **Related Information**  
diff --git a/docs/create-control-variants-views-3dbd97f.md b/docs/create-control-variants-views-3dbd97f.md
index 853c477..86aae3e 100644
--- a/docs/create-control-variants-views-3dbd97f.md
+++ b/docs/create-control-variants-views-3dbd97f.md
@@ -2,6 +2,8 @@
 
 # Create Control Variants \(Views\)
 
+Learn how to use the Adaptation Editor to create, load, change, and save control variants.
+
 
 
 <a name="loio3dbd97f940564b11a8b7baf1e08aa88e__prereq_lg3_hty_hkb"/>
@@ -21,7 +23,7 @@
 
 ## Context
 
-The Adaptation Editor allows you to create, load, change, and save control variants. Typically, you would create variants of a control to give different options for the end user for better usability in special use cases when they might need \(or not\) a specific part of control.
+The Adaptation Editor allows you to create, load, change, and save control variants. You can create variants of a control to give different options for the end user for better usability in use cases when they do or do not need a specific part of a control.
 
 > ### Note:  
 > You can define variants for specific controls on the user interface. On the user interface, variants are called views.
@@ -32,5 +34,5 @@ The Adaptation Editor allows you to create, load, change, and save control varia
 
 ## Procedure
 
-Creating and adapting control variants \(views\) is the same process as the key user scenario. You can follow the procedure described in [Creating and Adapting Views](https://help.sap.com/viewer/4fc8d03390c342da8a60f8ee387bca1a/latest/en-US/91ae3492323b42a79ca66fbfaf5af3f9.html) . The only difference from the key user scenario is that you do not have to publish your changes. They are saved as an ordinary change in your adaptation project, in the same manner as all other changes.
+Creating and adapting control variants \(views\) is the same process as the key user scenario. You can follow the procedure described in [Creating and Adapting Views](https://help.sap.com/viewer/4fc8d03390c342da8a60f8ee387bca1a/latest/en-US/91ae3492323b42a79ca66fbfaf5af3f9.html). The only difference from the key user scenario is that you do not have to publish your changes. They are saved as an ordinary change in your adaptation project in the same manner as all other changes.
 
diff --git a/docs/create-control-variants-views-b4026b7.md b/docs/create-control-variants-views-b4026b7.md
index 662af80..07ec937 100644
--- a/docs/create-control-variants-views-b4026b7.md
+++ b/docs/create-control-variants-views-b4026b7.md
@@ -2,7 +2,7 @@
 
 # Create Control Variants \(Views\)
 
-As a developer you can create control variants within the SAPUI5 Visual Editor.
+As a developer, you can create control variants within the SAPUI5 Visual Editor.
 
 
 
@@ -21,10 +21,10 @@ As a developer you can create control variants within the SAPUI5 Visual Editor.
 
 ## Context
 
-The SAPUI5 Visual Editor allows you to create, load, change, and save control variants. Typically, you would create variants of a control to give different options for the end user for better usability in special use cases when they might need \(or not\) a specific part of control.
+The SAPUI5 Visual Editor allows you to create, load, change, and save control variants. You can create variants of a control to give different options for the end user for better usability in special use cases when they do or do not need a specific part of control.
 
 > ### Note:  
-> You can define variants for specific controls on the user interface. Have in mind that variants are also called "views", usually in a more nontechnical context, for example, on the user interface.
+> You can define variants for specific controls on the user interface. Have in mind that variants are also called "views" in a more non-technical context, for example, on the user interface.
 
 
 
@@ -32,5 +32,5 @@ The SAPUI5 Visual Editor allows you to create, load, change, and save control va
 
 ## Procedure
 
-Creating and adapting control variants \(views\) is done the same way, as in the key user scenario. You can follow the procedure described in [Creating and Adapting Views](https://help.sap.com/viewer/4fc8d03390c342da8a60f8ee387bca1a/latest/en-US/91ae3492323b42a79ca66fbfaf5af3f9.html) . The only difference from the key user scenario is that you do not have to publish your changes. They are saved as an ordinary change in your adaptation project, in the same manner as all other changes.
+Creating and adapting control variants \(views\) is done the same way, as in the key user scenario. You can follow the procedure described in [Creating and Adapting Views](https://help.sap.com/viewer/4fc8d03390c342da8a60f8ee387bca1a/latest/en-US/91ae3492323b42a79ca66fbfaf5af3f9.html). The only difference from the key user scenario is that you do not have to publish your changes. They are saved as an ordinary change in your adaptation project in the same manner as all other changes.
 
diff --git a/docs/create-the-adaptation-project-d6ab261.md b/docs/create-the-adaptation-project-d6ab261.md
index 4e3fb15..8beab7d 100644
--- a/docs/create-the-adaptation-project-d6ab261.md
+++ b/docs/create-the-adaptation-project-d6ab261.md
@@ -2,7 +2,7 @@
 
 # Create the Adaptation Project
 
-Create an adaptation project from existing SAP Fiori elements, or freestyle SAPUI5 applications in SAP S/4HANA Cloud Public Edition.
+Create an adaptation project from existing SAP Fiori elements or freestyle SAPUI5 applications in SAP S/4HANA Cloud Public Edition.
 
 
 
@@ -10,11 +10,11 @@ Create an adaptation project from existing SAP Fiori elements, or freestyle SAPU
 
 ## Procedure
 
-1.  Open your instance of VS Code, then start and open the dev space that you want to use. The dev space needs to either have *SAPUI5 Adaptation Project* as a predefined extension, or it has to be chosen manually as an extension for the dev space during its creation.
+1.  Open Visual Studio Code \(VS Code\) and start and open the dev space that you want to use. The dev space must have *SAPUI5 Adaptation Project* as a predefined extension or it has been chosen manually as an extension for the dev space during creation.
 
-2.  Choose *File* \> *Open Folder...*. Select the *projects* folder and click *OK*.
+2.  Click *File* \> *Open Folder...*. Select the *projects* folder and click *OK*.
 
-3.  To start the Yeoman generator, choose *View* \> *Command Palette*. In the command palette, enter **`Open Template Wizard`** and select the wizard from the list. After the generator loads, choose the *Adaptation Project* tile and select *Start*.
+3.  To start the Yeoman generator, click *View* \> *Command Palette*. In the Command Palette, enter `Open Template Wizard` and select the wizard from the list. After the generator loads, click the *Adaptation Project* tile and click *Start*.
 
 4.  Use the wizard to configure the project information.
 
@@ -22,23 +22,23 @@ Create an adaptation project from existing SAP Fiori elements, or freestyle SAPU
 
     2.  Enter a name for the project and a title for the application. The project name has to be unique in the system.
 
-    3.  The *Namespace* field always starts with **`customer.`**. Enter the name of your project after **`customer.`**. Choose *Next*.
+    3.  The *Namespace* field always starts with `customer.`. Enter the name of your project after `customer.`. Click *Next*.
 
     4.  Select a system.
 
-    5.  \(Optional\) If required enter your username and password for the system and select *Login* from inside the password field. Basic authentication is supported.
+    5.  \(Optional\) If required, enter your username and password for the system and click *Login* from inside the password field. Basic authentication is supported.
 
     6.  The system type will be automatically detected, being *CloudReady*.
 
-    7.  Choose the application that you want to work with. Have in mind that only applications extensible in adaptation projects will be shown in the list.
+    7.  Choose the application that you want to work with. Only applications extensible in adaptation projects will be shown in the list.
 
-    8.  You can choose if you want to use the adaptation project in Safe Mode or not. Safe Mode provides less freestyle capabilities, but allows your project to stay fully compatible with future upgrades of the source application. You will be able to switch off the Safe Mode afterwards.
+    8.  You can choose if you want to use the adaptation project in Safe Mode. Safe Mode provides less freestyle capabilities but allows your project to stay fully compatible with future upgrades of the source application. You can switch off Safe Mode afterwards.
 
-    9.  Choose *Next*.
+    9.  Click *Next*.
 
-    10. If the base app has an navigation intent specified in its manifest you can choose it. If not you need to enter semantic object, action, and parameters.
+    10. If the base app has an navigation intent specified in its manifest, you can choose it. If not, you need to enter semantic object, action, and parameters.
 
-    11. Enter the title and the subtitle \(optional\) for the new tile and press *Next*.
+    11. Enter the title and the subtitle \(optional\) for the new tile and click *Next*.
 
     12. Enter the SAPUI5 ABAP repository you want to use for your deployment.
 
@@ -46,13 +46,13 @@ Create an adaptation project from existing SAP Fiori elements, or freestyle SAPU
 
     14. Enter the package you want to use for your deployment.
 
-    15. \(Optional\) If needed you will be asked to enter a transport request number.
+    15. \(Optional\) If needed, you will be asked to enter a transport request number.
 
-    16. Choose *Finish* and wait until your project gets generated, you will be notified about it.
+    16. Click *Finish*.
 
 
-5.  A notification message appears, that the project has been generated and will be saved for future use.
+5.  A notification message appears that the project has been generated and will be saved for future use.
 
-6.  You can now preview the adaptation project. See [Preview the Adaptation Project](preview-the-adaptation-project-64cc15b.md). You can also continue developing. See [Make Adaptations](make-adaptations-6d2cfea.md).
+6.  You can now preview the adaptation project. For more information, see [Preview the Adaptation Project](preview-the-adaptation-project-64cc15b.md). You can also continue developing. For more information, see [Make Adaptations](make-adaptations-6d2cfea.md).
 
 
diff --git a/docs/creating-the-project-072f566.md b/docs/creating-the-project-072f566.md
index b839504..cb11f2d 100644
--- a/docs/creating-the-project-072f566.md
+++ b/docs/creating-the-project-072f566.md
@@ -44,5 +44,3 @@ Create an adaptation project in an on-premise system.
 
 Your adaption project has been generated. To preview your adaption project, see [Previewing the Adaptation Project](previewing-the-adaptation-project-8701335.md). To continue development, see [Making Adaptations](making-adaptations-2a076dd.md) and [Create New SAPUI5 Extensions](https://help.sap.com/docs/bas/developing-sap-fiori-app-in-sap-business-application-studio/create-new-sapui5-extensions?locale=en-US).
 
-.
-
diff --git a/docs/css/SAP-icons-V5.woff b/docs/css/SAP-icons-V5.woff
index b629610..fd12965 100644
Binary files a/docs/css/SAP-icons-V5.woff and b/docs/css/SAP-icons-V5.woff differ
diff --git a/docs/css/SAP-icons.woff b/docs/css/SAP-icons.woff
index b565344..fd12965 100644
Binary files a/docs/css/SAP-icons.woff and b/docs/css/SAP-icons.woff differ
diff --git a/docs/delete-the-adaptation-project-3db6190.md b/docs/delete-the-adaptation-project-3db6190.md
index 560acc6..794b442 100644
--- a/docs/delete-the-adaptation-project-3db6190.md
+++ b/docs/delete-the-adaptation-project-3db6190.md
@@ -2,7 +2,7 @@
 
 # Delete the Adaptation Project
 
-If you no longer need an app variant that you created via an adaptation project, you can delete it from the back-end system as described here.
+If you no longer need an app variant that you have created using an adaptation project, you can delete it from the back-end system.
 
 
 
@@ -24,8 +24,8 @@ You can delete the adaptation project using the Command Line Interface \(CLI\).
 
 ## Procedure
 
-1.  Open SAP Business Application studio main menu and choose *Terminal* / *New terminal*.
+1.  Open SAP Business Application Studio main menu and choose *Terminal* \> *New terminal*.
 
-2.  Then you can use the following command: `npm run undeploy`.
+2.  Then, you use the following command: `npm run undeploy`.
 
 
diff --git a/docs/deleting-the-adaptation-project-458f1f3.md b/docs/deleting-the-adaptation-project-458f1f3.md
index 5f0fa4c..b501cef 100644
--- a/docs/deleting-the-adaptation-project-458f1f3.md
+++ b/docs/deleting-the-adaptation-project-458f1f3.md
@@ -2,6 +2,8 @@
 
 # Deleting the Adaptation Project
 
+Learn how to delete an adaptation project.
+
 
 
 <a name="loio458f1f3280a04df3805849f1c29ac5c5__context_yzq_v4p_qlb"/>
@@ -9,9 +11,9 @@
 ## Context
 
 > ### Caution:  
-> If a key user has created further app variants based on the app variant you just deleted, these key user app variants will be deleted, as well.
+> If a key user has created app variants based on the app variant you have just deleted, these will also be deleted.
 
-There are three options – using the tool you have already used for deployment, using the Command Line Interface \(CLI\), or using an ABAP report.
+There are three methods to delete an adaptation project: using the deployment tool, using the Command Line Interface \(CLI\), or using an ABAP report.
 
 <a name="task_ubv_13p_wtb"/>
 
@@ -25,9 +27,9 @@ There are three options – using the tool you have already used for deployment,
 
 ## Prerequisites
 
-You have deployed an app variant, which you created via an adaptation project, to your ABAP system.
+You have deployed an app variant, which have you created using an adaptation project, to your ABAP system.
 
-In order to be able to delete any deployed adaptation project you should have the role `SAP_UI_FLEX_DEVELOPER` assigned.
+You have the `SAP_UI_FLEX_DEVELOPER` role assigned.
 
 
 
@@ -35,11 +37,11 @@ In order to be able to delete any deployed adaptation project you should have th
 
 ## Procedure
 
-1.  Right-click on main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and select *Open Deployment Wizard*.
+1.  Right-click on the main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Open Deployment Wizard*.
 
-2.  Choose the system you want to undeploy the project from. Have in mind that the one you have used to create the project will be selected by default. Select *Next* to continue.
+2.  Choose the system you want to undeploy the project from. The system you have used to create the project will be selected by default. Click *Next* to continue.
 
-3.  Choose *Undeploy* and select *Finish* to start the undeployment.
+3.  Click *Undeploy* and click *Finish* to start the undeployment.
 
 
 <a name="task_ecy_r3p_wtb"/>
@@ -54,9 +56,9 @@ In order to be able to delete any deployed adaptation project you should have th
 
 ## Prerequisites
 
-You have deployed an app variant, which you created via an adaptation project, to your ABAP system.
+You have deployed an app variant, which you created using an adaptation project, to your ABAP system.
 
-Тhe minimum required version of the software component to have this report is SAP\_UI 7.55.
+Тhe minimum required version of the software component is `SAP_UI 7.55`.
 
 
 
@@ -64,18 +66,24 @@ You have deployed an app variant, which you created via an adaptation project, t
 
 ## Procedure
 
-1.  In your project folder, open the `manifest.appdescr_variant` file in your adaptation project and copy the value of the id element.
+1.  In your project folder, open the `manifest.appdescr_variant` file in your adaptation project and copy the value of the `id` element.
 
-2.  In the respective back-end system, start transaction SE38 and execute report `/UI5/DEL_ADAPTATION_PROJECT`.
+2.  In the back-end system, start transaction `SE38` and execute report `/UI5/DEL_ADAPTATION_PROJECT`.
 
-3.  Paste the copied ID of the app variant that you want to delete, or use the F4 help to find it.
+3.  Paste the copied `ID` of the app variant that you want to delete or use the [F4\] help to find it.
 
-4.  Choose *Execute* \(F8\).
+4.  Click *Execute* \([F8\]\).
 
 5.  If prompted, select or create a transport request.
 
-6.  In the overview of the files that will be deleted, choose *Execute* \(Shift+F1\) again.
+6.  In the overview of the files that will be deleted, click *Execute* \([Shift\] + [F1\]  \) again.
+
+
+
+
+<a name="task_ecy_r3p_wtb__result_pkn_srb_fdc"/>
 
-7.  The app variant is deleted from all systems as soon as you release the transport request.
+## Results
 
+The app variant is deleted from all systems as soon as you release the transport request.
 
diff --git a/docs/deploy-or-update-the-adaptation-project-to-the-abap-repository-32c901d.md b/docs/deploy-or-update-the-adaptation-project-to-the-abap-repository-32c901d.md
index d75786f..c86a4c5 100644
--- a/docs/deploy-or-update-the-adaptation-project-to-the-abap-repository-32c901d.md
+++ b/docs/deploy-or-update-the-adaptation-project-to-the-abap-repository-32c901d.md
@@ -2,7 +2,7 @@
 
 # Deploy or Update the Adaptation Project to the ABAP Repository
 
-Deploy or update the app variant to the SAPUI5 ABAP repository in S/4HANA Cloud, or SAP BTP system .
+Deploy or update the app variant to the SAPUI5 ABAP repository in SAP S/4HANA Cloud or SAP Business Technology Platform \(SAP BTP\) system.
 
 <a name="task_a5r_yym_vvb"/>
 
@@ -15,7 +15,7 @@ Deploy or update the app variant to the SAPUI5 ABAP repository in S/4HANA Cloud,
 ## Context
 
 > ### Note:  
-> Please keep your builder up-to-date by calling `npm update` and redeploy your adaptation project, to ensure that there is no direct impact to deployed adaptation project after an upgrade.
+> Please keep your builder up-to-date by calling `npm update` and redeploy your adaptation project to ensure that there is no impact to the deployed adaptation project after an upgrade.
 
 
 
@@ -23,11 +23,11 @@ Deploy or update the app variant to the SAPUI5 ABAP repository in S/4HANA Cloud,
 
 ## Procedure
 
-1.  Open SAP Business Application studio main menu and choose *Terminal* / *New terminal*.
+1.  Open SAP Business Application Studio main menu and choose *Terminal* \> *New terminal* .
 
     > ### Note:  
-    > When you open the terminal make sure that you are working in the correct folder. If needed navigate to your project main folder.
+    > When you open the terminal, ensure that you are working in the main project folder.
 
-2.  Then use the following command for deployment/update: `npm run deploy`.
+2.  Then, use the following command for to deploy or update your deployment: `npm run deploy`.
 
 
diff --git a/docs/deploying-the-adaptation-project-to-the-abap-repository-febf0d9.md b/docs/deploying-the-adaptation-project-to-the-abap-repository-febf0d9.md
index d870849..e7a24b3 100644
--- a/docs/deploying-the-adaptation-project-to-the-abap-repository-febf0d9.md
+++ b/docs/deploying-the-adaptation-project-to-the-abap-repository-febf0d9.md
@@ -2,17 +2,22 @@
 
 # Deploying the Adaptation Project to the ABAP Repository
 
+Learn how to deploy an adaptation project to the ABAP repository.
 
 
-<a name="loiofebf0d9e3266451b8fc751ed25736ce1__prereq_spv_ccq_jpb"/>
+
+<a name="loiofebf0d9e3266451b8fc751ed25736ce1__prereq_zmv_gz1_fdc"/>
 
 ## Prerequisites
 
-This prerequisite is only valid for on premise customer developers who deploy their adaptation projects to SAP NW AS ABAP. In order to deploy, your user should be assigned to the role `SAP_UI_FLEX_DEVELOPER`, if SAP\_UI version is 7.55 and above, or to the role `S_DEVELOP`, if SAP\_UI version is below 7.55. Also, if a cloud connector is in use, `POST` and `PUT` requests should be allowed for this path: `/sap/bc/lrep/dta_folder/`.
+> ### Note:  
+> This prerequisite is only valid for on-premise developers who deploy their adaptation projects to SAP NW AS ABAP.
+
+If the `SAP_UI` version is 7.55 or above, your user must have the `SAP_UI_FLEX_DEVELOPER` role assigned. If the `SAP_UI` version is below 7.55, your user must have the `S_DEVELOP` role assigned. If you use a cloud connector, `POST` and `PUT` requests must be allowed for the path: `/sap/bc/lrep/dta_folder/`.
 
 
 
-<a name="loiofebf0d9e3266451b8fc751ed25736ce1__context_zbx_nmv_zjb"/>
+<a name="loiofebf0d9e3266451b8fc751ed25736ce1__context_anv_gz1_fdc"/>
 
 ## Context
 
@@ -20,25 +25,27 @@ After you have created the app variant, you deploy it to your ABAP system. Since
 
 
 
+<a name="loiofebf0d9e3266451b8fc751ed25736ce1__steps_bnv_gz1_fdc"/>
+
 ## Procedure
 
-1.  Right-click the main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and select Open Deployment Wizard
+1.  Right-click the main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Open Deployment Wizard*.
 
-2.  Choose the system you want to use to deploy the project. Have in mind that the one you have used to create the project will be selected by default. Select *Next* to continue.
+2.  Choose the system you want to use to deploy the project. The system you have used to create the project will be selected by default. Click *Next* to continue.
 
-3.  This step depends on if you have previously deployed this project to the selected system or not:
+3.  Depending on whether you have previously deployed this project to the selected system, perform the following steps:
 
-    -   If you haven’t previously deployed this project to the selected system, you need to enter the package to be used for the deployment. If the package entered does not require transport request number, choose *Finish*. If needed by the package, enter the transport request number on the next page. Choose *Finish*.
+    -   If you have not previously deployed this project to the selected system, you need to enter the package to be used for the deployment. If the package entered does not require a transport request number, click *Finish*. If the package does require a transport request number, enter the transport request number on the next page. Click *Finish*.
 
-    -   If you have deployed this project to the system, you need to choose the type of operation you want to perform. Choose *Update* and then select *Finish* to start the process of deployment.
+    -   If you have deployed this project to the system, you need to choose the type of operation you want to perform. Click *Update* and then click *Finish* to start the deployment process.
 
 
-4.  You will be notified if the deployment process is successful, or there was some kind of an error.
+4.  You will be notified if the deployment process is successful or if there was an error.
 
     The UI changes you made in the adaptation project are applied to the layered repository in the selected SAP NetWeaver Application Server ABAP for your application. To add the new app variant to the SAP Fiori launchpad, you need to configure target mappings in the SAP Fiori launchpad designer. For more information, see [Configuring Target Mappings](https://help.sap.com/docs/ABAP_PLATFORM_NEW/a7b390faab1140c087b8926571e942b7/33daedef95454af68903ef1238aa0373.html?version=latest).
 
-    In case of error "ZIP archive contains disallowed files or has an incorrect structure", refer to SAP Note[3073188](https://me.sap.com/notes/3073188).
+    If the error "ZIP archive contains disallowed files or has an incorrect structure" occurs, refer to SAP Note [3073188](https://me.sap.com/notes/3073188).
 
-    In case of error “500 Internal server error” or “Transport check could not be performed”, refer to SAP Note [3243791](https://me.sap.com/notes/3243791).
+    If the error "500 Internal server error" or "Transport check could not be performed" occurs, refer to SAP Note [3243791](https://me.sap.com/notes/3243791).
 
 
diff --git a/docs/extending-an-sap-fiori-application-for-an-on-premise-system-802f01c.md b/docs/extending-an-sap-fiori-application-for-an-on-premise-system-802f01c.md
index 0788c68..954042f 100644
--- a/docs/extending-an-sap-fiori-application-for-an-on-premise-system-802f01c.md
+++ b/docs/extending-an-sap-fiori-application-for-an-on-premise-system-802f01c.md
@@ -35,13 +35,13 @@ You can create an adaptation project forapplications that meet the following req
 -   The application is not a scaffolding application \(an application that uses `sap.ca.scfld.md` in its `manifest.json` file\).
 
 > ### Note:  
-> Adaptation project can also be used as a basis, but only when it is SAP or partner provided and with the following conditions:
+> Adaptation projects can also be used as a basis but only when it is SAP or partner provided and with the following conditions:
 > 
 > -   If the selected system has a SAPUI5 version lower than 1.96, you need to implement [3223667](https://me.sap.com/notes/3223667) on your system.
 > -   If the selected system has a SAPUI5 version lower than 1.90, it does not support an adaptation project as а base for a new adaptation project. You need to update the SAPUI5 version for the project to work after deployment.
 
 > ### Note:  
-> Adaptation project does not support as a basis:
+> Adaptation projects doe not support as a basis:
 > 
 > -   An application that requires a mandatory parameter to start.
 > -   An application variant that has already been deployed with an adaptation project.
@@ -69,9 +69,9 @@ A typical workflow for extending an SAP Fiori application includes the following
 
 ## Things to Consider
 
-You cannot deploy and use cannot deploy an adaptation project with a package that is enabled for ABAP for Cloud Development. You will be able to create an adaptation project and use its Adaptation Editor but you won't be able to deploy it. For more information, see [**Developer Extensibility**](https://help.sap.com/docs/ABAP_PLATFORM_NEW/b5670aaaa2364a29935f40b16499972d/155909e3569941e08831c78cf4c2d495.html).
+You cannot deploy and use an adaptation project with a package that is enabled for ABAP for Cloud Development. You will be able to create an adaptation project and use its Adaptation Editor but you won't be able to deploy it. For more information, see [**Developer Extensibility**](https://help.sap.com/docs/ABAP_PLATFORM_NEW/b5670aaaa2364a29935f40b16499972d/155909e3569941e08831c78cf4c2d495.html).
 
 
 
-An adaptation project runs the preview of its applications in the Adaptation Editor and in a separate browser tab preview, both of which are sandbox-like environments and not within SAP Fiori launchpad. Therefore, features that depend on SAP Fiori launchpad may not function as expected \(for example, navigation between different applications\) when previewing the application during development, but will work after deployment and in SAP Fiori launchpad.
+An adaptation project runs the preview of its applications in the Adaptation Editor and in a separate browser tab preview, both of which are sandbox-like environments and not within SAP Fiori launchpad. Therefore, features that depend on SAP Fiori launchpad may not function as expected \(for example, navigation between different applications\) when previewing the application during development but will work after deployment and in SAP Fiori launchpad.
 
diff --git a/docs/extending-an-sap-fiori-application-for-s-4hana-cloud-public-edition-and-sap-btp-abap-envi-f4881a9.md b/docs/extending-an-sap-fiori-application-for-s-4hana-cloud-public-edition-and-sap-btp-abap-envi-f4881a9.md
index e1b4bd1..a427155 100644
--- a/docs/extending-an-sap-fiori-application-for-s-4hana-cloud-public-edition-and-sap-btp-abap-envi-f4881a9.md
+++ b/docs/extending-an-sap-fiori-application-for-s-4hana-cloud-public-edition-and-sap-btp-abap-envi-f4881a9.md
@@ -2,7 +2,7 @@
 
 # Extending an SAP Fiori Application for S/4HANA Cloud Public Edition and SAP BTP, ABAP Environment
 
-You can use SAPUI5 Adaptation Project to extend SAP Fiori elements, or freestyle SAPUI5 applications with an application variant.
+You can use a SAPUI5 Adaptation Project to extend SAP Fiori elements or freestyle SAPUI5 applications with an application variant.
 
 
 
@@ -10,7 +10,7 @@ You can use SAPUI5 Adaptation Project to extend SAP Fiori elements, or freestyle
 
 ## Overview
 
-You can extend SAPUI5 applications in SAP S/4HANA Cloud Public Edition and SAP BTP, ABAP Environment with an application variant, without changing the original application.
+You can extend SAPUI5 applications in SAP S/4HANA Cloud Public Edition and SAP BTP, ABAP Environment with an application variant without changing the original application.
 
 
 
@@ -18,12 +18,12 @@ You can extend SAPUI5 applications in SAP S/4HANA Cloud Public Edition and SAP B
 
 ## Prerequisites
 
--   SAP S/4HANA Cloud only: To determine, if the application can be extended using the adaptation project, see [SAP Fiori Apps Reference Library](https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/homePage) and check the application’s implementation information under Extensibility \(extensibility of the SAPUI5 application in the front-end server\).
+-   SAP S/4HANA Cloud only: To determine if the application can be extended using the adaptation project, see [SAP Fiori Apps Reference Library](https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/homePage) and check the application’s implementation information under Extensibility \(extensibility of the SAPUI5 application in the front-end server\).
 
--   SAP S/4HANA Cloud only: If the SAP-delivered application you want to extend with an adaptation project is not yet supported, please submit a request here: [Influence Opportunity Homepage - Customer Influence](https://influence.sap.com/sap/ino/#/campaign/1177).
--   SAP S/4HANA Cloud only: Since a developer tenant is required, this feature is only available with 3 system landscape. For more information, see [System Landscapes in SAP S/4HANA Cloud](https://help.sap.com/docs/SAP_S4HANA_CLOUD/a630d57fc5004c6383e7a81efee7a8bb/aa60b129af7b4ce8ae052618c8315d29.html).
+-   SAP S/4HANA Cloud only: If the SAP delivered application you want to extend with an adaptation project is not supported, please submit a request here: [Influence Opportunity Homepage - Customer Influence](https://influence.sap.com/sap/ino/#/campaign/1177).
+-   SAP S/4HANA Cloud only: Since a developer tenant is required, this feature is only available with a 3 system landscape. For more information, see [System Landscapes in SAP S/4HANA Cloud](https://help.sap.com/docs/SAP_S4HANA_CLOUD/a630d57fc5004c6383e7a81efee7a8bb/aa60b129af7b4ce8ae052618c8315d29.html).
 -   [Releasing an SAP Fiori Application to Be Extensible in Adaptation Projects on SAP S/4HANA Cloud and SAP BTP, ABAP Environment](releasing-an-sap-fiori-application-to-be-extensible-in-adaptation-projects-on-sap-s-4hana-1046206.md).
--   A destination for the development tenant exists. See, [Create a Destination to Connect to SAP Business Application Studio](https://help.sap.com/docs/SAP_S4HANA_CLOUD/6aa39f1ac05441e5a23f484f31e477e7/0af2819bbe064a3da455753c8518dd81.html).
+-   A destination for the development tenant exists. For more information, see [Create a Destination to Connect to SAP Business Application Studio](https://help.sap.com/docs/SAP_S4HANA_CLOUD/6aa39f1ac05441e5a23f484f31e477e7/0af2819bbe064a3da455753c8518dd81.html).
 -   The developer requires the following business catalogs: The application that will be adapted must be released for extensibility via adaptation projects. For more information, see
     -   Development - UI Deployment \(SAP\_A4C\_BC\_DEV\_UID\_PC\)
     -   Business catalog to retrieve the list of extensible apps \(for example SAP\_A4C\_BC\_DEV\_OBJ\_DIS\_PC\)
@@ -40,7 +40,7 @@ The following diagram shows the relationship between the source application \(sh
 ![](images/AdaptationProjectS4HCarchitecture_f84e21c.png)
 
 > ### Note:  
-> The application that will be adapted must be released for extensibility via adaptation. Have in mind that you can use source control, such as Git, to maintain your project source code.
+> The application that will be adapted must be released for extensibility using adaptation. You can use source control, such as Git, to maintain your project source code.
 > 
 > You must use the project source code to preview and modify it. For more information, see [Git Source Control](https://help.sap.com/docs/bas/sap-business-application-studio/git-source-control).
 
diff --git a/docs/generating-an-application-with-joule-using-sap-fiori-tools-6845fed.md b/docs/generating-an-application-with-joule-using-sap-fiori-tools-6845fed.md
index 367661d..fa5f776 100644
--- a/docs/generating-an-application-with-joule-using-sap-fiori-tools-6845fed.md
+++ b/docs/generating-an-application-with-joule-using-sap-fiori-tools-6845fed.md
@@ -51,6 +51,9 @@ Ensure the following prerequisites are met:
 
 2.  Prepare your business requirements document for generating a new application. To get started, see [Example 1: Manage Contracts and Customer Information in the System](example-1-manage-contracts-and-customer-information-in-the-system-c1bccf2.md) and [Example 2: Display Customers with Related Contracts](example-2-display-customers-with-related-contracts-a6c978f.md).
 
+    > ### Caution:  
+    > SAP Fiori tools does not filter personal or sensitive data. Therefore, you should not share personal or sensitive data in your business requirements document.
+
 3.  Paste your business requirements document following the pattern provided in the examples. We recommend that you use English to achieve the best results.
 
     > ### Note:  
diff --git a/docs/index.md b/docs/index.md
index b0d8b91..1a824f4 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -22,7 +22,7 @@ Last Updated: May 2023
     -   [Report Issues and Security](Getting-Started-with-SAP-Fiori-Tools/report-issues-and-security-7c755a5.md)
 -   [Project Functions](Project-Functions/project-functions-0d8fa32.md)
     -   [Application Information](Project-Functions/application-information-c3e0989.md)
-    -   [Application Minimum SAPUI5 Version](Project-Functions/application-minimum-sapui5-version-009f43e.md)
+    -   [Application SAPUI5 Version](Project-Functions/application-sapui5-version-009f43e.md)
     -   [Data Editor](Project-Functions/data-editor-18e43b5.md)
     -   [Deleting an Application in CAP Project](Project-Functions/deleting-an-application-in-cap-project-709f838.md)
     -   [Environment Check](Project-Functions/environment-check-75390cf.md)
diff --git a/docs/internationalization-a789703.md b/docs/internationalization-a789703.md
index 943ffd5..47420d1 100644
--- a/docs/internationalization-a789703.md
+++ b/docs/internationalization-a789703.md
@@ -2,17 +2,17 @@
 
 # Internationalization
 
-Adaptation project supports internationalization \(i18n\), which enables you to provide easily translatable text for applications. The topic describes the ways in which you provide text for internationalization. You can define i18n key-value pairs and change the value for existing i18n keys.
+Adaptation projects support internationalization \(i18n\) which enables you to provide easily translatable text for applications. This topic describes the ways in which you can provide text for internationalization. You can define i18n key-value pairs and change the value for existing i18n keys.
 
 **Context**
 
-Internationalization refers to the process of designing and developing a software application and its content so that it can be adapted to multiple languages without making much engineering changes.
+Internationalization is the process of designing and developing a software application so that it can be adapted to multiple languages without making major engineering changes.
 
-When you create an Adaptation project, an *i18n.properties* file is created for every page of the application. Define a key-value pair in the *i18n.properties* file that you can refer to while providing text for the UI controls.
+When you create an adaptation project, an `i18n.properties` file is created for every page of the application. Define a key-value pair in the `i18n.properties` file to refer to when providing text for the UI controls.
 
 **Folder Structure**
 
-In your workspace, under the Adaptation project, the folder structure looks like:
+In your workspace, under the adaptation project, the folder structure is:
 
 -   Project name
 
@@ -42,5 +42,5 @@ In your workspace, under the Adaptation project, the folder structure looks like
 
 **Define Key-Value Pair**
 
-Define your key-value pairs in the *i18n.properties*. Refer to the keys while you edit the project using Adaptation Editor. In the *Properties* pane, refer to the i18n key for a SAPUI5 control instead of typing-in the text. Run the project as a web application and check whether the i18n value associated to the key appears on the UI control. Similarly, you can change the text of existing UI controls by overriding the associated i18n key-value pairs in the source application.
+Define your key-value pairs in the `i18n.properties` file. Refer to the keys while you edit the project using the Adaptation Editor. In the *Properties* pane, refer to the i18n key for a SAPUI5 control instead of typing in the text. Run the project as a web application and check whether the i18n value associated to the key appears on the UI control. You can also change the text of existing UI controls by overriding the associated i18n key-value pairs in the source application.
 
diff --git a/docs/internationalization-f6d1972.md b/docs/internationalization-f6d1972.md
index 84f959f..1dd3013 100644
--- a/docs/internationalization-f6d1972.md
+++ b/docs/internationalization-f6d1972.md
@@ -2,17 +2,17 @@
 
 # Internationalization
 
-Adaptation project supports internationalization \(i18n\), which enables you to provide easily translatable text for applications. The topic describes the ways in which you provide text for internationalization. You can define i18n key-value pairs and change the value for existing i18n keys.
+Adaptation projects support internationalization \(i18n\) which enables you to provide easily translatable text for applications. This topic describes the ways in which you can provide text for internationalization. You can define i18n key-value pairs and change the value for existing i18n keys.
 
 **Context**
 
-Internationalization refers to the process of designing and developing a software application and its content so that it can be adapted to multiple languages without making much engineering changes.
+Internationalization refers to the process of designing and developing a software application and its content so that it can be easily adapted to multiple languages.
 
-When you create an Adaptation project, an *i18n.properties* file is created for every page of the application. Define a key-value pair in the *i18n.properties* file that you can refer to while providing text for the UI controls.
+When you create an adaptation project, an `i18n.properties` file is created for every page of the application. Define a key-value pair in the `i18n.properties` file that you can refer to while providing text for the UI controls.
 
 **Sample Folder Structure**
 
-In your workspace, under the Adaptation project, the folder structure looks like \(this is an example\):
+In your workspace, under the adaptation project, the folder structure looks like:
 
 -   Project name
 
@@ -42,5 +42,5 @@ In your workspace, under the Adaptation project, the folder structure looks like
 
 **Define Key-Value Pair**
 
-Define your key-value pairs in the *i18n.properties*. Refer to the keys while you edit the project using SAPUI5 Visual Editor. In the *Properties* pane, refer to the i18n key for a SAPUI5 control instead of typing-in the text. Run the project as a web application and check whether the i18n value associated to the key appears on the UI control. Similarly, you can change the text of existing UI controls by overriding the associated i18n key-value pairs in the source application.
+Define your key-value pairs in the `i18n.properties`. Refer to the keys while you edit the project using SAPUI5 Visual Editor. In the *Properties* pane, refer to the i18n key for a SAPUI5 control instead of typing in the text. Run the project as a web application and check whether the i18n value associated to the key appears on the UI control. Similarly, you can change the text of existing UI controls by overriding the associated i18n key-value pairs in the source application.
 
diff --git a/docs/make-adaptations-6d2cfea.md b/docs/make-adaptations-6d2cfea.md
index c9a6d6d..3d34950 100644
--- a/docs/make-adaptations-6d2cfea.md
+++ b/docs/make-adaptations-6d2cfea.md
@@ -2,7 +2,7 @@
 
 # Make Adaptations
 
-Define changes to the generated application variant in your SAPUI5 adaptation poject. You can adapt the UI and add app descriptor changes.
+Define changes to the generated application variant in your SAPUI5 adaptation project. You can adapt the UI and add app descriptor changes.
 
 
 
@@ -27,5 +27,5 @@ Define changes to the generated application variant in your SAPUI5 adaptation po
 
 
 > ### Note:  
-> Fiori Elements based apps can be additionally adapted using the possibilities described in [Extending Delivered Apps Using Adaptation Extensions](https://ui5.sap.com/#/topic/52fc48b479314d0688be24f699778c47).
+> Fiori Elements based apps can be additionally adapted using adaptation extensions. For more information, see [Extending Delivered Apps Using Adaptation Extensions](https://ui5.sap.com/#/topic/52fc48b479314d0688be24f699778c47).
 
diff --git a/docs/preview-the-adaptation-project-64cc15b.md b/docs/preview-the-adaptation-project-64cc15b.md
index 128a090..467b1b1 100644
--- a/docs/preview-the-adaptation-project-64cc15b.md
+++ b/docs/preview-the-adaptation-project-64cc15b.md
@@ -8,9 +8,9 @@ You can preview the adaptation project in a new browser tab.
 
 ## Context
 
-Expand the *webapp* folder from your workspace, right-click the `manifest.appdescr_variant` file, and choose *Open Preview*. You will be asked to allow popup windows, as this will trigger opening another browser tab – you should allow popups in this case.
+Expand the `webapp` folder from your workspace, right-click the `manifest.appdescr_variant` file, and click *Open Preview*. A prompt will appear asking you to allow popup windows because the preview opens in a separate browser tab. Click *Allow*.
 
-\(Optional\) Depending on your authentication model you might be asked to enter credentials for the system you are trying to reach. If this is the case, provide your credentials.
+\(Optional\) Depending on your authentication model, you might be asked to enter credentials for the system you are trying to reach. If this is the case, provide your credentials.
 
-The adaptation project will then be loaded in this separate browser tab. It is fully functional, you can navigate in it, load data, or test your newly added functionality.
+The adaptation project preview opens in a separate browser tab. You can navigate, load data, and test functionality.
 
diff --git a/docs/previewing-the-adaptation-project-8701335.md b/docs/previewing-the-adaptation-project-8701335.md
index 7ec06f7..57de54a 100644
--- a/docs/previewing-the-adaptation-project-8701335.md
+++ b/docs/previewing-the-adaptation-project-8701335.md
@@ -2,11 +2,22 @@
 
 # Previewing the Adaptation Project
 
+Learn how to preview an adaption project.
+
 
 
 ## Context
 
-Right click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file an choose *Preview Application*.
+Right click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Preview Application*.
+
+
+
+<a name="loio8701335d5dbd4d09babfabb5e9f752d7__steps_pgc_l4v_2dc"/>
+
+## Procedure
+
+1.  Right click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Preview Application*.
+
+2.  Click *start*. Your adaptation project will load in a separate browser tab. You can navigate, load data, and test your newly added functionality.
 
-Choose *start*. The adaptation project will then be loaded in this separate browser tab. It is fully functional, you can navigate in it, load data, or test your newly added functionality.
 
diff --git a/docs/releasing-an-sap-fiori-application-to-be-extensible-in-adaptation-projects-on-sap-s-4hana-1046206.md b/docs/releasing-an-sap-fiori-application-to-be-extensible-in-adaptation-projects-on-sap-s-4hana-1046206.md
index 089c203..eeeeba4 100644
--- a/docs/releasing-an-sap-fiori-application-to-be-extensible-in-adaptation-projects-on-sap-s-4hana-1046206.md
+++ b/docs/releasing-an-sap-fiori-application-to-be-extensible-in-adaptation-projects-on-sap-s-4hana-1046206.md
@@ -2,7 +2,7 @@
 
 # Releasing an SAP Fiori Application to Be Extensible in Adaptation Projects on SAP S/4HANA Cloud and SAP BTP, ABAP Environment
 
-If you develop an SAP Fiori application as an SAP partner and want to make it extensible in adaptation projects, you need to make sure that the UI adaptations made by your customers don't break during an upgrade.
+Ensure the UI adaptations that your customers make do not cause breaking changes when upgrading your project.
 
 
 
@@ -10,13 +10,13 @@ If you develop an SAP Fiori application as an SAP partner and want to make it ex
 
 ## Prerequisites
 
--   Follow the best practices for developing SAPUI5 applications. See [Best Practices for Developers](https://ui5.sap.com/#/topic/28fcd55b04654977b63dacbee0552712).
+-   Follow the best practices for developing SAPUI5 applications. For more information, see [Best Practices for Developers](https://ui5.sap.com/#/topic/28fcd55b04654977b63dacbee0552712).
 
--   Enable your app for UI adaptation. See [SAPUI5 Flexibility: Enable Your App for UI Adaptation](https://ui5.sap.com/#/topic/f1430c0337534d469da3a56307ff76af.html).
+-   Enable your application for UI adaptation. For more information, see [SAPUI5 Flexibility: Enable Your App for UI Adaptation](https://ui5.sap.com/#/topic/f1430c0337534d469da3a56307ff76af.html).
 
--   Before releasing a new version of your application, increment the version number in the `manifest.json` file, under `sap.app/applicationVersion/version`. See [Descriptor for Applications, Components, and Libraries \(manifest.json\)](https://ui5.sap.com/#/topic/be0cf40f61184b358b5faedaec98b2da).
+-   Before releasing a new version of your application, increment the version number in the `manifest.json` file, under `sap.app/applicationVersion/version`. For more information, see [Descriptor for Applications, Components, and Libraries \(manifest.json\)](https://ui5.sap.com/#/topic/be0cf40f61184b358b5faedaec98b2da).
 
-    A new version number is required for the consumer to be notified by an ATC check when the base app is updated. See [Check Whether Your Adaptation Project Is Up-To-Date with Base App Upgrades](check-whether-your-adaptation-project-is-up-to-date-with-base-app-upgrades-c6ef105.md).
+    A new version number is required for the consumer to be notified by an ATC check when the base app is updated. For more information, see [Check Whether Your Adaptation Project Is Up-To-Date with Base App Upgrades](check-whether-your-adaptation-project-is-up-to-date-with-base-app-upgrades-c6ef105.md).
 
 
 
@@ -29,7 +29,7 @@ If you develop an SAP Fiori application as an SAP partner and want to make it ex
 
     Set the state of the C1 contract to *Released*.
 
-    The C1 contract forbids incompatible changes of the structure of the service, but has no restrictions for changing annotations.
+    The C1 contract forbids incompatible changes of the structure of the service but has no restrictions for changing annotations.
 
     For more information, see [Setting the API Release State](https://help.sap.com/docs/SAP_S4HANA_CLOUD/25cf71e63940453397a32dc2b7676947/90339a4e940e44f2be4e96bb9d3b3d4d.html).
 
@@ -37,25 +37,25 @@ If you develop an SAP Fiori application as an SAP partner and want to make it ex
 
     In the `manifest.json` file, set the attribute `sap.fiori/cloudDevAdaptationStatus` to `released`.
 
-    Other allowed values are no value \(= not released\), `deprecated`, and `obsolete`.
+    Other allowed values are no value \(which means not released\), `deprecated`, and `obsolete`.
 
-    As a prerequisite for providing the manifest setting `sap.fiori/cloudDevAdaptationStatus`, the C1 contract for the OData service of the SAP Fiori app must be set to the state *Released*. The app can only be deployed if this prerequisite is met.
+    As a prerequisite for providing the manifest setting, `sap.fiori/cloudDevAdaptationStatus`, the C1 contract for the OData service of the SAP Fiori application must be set to the state *Released*. The application can only be deployed if this prerequisite is met.
 
-    In the `manifest.json` file, make sure that the attribute `sap.app/id` has at least 2 segments.
+    In the `manifest.json` file, ensure that the attribute: `sap.app/id` has at least two segments.
 
 3.  Release the authorization objects and the restriction types that are used by the OData service.
 
     Set the state of the C1 contract to *Released*.
 
-    Activate the checkbox *Use in Cloud Development*.
+    Select the *Use in Cloud Development* checkbox.
 
     > ### Note:  
-    > This step is not a prerequisite for releasing the OData service and the Fiori app. You can still create app variants even if the authorization objects and the restriction types of the OData service are not released. However a drawback is that the authorizations of the application variant are then identical to the authorizations of the original application. Furthermore the original app and the original app's business catalogs have to be assigned to the user's role,
+    > This step is not a prerequisite for releasing the OData service and the Fiori application. You can still create app variants even if the authorization objects and the restriction types of the OData service are not released. However, the authorizations of the application variant are then identical to the authorizations of the original application. Also, the original application and the original application's business catalogs must be assigned to the user's role.
 
-4.  Create an API snapshot including the released APIs, ideally directly before shipment, using the app *Manage API Snapshots*. See [Manage API Snapshots](https://help.sap.com/docs/SAP_S4HANA_CLOUD/6aa39f1ac05441e5a23f484f31e477e7/8dda6b60464540e1afe50d6d03320c99.html).
+4.  Create an API snapshot including the released APIs, directly before shipment, using the *Manage API Snapshots* application. For more information, see [Manage API Snapshots](https://help.sap.com/docs/SAP_S4HANA_CLOUD/6aa39f1ac05441e5a23f484f31e477e7/8dda6b60464540e1afe50d6d03320c99.html).
 
 
-Once you've set these contracts, they're enforced by ATC checks. For more information, see [Check Consistency of Release State](check-consistency-of-release-state-1f91cd4.md).
+Once you have set these contracts, they are enforced by ATC checks. For more information, see [Check Consistency of Release State](check-consistency-of-release-state-1f91cd4.md).
 
 **Related Information**  
 
diff --git a/docs/replacing-odata-service-6b51df2.md b/docs/replacing-odata-service-6b51df2.md
index da2abe8..d4facf6 100644
--- a/docs/replacing-odata-service-6b51df2.md
+++ b/docs/replacing-odata-service-6b51df2.md
@@ -2,25 +2,27 @@
 
 # Replacing OData Service
 
+Learn how to replace an OData service.
+
 
 
 ## Procedure
 
-1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file an choose Replace OData Service.
+1.  Right-click on the project main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and click *Replace OData Service*.
 
-2.  From the *Target*OData*Service* dropdown choose which service from the manifest of the base application you want to replace.
+2.  From the *Target OData Service* dropdown, choose which service from the manifest of the base application you want to replace.
 
 3.  Enter the URI of the OData service you want to use instead.
 
-4.  \(Optional\) Enter maxAge of the new OData service.
+4.  \(Optional\) Enter the `maxAge` of the new OData service.
 
 5.  \(Optional\) Enter the URI of the OData Annotation Data Source you want to use instead.
 
-    This field will be visible, if the service you are using supports annotations.
+    This field will be visible if the service you are using supports annotations.
 
     > ### Note:  
-    > The new OData service needs to be compatible to the OData service of the original app. The entity set names, properties in the entity set, and function imports used from the original service should also exist in the new service. For V2 services using annotations, the annotation data source needs to be changed and the new annotation must also be compatible with the annotation of the original app.
+    > The new OData service needs to be compatible with the OData service of the original app. The entity set names, properties in the entity set, and function imports used from the original service should also exist in the new service. For OData V2 services using annotations, the annotation data source needs to be changed and the new annotation must also be compatible with the annotation of the original application.
 
-6.  Choose *Finish* to create the change.
+6.  Click *Finish* to save your changes.
 
 
diff --git a/docs/replacing-odata-service-e913fbf.md b/docs/replacing-odata-service-e913fbf.md
index f9a662e..6b04b89 100644
--- a/docs/replacing-odata-service-e913fbf.md
+++ b/docs/replacing-odata-service-e913fbf.md
@@ -2,7 +2,7 @@
 
 # Replacing OData Service
 
-This guide describes how to replace OData service in an adaptation project without tooling support.
+This guide describes how to replace an OData service in an adaptation project without tooling support.
 
 
 
@@ -11,7 +11,7 @@ This guide describes how to replace OData service in an adaptation project witho
 ## Context
 
 > ### Note:  
-> The new OData service needs to be compatible to the OData service of the original app. The entity set names, properties in the entity set, and function imports used from the original service should also exist in the new service. For V2 services using annotations, the annotation data source needs to be changed and the new annotation must also be compatible with the annotation of the original app.
+> The new OData service needs to be compatible to the OData service of the original app. The entity set names, properties in the entity set, and function imports used from the original service must also exist in the new service. For OData V2 services using annotations, the annotation data source needs to be changed and the new annotation must also be compatible with the annotation of the original app.
 
 
 
@@ -19,18 +19,18 @@ This guide describes how to replace OData service in an adaptation project witho
 
 1.  Right click the `manifest.appdescr_variant` file of your adaptation project and select the *Adaptation Project* \> *Replace OData Service*.
 
-2.  After the wizard starts you may be asked to enter the credentials for the system that you created your adaptation project.
+2.  After the wizard starts, you may be asked to enter the credentials for the system that you created your adaptation project.
 
-3.  From the *Target OData Service* dropdown choose which service from the manifest of the base application you want to replace.
+3.  From the *Target OData Service* dropdown, choose which service from the manifest of the base application you want to replace.
 
 4.  Enter the URI of the OData service you want to use instead.
 
-5.  \(Optional\) Enter maxAge of the new OData service.
+5.  \(Optional\) Enter the maxAge of the new OData service.
 
 6.  \(Optional\) Enter the URI of the OData Annotation Data Source you want to use instead.
 
-    This field will be visible, if the service you are using supports annotations.
+    This field will be visible if the service you are using supports annotations.
 
-7.  Choose *Finish* to create the change.
+7.  Click *Finish* to save your changes.
 
 
diff --git a/docs/updating-the-adaptation-project-5808877.md b/docs/updating-the-adaptation-project-5808877.md
index 20ba2a8..2cef6f3 100644
--- a/docs/updating-the-adaptation-project-5808877.md
+++ b/docs/updating-the-adaptation-project-5808877.md
@@ -2,30 +2,26 @@
 
 # Updating the Adaptation Project
 
+Learn how to update an adaptation project to redeploy your changes.
+
 
 
 <a name="loio580887790be14634a44f620127dbeb5e__prereq_hd2_g2g_wtb"/>
 
 ## Prerequisites
 
-You have already deployed the adaptation project in question to an on-premise system following the procedure described in [Deploy the Adaptation Project to the ABAP Repository](https://help.sap.com/docs/bas/developing-sap-fiori-app-in-sap-business-application-studio/deploy-adaptation-project?locale=en-US). The technical requirements for the update action are the same as these for the deploy.
-
-
-
-## Context
-
-When you have previously deployed your adaptation project but there are further changes in it, you can redeploy it update it directly using the same tool used for deployment.
+You have already deployed your adaptation project to an on-premise system following the procedure described in [Deploy the Adaptation Project to the ABAP Repository](https://help.sap.com/docs/bas/developing-sap-fiori-app-in-sap-business-application-studio/deploy-adaptation-project?locale=en-US).
 
 
 
 ## Procedure
 
-1.  Right-click on main folder, the `webapp` folder, or the `manifest.appdescr_variant` file and select *Open Deployment Wizard*.
+1.  Right-click on the main folder, the `webapp` folder, or the`manifest.appdescr_variant` file and click *Open Deployment Wizard*.
 
-2.  Choose which system you want to deploy the project to. The system that you have used for the creation of the project is selected by default.
+2.  Choose which system you want to deploy the project to. The system that you have used to create the project is selected by default.
 
-3.  If the project that you have selected has been already deployed to that system \(it is eligible for update\) you will be asked what action would you like to perform – *Update* or *Undeploy*. Choose *Update*.
+3.  If the project that you have selected has been already deployed to that system, you will be asked what action would you like to perform: *Update* or *Undeploy*. Click*Update*.
 
-4.  Choose `Next`, to start the deployment process.
+4.  Click *Next* to start the deployment process.
 
 
diff --git a/docs/upgrade-safe-compatibility-rules-53706e2.md b/docs/upgrade-safe-compatibility-rules-53706e2.md
index f0b4ebb..39ae429 100644
--- a/docs/upgrade-safe-compatibility-rules-53706e2.md
+++ b/docs/upgrade-safe-compatibility-rules-53706e2.md
@@ -8,10 +8,10 @@
 
 ## Overview
 
-SAPUI5 Flexibility ensures a modification-free extensibility approach by separating extension code from the original application life cycle. However, applications may change their UI implementation details and enhance their service implementation compatibly during the upgrade. Developing controller extensions along this guideline will prevent breaking extensions after the upgrade of the base application or reduce effort to adapt to potential changes on UI level.
+SAPUI5 Flexibility ensures a modification-free extensibility approach by separating extension code from the original application life cycle. However, applications may change their UI implementation details and enhance their service implementation compatibility during the upgrade. Developing controller extensions using these rules will prevent breaking extensions after the upgrading the base application and reduce the effort to adapt to changes on the UI level.
 
 > ### Note:  
-> To comply with automatic upgrades in Cloud, an Adaptation project deployed to S/4HANA Cloud system will contain a runnable snapshot of the base application containing all UI artefacts as well as a local copy of all UI annotations. Once the base application is upgraded, the snapshot will ensure that the extended application is still runnable even in case of conflicts between extension coding and new UI implementation details. Those conflicts should be solved, and a new version of Adaptation project has to be deployed to benefit from the upgraded version as well as to receive further support for the base app functionality in the extension case.
+> To comply with automatic upgrades in the adaptation project deployed to S/4HANA Cloud system will contain a runnable snapshot of the base application containing all UI artefacts as well as a local copy of all UI annotations. Once the base application is upgraded, the snapshot will ensure that the extended application is still runCloud, and stable even in case of conflicts between extension coding and new UI implementation details. However, you still need to solve these conflicts and deploy a new version of your adaptation project to benefit from the upgraded version as well as to receive support for the base app functionality.
 
 To check whether the base app of an adaptation project is up-to-date, see [Check Whether Your Adaptation Project Is Up-To-Date with Base App Upgrades](check-whether-your-adaptation-project-is-up-to-date-with-base-app-upgrades-c6ef105.md).
 
@@ -23,15 +23,15 @@ To check whether the base app of an adaptation project is up-to-date, see [Check
 
 -   Follow the general [Best Practices for Developers](https://ui5.sap.com/#/topic/28fcd55b04654977b63dacbee0552712).
 
--   Only access controls with stable IDs, never rely on the order of controls in the aggregations or parent-child chain.
+-   Only access controls with stable IDs. Never rely on the order of controls in the aggregations or parent-child chain.
 -   Always check that a control you are accessing exists and that it is of an expected control type before calling any further methods of the control.
 
-    This applies also for controls added via adaptation project, which might have been added by [Add Fragments to an Aggregation or Extension Point](add-fragments-to-an-aggregation-or-extension-point-6033d56.md) changes or via controller coding.
+    This also applies to controls added using an adaptation project which can be added added by [Add Fragments to an Aggregation or Extension Point](add-fragments-to-an-aggregation-or-extension-point-6033d56.md) changes or controller coding.
 
 -   Don't call or override any private or protected methods of SAPUI5 app coding.
 -   Don’t use any deprecated SAPUI5 artifacts \(controls, properties, methods, or other\).
 -   Value helps are not part of the SAP internal stability contract \(for example, they might change after an upgrade\). Do not use value help entity sets in the controller coding and for data binding of controls in XML fragments.
 -   For SAP Fiori elements-based applications, follow the guide [Extending Delivered Apps Using Adaptation Extension](https://ui5.sap.com/#/topic/52fc48b479314d0688be24f699778c47).
--   Reuse components might change, always write resilient coding when accessing any functionality of a reuse component to handle unexpected errors and failures gracefully.
--   The OData metadata can change during the app upgrade, so don't hard code against any property values.
+-   Reuse components might change. Always write resilient coding when accessing any functionality of a reuse component to handle unexpected errors and failures gracefully.
+-   The OData metadata can change during the app upgrade so do not hard code against any property values.