Add Tomasz's feedback and edits

Author: vanngo-okta

packages/@okta/vuepress-site/docs/guides/submit-oin-app/main/wfactions/universal-logout-properties.md

@@ -4,9 +4,9 @@
 > * This section appears only if you select **Universal Logout** with API Integration Actions.
 > * Universal Logout is only supported with SSO integrations.
 > * If you want instructions for SSO integrations, select **OpenID Connect** or **SAML 2.0** from the **Instructions for** dropdown list on the right.
-> * For integrations that include API Integration Actions, always access the OIN Wizard through the **Application** > **Your OIN Integrations** path in the Admin Console.
+> * For integrations that include API actions, always access the OIN Wizard through the **Application** > **Your OIN Integrations** path in the Admin Console.
 
-1. Specify the following properties for Universal Logout with API Integration Actions:
+1. Specify the following properties for Universal Logout:
 
     | <div style="width:150px">Property</div> | Description  |
     | ----------------- | ------------ |

packages/@okta/vuepress-site/docs/guides/update-oin-app/main/index.md

@@ -40,7 +40,7 @@ The OIN Wizard currently supports updates for integrations that use the followin
 
 > **Note:** You can use the [OIN Wizard](/docs/guides/update-oin-app/) to update OIDC, SAML 2.0, SCIM 2.0, and API service integrations that were originally submitted through the [OIN Manager](/docs/guides/submit-app/).
 
-When you edit a published OIN integration, you need to test the flows for the updated version and the published version for backwards compatibility. The integration version that was previously installed in your customer's org isn't modified with the updated version from the OIN catalog. Testing the published version for backwards compatibility ensures that your integration still works for customers who have already installed it. See [Update integration considerations](#update-integration-considerations) before you edit your published integration.
+When you edit a published OIN integration, you need to test the flows for the updated version and the published version for backwards compatibility. The integration version that was previously installed in your customer's org won't contain new settings from the updated version. Testing the published version for backwards compatibility ensures that your integration still works for customers who have already installed it. See [Update integration considerations](#update-integration-considerations) before you edit your published integration.
 
 After you successfully test the updated and published versions of your integration, resubmit your integration to the OIN team. Your integration goes through a [submission review process](/docs/guides/submit-app-overview/#understand-the-submission-review-process) before the updated version is published in the OIN catalog.
 
@@ -49,7 +49,7 @@ After you successfully test the updated and published versions of your integrati
 > **Note:** Some considerations on this page are specifically for the **<StackSnippet snippet="protocol-name" inline/>** . <br>
 > If you want to change the instructions that you see on this page, select a different option from the **Instructions for** dropdown list.
 
-When you update an integration that's already published, be mindful to preserve backwards compatibility for your integration. Older instances of your integration could be in use by Okta customers.
+When you update an integration that's already published, be mindful to preserve backwards compatibility for customer that have installed your integration before your latest update.
 
 * If you modify the **Name** (`name`) property of your [tenant settings](/docs/guides/submit-oin-app/openidconnect/main/#tenant-settings), Okta removes the original variable and creates a variable with your updated name. This action negatively impacts your existing customers if you use the original variable in your integration dynamic properties.
 

packages/@okta/vuepress-site/docs/guides/update-oin-app/main/scim/required-app-instances.md

@@ -3,7 +3,7 @@ The **Required app instances** section shows you the instances detected in your
 * The **CURRENT VERSION** status indicates the instances that you need to test your current integration submission. [Generate an instance](#generate-an-instance) to test SCIM if **No instance detected** appears next to the **SCIM** label.
 * The **PUBLISHED VERSION** status indicates the instances that you need to test backwards compatibility for SSO. If your integration only supports the SCIM protocol, then the OIN Wizard doesn't require a published-version instance.
 
-Depending on the nature of your updates, you may need to generate instances for backward-compatibility testing. Okta recommends that you execute the Runscope tests on your SCIM published-version instance for backwards compatibility, but it's not a requirement for submission.
+Depending on the nature of your updates, you may need to generate instances for backwards-compatibility testing. Okta recommends that you execute the Runscope tests on your SCIM published-version instance for backwards compatibility, but it's not a requirement for submission.
 
    * If you're only updating app profiles or mapping, then you don't need to create an extra app instance for SCIM backward-compatibility testing. You can test the app profile updates in the updated instance version of your submission. See [Configure attribute mappings](#configure-attribute-mappings) when you generate a SCIM instance for testing. However, if you're updating the properties such as description, logo, or guide link, then Okta recommends that you create an extra app instance for SCIM backward-compatibility testing.
 

packages/@okta/vuepress-site/docs/guides/update-oin-app/main/wfactions/considerations.md

@@ -1,4 +1,4 @@
-* You can add the Entitlement Management capability only if your integration also supports provisioning with API integration actions.
+* You can add the Entitlement Management capability only if your integration also supports provisioning.
 
 * The API service capability is mutually exclusive of other capabilities in a submission. If you selected the SSO or provisioning capabilities, you can't select the API service capability (the option is unavailable in the submission).
 

packages/@okta/vuepress-site/docs/guides/update-oin-app/main/wfactions/test-instance.md

@@ -4,5 +4,5 @@ Test the following on both your published and updated generated instances:
 
 * For Universal Logout integration updates, test the logout flow manually. See [Test your Universal Logout integration](/docs/guides/submit-oin-app/wfactions/main/#test-your-universal-logout-integration).
 
-* For API Integration Actions updates, Okta provides a test plan for you to functionally test your provisioning flow through the Admin Console and End-User Dashboard. See [Test API integration action provisioning](/docs/guides/submit-oin-app/wfactions/main/#test-api-integration-action-provisioning).
+* For API action updates, Okta provides a test plan for you to functionally test your provisioning flow through the Admin Console and End-User Dashboard. See [Test API integration action provisioning](/docs/guides/submit-oin-app/wfactions/main/#test-api-integration-action-provisioning).