Merge branch 'admin-ui-sdk-2.1' of https://github.com/asalloum5/commerce-extensibility into pr/301

Author: keharper

src/pages/admin-ui-sdk/app-registration.md

@@ -141,7 +141,7 @@ This file now declares extensions and redirects to an `ext.config.yaml` file.
 
 ## Add or update the `ext.config.yaml`
 
-Add or update the `ext.config.yaml` under `src/commerce-backend-ui-1`. This directory will contain the `actions` and `web-src` code.
+Add or update the `src/commerce-backend-ui-1/ext.config.yaml` file. The `commerce-backend-ui-1` directory contains the `actions` and `web-src` code.
 
 Your extension configuration file should look like this:
 
@@ -168,8 +168,8 @@ runtimeManifest:
             final: true
 ```
 
-The package should be called `admin-ui-sdk` and the action called `registration`. The function can point to any route that returns the registration in the correct expected format.
+The package name must be `admin-ui-sdk`, and the action must be `registration`. The `function` can point to any route that returns the registration in the correct expected format.
 
-It is recommended to secure the registration runtime action by setting `require-adobe-auth` to `true`. The Adobe Commerce instance will correctly load registrations securely based on the IMS credentials provided.
+We recommend securing the registration runtime action by setting `require-adobe-auth` to `true`. The Adobe Commerce instance will correctly load registrations securely based on the provided IMS credentials.
 
 Complete this file with the actions from your app.

src/pages/admin-ui-sdk/configuration.md

@@ -14,23 +14,23 @@ Navigate to **Stores** > Settings > **Configuration** > **Adobe Services** > **A
 
 ## General configuration
 
-The general configuration section allows to enable the Admin UI SDK and refresh registrations when changes are made.
+The **General configuration** section enables the Admin UI SDK and refreshes registrations when changes are made.
 
 ![Admin UI SDK general configuration](../_images/admin-ui-sdk-general-config.png)
 
-The Admin UI SDK is disabled by default. To enable it, set the `Enable Admin UI SDK` field to `Yes`. To disable it, change this field to `No`.
+The Admin UI SDK is disabled by default. To enable it, set the **Enable Admin UI SDK** field to **Yes**.
 
-The `Refresh registrations` button reloads all registrations from the registries. It is typically used when changes are made to the registration on the app builder application side or when a new app is added and published, to reflect these changes in the Admin Panel.
+The `Refresh registrations` button reloads all registrations from the registries. It is typically used when changes are made to the registration on the app builder application side or when a new app is added and published, to reflect these changes in the Admin.
 
 ## Database logging configuration
 
-The database logging configuration enables saving logs generated by the Admin UI SDK in the database with a specified retention period. These logs can be accessed directly in the Admin Panel by navigating to **System** > Admin UI SDK > **Admin UI SDK Logs** screen.
+The **Database logging configuration** section allows you to save Admin UI SDK log entries for the specified retention period.
 
 ![Admin UI SDK database logging configuration](../_images/admin-ui-sdk-db-log-config.png)
 
-To save logs, set the `Enable Logs` field to `Yes`. By default, this field is set to `No`.
+To save logs, set the **Enable Logs** field to **Yes**. By default, this field is set to **No**.
 
-Set the minimum log level to save. Any logs at this level or higher will be stored. By default, the minimum level is set to `Warning`.
+Set the minimum log level to save. Any logs at this level or higher will be stored. By default, the minimum level is set to **Warning**.
 
 Set the retention period for logs to be cleaned from the database. This field specifies the number of days. By default, the retention period is set to 1 day.
 
@@ -42,15 +42,9 @@ The staging testing option provides a sandbox environment to test your applicati
 
 1. Select **Yes** from the **Enable testing** menu.
 
-1. Set the **Testing mode** to `Staging`.
+1. Set the **Testing mode** to **Staging**.
 
-1. Select all app status to load in the Admin Panel.
-
-### Prerequisites
-
-* Adobe Commerce on cloud infrastructure or on premises: 2.4.5+
-* PHP 8.1+
-* [Adobe Identity Management Service (IMS) for Adobe Commerce](https://experienceleague.adobe.com/docs/commerce-admin/start/admin/ims/adobe-ims-integration-overview.html)
+1. Select all app statuses to load.
 
 ## Local testing
 
@@ -72,10 +66,6 @@ When you enable the local service, all calls are automatically redirected to the
 
 1. Save your configuration.
 
-### Prerequisites
-
-- An Adobe Commerce instance installed on the local machine.
-
 ### Configuration
 
 You can download a sample app from the [Adobe Commerce Samples repository](https://github.com/adobe/adobe-commerce-samples/tree/main/admin-ui-sdk/menu/custom-menu) to gain insight on how the Admin SDK injects menus and pages into the Admin.

src/pages/admin-ui-sdk/extension-points/customer/grid-columns.md

@@ -77,9 +77,9 @@ It leverages API Mesh [JSON Schemas handler](https://developer.adobe.com/graphql
 
 ### Sample runtime action to retrieve data
 
-This sample `get-customers` runtime action is referenced in the mesh configuration file. It defines the path to the runtime action to retrieve the data of custom columns.
+The `get-customers` sample runtime action is referenced in the mesh configuration file. It defines the path to the runtime action that retrieves the data of custom columns.
 
-It is important to add the `ids={args.ids}` as part of the query and handle this filtering in the runtime action. This will allow Admin UI SDK to load only necessary data needed to display in the grid columns in the Admin Panel of the Adobe Commerce instance.
+It is important to add the `ids={args.ids}` as part of the query and handle this filtering in the runtime action. This allows Admin UI SDK to load only the necessary data needed to display in the grid columns in the Admin.
 
 ```javascript
 export async function main(props) {
@@ -125,7 +125,7 @@ export async function main(props) {
 
 ### Sample schema file
 
-This sample `schema.json` file is referenced in the mesh configuration file. It defines the response of the external `customerGridColumns` query that fetches column data.
+The  `schema.json` sample file, which is also referenced in the mesh configuration file, defines the response of the external `customerGridColumns` query that fetches column data.
 
 ```json
 {
@@ -155,9 +155,9 @@ This sample `schema.json` file is referenced in the mesh configuration file. It
 }
 ```
 
-### Create or Update your mesh
+### Create or update your mesh
 
-Make sure to create or update your mesh, and to keep the mesh id provided.
+Use one of the following commands to create or update your mesh. Be sure to store the mesh ID provided.
 
 ```bash
 aio api-mesh:create mesh.json
@@ -169,17 +169,13 @@ aio api-mesh:update mesh.json
 
 ### Customer data matching
 
-#### Id matching
+The Admin UI SDK expects the customer ID in Adobe Commerce to correctly match the customer to the data and fill the correct cell.
 
-The Admin UI SDK expects the customer id in Adobe Commerce to correctly match the customer to the data and fill the correct cell.
+A default value can be provided to be added to unmatched IDs, or in case data doesn't match, the expected type of the column. If a value is not provided, the cell is left empty.
 
-#### Default value
+In case of error, check the Adobe Commerce logs.
 
-A default value can be provided to be added to unmatched ids, or in case data doesn't match the expected type of the column. If not provided, the cell is left empty.
-
-In case of error, more info can be found in the Adobe Commerce logs.
-
-##### Example of default value
+The following example provides a default value.
 
 ```javascript
 "*": {

src/pages/admin-ui-sdk/extension-points/order/grid-columns.md

@@ -85,7 +85,7 @@ It leverages API Mesh [JSON Schemas handler](https://developer.adobe.com/graphql
 
 This sample `get-orders` runtime action is referenced in the mesh configuration file. It defines the path to the runtime action to retrieve the data of custom columns.
 
-It is important to add the `ids={args.ids}` as part of the query and handle this filtering in the runtime action. This will allow Admin UI SDK to load only necessary data needed to display in the grid columns in the Admin Panel of the Adobe Commerce instance.
+It is important to add `ids={args.ids}` to the query and handle this filtering in the runtime action. As a result, the Admin UI SDK loads only the data necessary to display in the grid columns of the Admin.
 
 ```javascript
 export async function main(props) {

src/pages/admin-ui-sdk/extension-points/product/grid-columns.md

@@ -36,9 +36,9 @@ product: {
 
 ### Sample runtime action to retrieve data
 
-This sample `get-products` runtime action is referenced in the mesh configuration file. It defines the path to the runtime action to retrieve the data of custom columns.
+The mesh configuration fule references the `get-products` sample runtime action. It defines the path to the runtime action to retrieve the data of custom columns.
 
-It is important to add the `ids={args.ids}` as part of the query and handle this filtering in the runtime action. This will allow Admin UI SDK to load only necessary data needed to display in the grid columns in the Admin Panel of the Adobe Commerce instance.
+It is important to add `ids={args.ids}` to the query and handle this filtering in the runtime action. As a result, the Admin UI SDK loads only the data necessary to display in the grid columns of the Adobe Commerce instance.
 
 ```javascript
 export async function main(props) {
@@ -149,9 +149,9 @@ This sample `schema.json` file is referenced in the mesh configuration file. It
 }
 ```
 
-### Create or Update your mesh
+### Create or update your mesh
 
-Make sure to create or update your mesh, and to keep the mesh id provided.
+Use one of the following commands to create or update your mesh. Be sure to store the mesh ID provided.
 
 ```bash
 aio api-mesh:create mesh.json
@@ -163,17 +163,13 @@ aio api-mesh:update mesh.json
 
 ### Products data matching
 
-#### Id matching
+The Admin UI SDK expects the product SKU in Adobe Commerce to correctly match the product to the data and to fill the correct cell.
 
-The Admin UI SDK expects the product sku in Adobe Commerce to correctly match the product to the data and fill the correct cell.
+A default value can be provided to be added to unmatched IDs, or in case data doesn't match, the expected type of the column. If a value is not provided, the cell is left empty.
 
-#### Default value
+In case of error, check the Adobe Commerce logs.
 
-A default value can be provided to be added to unmatched ids, or in case data doesn't match the expected type of the column. If not provided, the cell is left empty.
-
-In case of error, more info can be found in the Adobe Commerce logs.
-
-##### Example of default value
+The following example provides a default value.
 
 ```javascript
 "*": {