Acrolinx updates

Author: ryanberg-aquent

support/entra/entra-id/app-integration/error-code-AADSTS50105-user-not-assigned-role.md

@@ -1,12 +1,12 @@
 ---
-title: Error AADSTS50105 - The signed in user is not assigned to a role for the application.
+title: Error AADSTS50105 - The signed in user isn't assigned to a role for the application.
 description: Describes a problem in which you receive the AADSTS50105 error when you sign in to a SAML-based configured app with Microsoft Entra SSO.
 ms.date: 07/19/2023
 ms.reviewer: bernawy
 ms.service: entra-id
 ms.custom: sap:Issues Signing In to Applications
 ---
-# Error AADSTS50105 - The signed in user is not assigned to a role for the application
+# Error AADSTS50105 - The signed in user isn't assigned to a role for the application
 
 ## Summary
 
@@ -16,7 +16,7 @@ This article provides a resolution to the AADSTS50105 error that occurs during f
 
 ## Symptoms
 
-You receive the following error message when you try to sign in to an application that has been set up to use Microsoft Entra ID for identity management using SAML-based Single Sign-On (SSO):
+You receive the following error message when you try to sign in to an application that has been set up to use Microsoft Entra ID for identity management using SAML-based single sign-on (SSO):
 
 >Error AADSTS50105 - The signed in user is not assigned to a role for the application.
 

support/entra/entra-id/app-integration/error-code-AADSTS75005-not-a-valid-saml-request.md

@@ -1,20 +1,20 @@
 ---
-title: Error AADSTS75005 - The request is not a valid Saml2 protocol message
+title: Error AADSTS75005 - The request isn't a valid Saml2 protocol message
 description: Describes a problem in which you receive AADSTS75005 error when signing in to SAML-based single sign-on configured app.
 ms.date: 08/26/2022
 ms.reviewer: bernawy
 ms.service: entra-id
 ms.custom: sap:Issues Signing In to Applications
 ---
-# Error AADSTS75005 - The request is not a valid Saml2 protocol message
+# Error AADSTS75005 - The request isn't a valid Saml2 protocol message
 
 ## Summary
 
-This article describes a problem in which you receive the error message "Error AADSTS75005 - The request is not a valid Saml2 protocol message." when you try to sign into an apapplication that has been integrated with Microsoft Entra ID.
+This article describes a problem in which you receive the error message "Error AADSTS75005 - The request isn't a valid Saml2 protocol message." when you try to sign into an application that has been integrated with Microsoft Entra ID.
 
 ## Symptoms
 
-You receive error `AADSTS75005` when trying to sign into an application that has been set up to use Microsoft Entra ID for identity management using SAML-based SSO.
+You receive error `AADSTS75005` when trying to sign into an application that has been set up to use Microsoft Entra ID for identity management using SAML-based single sign-on (SSO).
 
 ## Cause
 

support/entra/entra-id/app-integration/reply-url-redirected-to-localhost.md

@@ -14,18 +14,18 @@ This article describes a problem in which Microsoft Entra ID is sending the toke
 
 ## Symptoms
 
-During single sign-on, if the sign-in request does not contain an explicit reply URL (Assertion Consumer Service URL) then Microsoft Entra ID will select any of the configured reply URLs for that application. Even if the application has an explicit reply URL configured, the user may be to redirected `https://127.0.0.1:444`.
+During single sign-on, if the sign-in request doesn't contain an explicit reply URL (Assertion Consumer Service URL) then Microsoft Entra ID selects any of the configured reply URLs for that application. Even if the application has an explicit reply URL configured, the user might be to redirected `https://127.0.0.1:444`.
 
 When the application was added as a non-gallery app, Microsoft Entra ID created this reply URL as a default value. This behavior has changed and Microsoft Entra no longer adds this URL by default.
 
 ## Cause
 
-The user has not been granted access to the application in Microsoft Entra ID.
+The user hasn't been granted access to the application in Microsoft Entra ID.
 
 ## Resolution
 
 Delete the unused reply URLs configured for the application.
 
-On the SAML-based SSO configuration page, in the **Reply URL (Assertion Consumer Service URL)** section, delete unused or default Reply URLs created by the system. For example, `https://127.0.0.1:444/applications/default.aspx`.
+On the SAML-based single sign-on (SSO) configuration page, in the **Reply URL (Assertion Consumer Service URL)** section, delete unused, or default Reply URLs created by the system. For example, `https://127.0.0.1:444/applications/default.aspx`.
 
 

support/entra/entra-id/app-integration/troubleshoot-sign-in-saml-based-apps.md

@@ -1,38 +1,38 @@
 ---
-title: Problems signing in to SAML-based Single Sign-On configured apps
-description: Guidance for the specific errors when signing into an application you have configured for SAML-based federated Single Sign-On with Microsoft Entra ID.
+title: Problems signing in to SAML-based single sign-on configured apps
+description: Guidance for the specific errors when signing into an application you have configured for SAML-based federated single sign-on with Microsoft Entra ID.
 ms.date: 07/18/2023
 ms.reviewer: bernawy
 ms.service: entra-id
 ms.custom: sap:Issues Signing In to Applications
 ---
 
-# Problems signing in to SAML-based Single Sign-On configured apps
+# Problems signing in to SAML-based single sign-on configured apps
 
 ## Summary
 
-This article provides guidance on resolving problems signing in to SAML-based Single Sign-On configured apps.
+This article provides guidance on resolving problems signing in to SAML-based single sign-on configured apps.
 
 ## Resolution
 
-To troubleshoot the sign-in issues below, we recommend the following to better diagnosis and automate the resolution steps:
+To troubleshoot these sign-in issues, we recommend the following to better diagnosis and automate the resolution steps:
 
 - Install the [My Apps Secure Browser Extension](/azure/active-directory/manage-apps/my-apps-deployment-plan) to help Microsoft Entra ID to provide better diagnosis and resolutions when using the testing experience in the Azure portal.
-- Reproduce the error using the testing experience in the app configuration page in the Azure portal. Learn more on [Debug SAML-based Single Sign-On applications](/azure/active-directory/manage-apps/debug-saml-sso-issues)
+- Reproduce the error using the testing experience in the app configuration page in the Azure portal. Learn more on [Debug SAML-based single sign-on applications](/azure/active-directory/manage-apps/debug-saml-sso-issues)
 
-If you use the [testing experience](/azure/active-directory/manage-apps/debug-saml-sso-issues) in the Azure portal with the My Apps Secure Browser Extension, you don't need to manually follow the steps below to open the SAML-based Single Sign-On configuration page.
+If you use the [testing experience](/azure/active-directory/manage-apps/debug-saml-sso-issues) in the Azure portal with the My Apps Secure Browser Extension, you don't need to manually follow these steps to open the SAML-based single sign-on configuration page.
 
-To open the SAML-based Single Sign-On configuration page:
+To open the SAML-based single sign-on configuration page:
 
 1. Open the [**Azure portal**](https://portal.azure.com/) and sign in as a **Global Administrator** or **Coadmin**.
 1. Open the **Microsoft Entra Extension** by selecting **All services** at the top of the main left-hand navigation menu.
 1. Type **“Microsoft Entra ID"** in the filter search box and select the **Microsoft Entra ID** item.
 1. Select **Enterprise Applications** from the Microsoft Entra left-hand navigation menu.
 1. Select **All Applications** to view a list of all your applications.
 
-    If you do not see the application you want show up here, use the **Filter** control at the top of the **All Applications List** and set the **Show** option to **All Applications**.
+    If you don't see the application you want to show up here, use the **Filter** control at the top of the **All Applications List** and set the **Show** option to **All Applications**.
 
-1. Select the application you want to configure for Single Sign-On.
+1. Select the application you want to configure for single sign-on.
 1. Once the application loads, select **Single Sign-On** from the application’s left-hand navigation menu.
 1. Select SAML-based SSO.