jborsecnik commented

Author: yoelhor

.openpublishing.redirection.json

@@ -6392,6 +6392,11 @@
       "redirect_url": "https://azure.microsoft.com/global-infrastructure/services/?products=active-directory-ds",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/active-directory-b2c/saml-technical-profile.md",
+      "redirect_url": "/azure/active-directory-b2c/saml-identity-provider-technical-profile",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/active-directory-ds/active-directory-ds-synchronization.md",
       "redirect_url": "/azure/active-directory-domain-services/synchronization",

articles/active-directory-b2c/identity-provider-salesforce-custom.md

@@ -199,13 +199,13 @@ The **ClaimsProviderSelection** element is analogous to an identity provider but
 Now that you have a button in place, you need to link it to an action. The action, in this case, is for Azure AD B2C to communicate with a Salesforce account to receive a token.
 
 1. Find the **OrchestrationStep** that includes `Order="2"` in the user journey.
-2. Add the following **ClaimsExchange** element making sure that you use the same value for **Id** that you used for **TargetClaimsExchangeId**:
+2. Add the following **ClaimsExchange** element making sure that you use the same value for **ID** that you used for **TargetClaimsExchangeId**:
 
     ```XML
     <ClaimsExchange Id="SalesforceExchange" TechnicalProfileReferenceId="salesforce" />
     ```
 
-    Update the value of **TechnicalProfileReferenceId** to the **Id** of the technical profile you created earlier. For example, `LinkedIn-OAUTH`.
+    Update the value of **TechnicalProfileReferenceId** to the **ID** of the technical profile you created earlier. For example, `LinkedIn-OAUTH`.
 
 3. Save the *TrustFrameworkExtensions.xml* file and upload it again for verification.