diff --git a/packages/@okta/vuepress-site/.vuepress/public/img/oin/scim_unmap-attribute.png b/packages/@okta/vuepress-site/.vuepress/public/img/oin/scim_unmap-attribute.png
index 9812092543c..9e4d1a9ad43 100644
Binary files a/packages/@okta/vuepress-site/.vuepress/public/img/oin/scim_unmap-attribute.png and b/packages/@okta/vuepress-site/.vuepress/public/img/oin/scim_unmap-attribute.png differ
diff --git a/packages/@okta/vuepress-site/docs/guides/submit-app/main/index.md b/packages/@okta/vuepress-site/docs/guides/submit-app/main/index.md
index ff648744194..943829db0b2 100644
--- a/packages/@okta/vuepress-site/docs/guides/submit-app/main/index.md
+++ b/packages/@okta/vuepress-site/docs/guides/submit-app/main/index.md
@@ -8,7 +8,7 @@ layout: Guides
 
 Use this guide to understand the process of submitting Workflows connector and API service integrations to the Okta Integration Network (OIN) using the OIN Manager. This guide also shows you how to update a previously published integration or delete a draft submission.
 
-> **Note:** For SSO or Lifecycle Management (LCM) SCIM integrations, use the [OIN Wizard](/docs/guides/submit-oin-app/scim/main/) for a seamless ISV submission experience. Previously submitted SSO and LCM SCIM integrations from the OIN Manager have been migrated to the OIN Wizard. You can edit these published integrations directly in the OIN Wizard and resubmit them to the OIN team. See [Update a published integratin with the OIN Wizard](/docs/guides/update-oin-app/).
+> **Note:** For SSO or Lifecycle Management (LCM) SCIM integrations, use the [OIN Wizard](/docs/guides/submit-oin-app/scim/main/) for a seamless ISV submission experience. Previously submitted SSO and LCM SCIM integrations from the OIN Manager have been migrated to the OIN Wizard. You can edit these published integrations directly in the OIN Wizard and resubmit them to the OIN team. See [Update a published integration with the OIN Wizard](/docs/guides/update-oin-app/).
 
 ---
 
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/saml2/backward-compatible-eg.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/saml2/backward-compatible-eg.md
index 12b8f7da326..d9281455f8e 100644
--- a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/saml2/backward-compatible-eg.md
+++ b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/saml2/backward-compatible-eg.md
@@ -1,4 +1,4 @@
-   Your integration update introduced a new variable (`companyId`), and you use it in your updated ACS URL. The ACS URL changed from `https://login.myapp.io` to `https://login.myapp.io?connection={org.companyId}`. In this case, ensure that the dynamic ACS URL is also valid for existing instances where the `companyId` value isn't set.
+   Your integration update introduced a new variable (`companyId`), and you use it in your updated ACS URL. The ACS URL changed from `https://login.myapp.io` to `https://login.myapp.io?connection=${org.companyId}`. In this case, ensure that the dynamic ACS URL is also valid for existing instances where the `companyId` value isn't set.
 
    To handle empty `companyId` values, you can define the ACS URL as:
 
diff --git a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/scim/backward-compatible-eg.md b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/scim/backward-compatible-eg.md
index 732d3f9f2aa..3ee8477b538 100644
--- a/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/scim/backward-compatible-eg.md
+++ b/packages/@okta/vuepress-site/docs/guides/update-oin-app/main/scim/backward-compatible-eg.md
@@ -1,4 +1,4 @@
-   Your integration update introduced a new variable (`companyId`), and you use it in your updated SCIM server base URL. The base URL changed from `https://fruits.example.com/scim2/myapp/` to `https://fruits.example.com/scim2/myapp?connection={app.companyId}`. In this case, ensure that the dynamic base URL is also valid for existing instances where the `companyId` value isn't set.
+   Your integration update introduced a new variable (`companyId`), and you use it in your updated SCIM server base URL. The base URL changed from `https://fruits.example.com/scim2/myapp/` to `'https://fruits.example.com/scim2/myapp?connection=' + app.companyId`. In this case, ensure that the dynamic base URL is also valid for existing instances where the `companyId` value isn't set.
 
    To handle empty `companyId` values, you can define the base URL as: