Merge branch 'main' into CEXT-3814

Author: keharper

src/pages/_images/events/general-configuration-updated.png

@@ -30,9 +30,9 @@ You must configure Commerce to communicate with your project. Configuration incl
 
 1. Copy the entire contents of the `<workspace-name>.json` file into the **Adobe I/O Workspace Configuration** field.
 
-1. Enter a unique identifier in the **Adobe Commerce Instance ID** field. This unique value identifies your Commerce instance, which allows Commerce events to connect to the correct `Event Provider` in Adobe I/O. This ID corresponds to the **Provider** displayed when [subscribing to events](#subscribe-and-register-events).
+1. Enter a unique identifier in the **Adobe I/O Event Provider Instance ID** field. This unique value identifies your Commerce instance, which allows Commerce events to connect to the correct `Event Provider` in Adobe I/O. This ID corresponds to the **Provider** displayed when [subscribing to events](#subscribe-and-register-events).
 
-   **Note**: The **Adobe Commerce Instance ID** field only supports alphanumeric characters, hyphens and underscores.
+   **Note**: The **Adobe I/O Event Provider Instance ID** field only supports alphanumeric characters, hyphens and underscores.
 
 1. Click **Save Config**, but do not leave the page. The next section creates an event provider, which is necessary to complete the configuration.
 

src/pages/_images/events/instance-name-developer-commerce.png

@@ -81,7 +81,7 @@ The event payload for this event could not contain the saved order's extension a
   const content = await oauth.get('orders/' + event_payload.entity_id)
 ```
 
-This example uses functions from the `oauth1a` module, as defined in the [adobe-commerce-samples repo](https://github.com/adobe/adobe-commerce-samples/blob/main/admin-ui-sdk/menu/custom-menu/actions/oauth1a.js).
+This example uses functions from the `oauth1a` module, as defined in the [adobe-commerce-samples repo](https://github.com/adobe/adobe-commerce-samples/blob/main/admin-ui-sdk/menu/custom-menu/src/commerce-backend-ui-1/actions/oauth1a.js).
 
 You can retrieve the `consumerKey`, `consumerSecret`, `accessToken`, and `accessTokenSecret` provided in the input to the `getCommerceOauthClient` function from Commerce after creating and activating an [Integration](https://experienceleague.adobe.com/en/docs/commerce-admin/systems/integrations) in the Commerce admin. You can configure these values in an App Builder [.env file](https://developer.adobe.com/app-builder/docs/guides/configuration/#env) and then [pass them as inputs to the App Builder action](https://developer.adobe.com/app-builder/docs/guides/configuration/#using-environment-variables-in-runtime-actions) through the action's configuration.
 

src/pages/events/configure-commerce.md

@@ -87,11 +87,11 @@ After adding the required API, download the workspace configuration for your pro
 
 ### The status shows the events have been successfully sent, but they were not received in the event registration
 
-If events are not received, determine if you have a different value for the `Adobe Commerce Instance ID` configured in the Adobe Commerce environment that is used in the event registration of the Developer Console.
+If events are not received, determine if you have a different value for the `Adobe I/O Event Provider Instance ID` configured in the Adobe Commerce environment that is used in the event registration of the Developer Console.
 
 ![Choose your instance ](../_images/events/instance-name-developer-console.png)
 
-![Adobe Commerce instance ID](../_images/events/instance-name-developer-commerce.png)
+![Adobe I/O Event Provider Instance ID](../_images/events/instance-name-developer-commerce.png)
 
 ## Event subscribe CLI command error
 

src/pages/events/consume-events-examples/runtime-action-commerce-callback.md

@@ -256,7 +256,7 @@ You must configure Commerce to communicate with your project. Configuration incl
 
 1. Copy the contents of the `<workspace-name>.json` file into the **Adobe I/O Workspace Configuration** field.
 
-1. Enter a unique identifier in the **Adobe Commerce Instance ID** field. This unique value identifies your Commerce instance, which allows Commerce events to connect to the correct `Event Provider` in Adobe I/O. This ID corresponds to the **Provider** displayed when [subscribing to events](../events/configure-commerce.md#subscribe-and-register-events).
+1. Enter a unique identifier in the **Adobe I/O Event Provider Instance ID** field. This unique value identifies your Commerce instance, which allows Commerce events to connect to the correct `Event Provider` in Adobe I/O. This ID corresponds to the **Provider** displayed when [subscribing to events](../events/configure-commerce.md#subscribe-and-register-events).
 
    **Note**: This value must contain English alphanumeric characters, underscores (_), and hyphens (-) only.