improve acrolynx score

Author: omondiatieno

articles/active-directory/manage-apps/prevent-domain-hints-with-home-realm-discovery.md

@@ -20,12 +20,12 @@ zone_pivot_groups: home-realm-discovery
 Home Realm Discovery Policy (HRD) offers administrators multiple ways to control how and where their users authenticate. The `domainHintPolicy` section of the HRD policy is used to help migrate federated users to cloud managed credentials like [FIDO](../authentication/howto-authentication-passwordless-security-key.md), by ensuring that they always visit the Azure AD sign-in page and aren't auto-accelerated to a federated IDP because of domain hints. To learn more about HRD policy, see [Home Realm Discovery](home-realm-discovery-policy.md).
 
 
-This policy is needed in situations where and admins can't control or update domain hints during sign-in.  For example, `outlook.com/contoso.com` sends the user to a login page with the `&domain_hint=contoso.com` parameter appended, to auto-accelerate the user directly to the federated IDP for the `contoso.com` domain. Users with managed credentials sent to a federated IDP can't sign in using their managed credentials, reducing security, and frustrating users with randomized sign-in experiences. Admins rolling out managed credentials [should also set up this policy](#suggested-use-within-a-tenant) to ensure that users can always use their managed credentials.
+This policy is needed in situations where and admins can't control or update domain hints during sign-in.  For example, `outlook.com/contoso.com` sends the user to a sign-in page with the `&domain_hint=contoso.com` parameter appended, to auto-accelerate the user directly to the federated IDP for the `contoso.com` domain. Users with managed credentials sent to a federated IDP can't sign in using their managed credentials, reducing security, and frustrating users with randomized sign-in experiences. Admins rolling out managed credentials [should also set up this policy](#suggested-use-within-a-tenant) to ensure that users can always use their managed credentials.
 
 
 ## DomainHintPolicy details
 
-The DomainHintPolicy section of the HRD policy is a JSON object, that allows an admin to opt out certain domains and applications from domain hint usage.  Functionally, this tells the Azure AD sign-in page to behave as if a `domain_hint` parameter on the login request wasn't present.
+The DomainHintPolicy section of the HRD policy is a JSON object that allows an admin to opt out certain domains and applications from domain hint usage.  Functionally, this tells the Azure AD sign-in page to behave as if a `domain_hint` parameter on the sign-in request wasn't present.
 
 ### The Respect and Ignore policy sections
 
@@ -40,11 +40,11 @@ The DomainHintPolicy section of the HRD policy is a JSON object, that allows an
 
 The DomainHintPolicy logic runs on each incoming request that contains a domain hint and accelerates based on two pieces of data in the request – the domain in the domain hint, and the client ID (the app). In short - "Respect" for a domain or app takes precedence over an instruction to "Ignore" a domain hint for a given domain or application.
 
-- In the absence of any domain hint policy, or if none of the 4 sections reference the app or domain hint mentioned, [the rest of the HRD policy will be evaluated](home-realm-discovery-policy.md#priority-and-evaluation-of-hrd-policies).
-- If either one (or both) of `RespectDomainHintForApps` or `RespectDomainHintForDomains` section includes the app or domain hint in the request, then the user will be auto-accelerated to the federated IDP as requested.
-- If either one (or both) of `IgnoreDomainHintsForApps` or `IgnoreDomainHintsForDomains` references the app or the domain hint in the request, and they’re not referenced by the “Respect” sections, then the request won't be auto-accelerated, and the user will remain at the Azure AD login page to provide a username.
+- In the absence of any domain hint policy, or if none of the four sections reference the app or domain hint mentioned, [the rest of the HRD policy will be evaluated](home-realm-discovery-policy.md#priority-and-evaluation-of-hrd-policies).
+- If either one (or both) of `RespectDomainHintForApps` or `RespectDomainHintForDomains` section includes the app or domain hint in the request, then the user is auto-accelerated to the federated IDP as requested.
+- If either one (or both) of `IgnoreDomainHintsForApps` or `IgnoreDomainHintsForDomains` references the app or the domain hint in the request, and they’re not referenced by the “Respect” sections, then the request won't be auto-accelerated, and the user remains at the Azure AD sign-in page to provide a username.
 
-Once a user has entered a username at the login page, they can use their managed credentials.  If they choose not to use a managed credential, or they have none registered, they'll be taken to their federated IDP for credential entry as usual.
+Once a user has entered a username at the sign-in page, they can use their managed credentials.  If they choose not to use a managed credential, or they have none registered, they are taken to their federated IDP for credential entry as usual.
 
 ## Prerequisites
 
@@ -60,7 +60,7 @@ To disable auto-acceleration sign-in for an application in Azure AD, you need:
 
 Admins of federated domains should set up this section of the HRD policy in a four-phase plan. The goal of this plan is to eventually get all users in a tenant to use their managed credentials regardless of domain or application, save those apps that have hard dependencies on `domain_hint` usage.  This plan helps admins find those apps, exempt them from the new policy, and continue rolling out the change to the rest of the tenant.
 
-1. Pick a domain to initially roll this change out to.  This will be your test domain, so pick one that may be more receptive to changes in UX (For example, seeing a different login page).  This will ignore all domain hints from all applications that use this domain name. Set this policy in your tenant-default HRD policy:
+1. Pick a domain to initially roll this change out to.  This is your test domain, so pick one that may be more receptive to changes in UX (For example, seeing a different sign-in page). This ignores all domain hints from all applications that use this domain name. Set this policy in your tenant-default HRD policy:
 
 ::: zone pivot="graph-hrd"
 
@@ -168,7 +168,7 @@ New-AzureADPolicy
 
 ::: zone-end
 
-After step 4 is complete all users, except those in `guestHandlingDomain.com`, can sign-in at the Azure AD sign-in page even when domain hints would otherwise cause an auto-acceleration to a federated IDP.  The exception to this is if the app requesting sign-in is one of the exempted ones - for those apps, all domain hints will still be accepted.
+After step 4 is complete all users, except those in `guestHandlingDomain.com`, can sign-in at the Azure AD sign-in page even when domain hints would otherwise cause an auto-acceleration to a federated IDP.  The exception to this is if the app requesting sign-in is one of the exempted ones - for those apps, all domain hints are still accepted.
 
 ::: zone pivot="graph-hrd"