Merge pull request #186650 from MicrosoftGuyJFlo/HybridNonBlockingFixes

[Azure AD] Devices - Fixes

Author: PRMerger15

articles/active-directory/devices/howto-hybrid-azure-ad-join.md

@@ -121,7 +121,7 @@ With Windows 10 1803 or newer, if instantaneous hybrid Azure AD join for a feder
 
 Organizations can test hybrid Azure AD join on a subset of their environment before a full rollout. The steps to complete a targeted deployment can be found in the article [Hybrid Azure AD join targeted deployment](hybrid-azuread-join-control.md). Organizations should include a sample of users from varying roles and profiles in this pilot group. A targeted rollout will help identify any issues your plan may not have addressed before you enable for the entire organization.
 
-Some organizations may not be able to use Azure AD Connect to configure AD FS, the steps to configure the claims manually can be found in the article [Configure hybrid Azure Active Directory join manually](hybrid-azuread-join-manual.md).
+Some organizations may not be able to use Azure AD Connect to configure AD FS. The steps to configure the claims manually can be found in the article [Configure hybrid Azure Active Directory join manually](hybrid-azuread-join-manual.md).
 
 ### Government cloud
 

articles/active-directory/devices/howto-hybrid-join-verify.md

@@ -32,8 +32,8 @@ For downlevel devices, see the article [Troubleshooting hybrid Azure Active Dire
 
 1. Go to the devices page using a [direct link](https://portal.azure.com/#blade/Microsoft_AAD_IAM/DevicesMenuBlade/Devices).
 2. Information on how to locate a device can be found in [How to manage device identities using the Azure portal](./device-management-azure-portal.md).
-3. If the **Registered** column says **Pending**, then hybrid Azure AD Join hasn't completed. In federated environments, this state happens only if it failed to register and Azure AD Connect is configured to sync the devices.
-4. If the **Registered** column contains a **date/time**, then hybrid Azure AD Join has completed.
+3. If the **Registered** column says **Pending**, then hybrid Azure AD join hasn't completed. In federated environments, this state happens only if it failed to register and Azure AD Connect is configured to sync the devices.
+4. If the **Registered** column contains a **date/time**, then hybrid Azure AD join has completed.
 
 ## Using PowerShell
 

articles/active-directory/devices/plan-device-deployment.md

@@ -195,7 +195,7 @@ If hybrid Azure AD join is the best option for your organization, see the follow
 If installing the required version of Azure AD Connect isn't an option for you, see [how to manually configure hybrid Azure AD join](hybrid-azuread-join-manual.md). 
 
 > [!NOTE] 
-> The on-premises domain-joined Windows 10 device attempts to auto-join to Azure AD to become hybrid Azure AD joined by default. This will only succeed if you haves set up the right environment. 
+> The on-premises domain-joined Windows 10 device attempts to auto-join to Azure AD to become hybrid Azure AD joined by default. This will only succeed if you have set up the right environment. 
 
 You may determine that hybrid Azure AD join is the best solution for a device in a different state. The following table shows how to change the state of a device.