Pencil edit: Acrolinx: correct numerous typos and branding errors

Author: denrea

articles/active-directory/hybrid/reference-connect-health-faq.yml

@@ -49,7 +49,7 @@ sections:
           * The first Connect Health Agent requires at least one Azure AD Premium (P1 or P2) license.
           * Each additional registered agent requires 25 more Azure AD Premium (P1 or P2) licenses.
           * Agent count is equivalent to the total number of agents that are registered across all monitored roles (AD FS, Azure AD Connect, and/or AD DS).
-          * AAD Connect Health licensing doesn't require you to assign the license to specific users. You only need to have the requisite number of valid licenses.
+          * Azure AD Connect Health licensing doesn't require you to assign the license to specific users. You only need to have the requisite number of valid licenses.
           
           Licensing information is also found on the [Azure AD Pricing page](https://aka.ms/aadpricing).
           
@@ -72,8 +72,8 @@ sections:
           | ------ | --------------- | --- |
           | Connect Health for Sync | Monitoring / Insight / Alerts / Analysis | No |
           |  | Sync error report | Yes |
-          | Connect Health for ADFS | Monitoring / Insight / Alerts / Analysis | No |
-          | Connect Health for ADDS | Monitoring / Insight / Alerts / Analysis | No |
+          | Connect Health for AD FS | Monitoring / Insight / Alerts / Analysis | No |
+          | Connect Health for AD DS | Monitoring / Insight / Alerts / Analysis | No |
           
           To ensure the agent connectivity of Connect Health for sync, configure the [installation requirement](how-to-connect-health-agent-install.md#outbound-connectivity-to-the-azure-service-endpoints) accordingly.
           
@@ -158,7 +158,7 @@ sections:
           The health agent can fail to register due to the following possible reasons:
           
           * The agent cannot communicate with the required endpoints because a firewall is blocking traffic. This issue is common on web application proxy servers. Make sure that you have allowed outbound communication to the required endpoints and ports. See the [requirements section](how-to-connect-health-agent-install.md#requirements) for details.
-          * Outbound communication is subjected to an TLS inspection by the network layer. This causes the certificate that the agent uses to be replaced by the inspection server/entity, and the steps to complete the agent registration fail.
+          * Outbound communication is subjected to a TLS inspection by the network layer. This causes the certificate that the agent uses to be replaced by the inspection server/entity, and the steps to complete the agent registration fail.
           * The user doesn't have access to perform the registration of the agent. Global admins have access by default. You can use [Azure role-based access control (Azure RBAC)](how-to-connect-health-operations.md#manage-access-with-azure-rbac) to delegate access to other users.
           
       - question: |
@@ -217,19 +217,19 @@ sections:
           ```
           
       - question: |
-          Why does the PowerShell cmdlet 'Get-MsolDirSyncProvisioningError' show less sync errors in the result?
+          Why does the PowerShell cmdlet 'Get-MsolDirSyncProvisioningError' show fewer sync errors in the result?
         answer: |
           <i>Get-MsolDirSyncProvisioningError</i> will only return DirSync provisioning errors. The Connect Health portal also shows other sync error types such as export errors. Read more about [Azure AD Connect Sync errors](./tshoot-connect-sync-errors.md).
           
       - question: |
-          Why are my ADFS audits not being generated?
+          Why are my AD FS audits not being generated?
         answer: |
-          Please use the PowerShell cmdlet <i>Get-AdfsProperties -AuditLevel</i> to ensure audit logs aren't in disabled state. Read more about [ADFS audit logs](/windows-server/identity/ad-fs/technical-reference/auditing-enhancements-to-ad-fs-in-windows-server#auditing-levels-in-ad-fs-for-windows-server-2016). Notice if there are advanced audit settings pushed to the ADFS server, any changes with auditpol.exe will be overwritten (event if Application Generated isn't configured). In this case, set the local security policy to log Application Generated failures and success.
+          Please use the PowerShell cmdlet <i>Get-AdfsProperties -AuditLevel</i> to ensure audit logs aren't in disabled state. Read more about [AD FS audit logs](/windows-server/identity/ad-fs/technical-reference/auditing-enhancements-to-ad-fs-in-windows-server#auditing-levels-in-ad-fs-for-windows-server-2016). Notice if there are advanced audit settings pushed to the AD FS server, any changes with auditpol.exe will be overwritten (event if Application Generated isn't configured). In this case, set the local security policy to log Application Generated failures and success.
           
       - question: |
-          When will the agent certificate be automatic renewed before expiration?
+          When will the agent certificate be automatically renewed before expiration?
         answer: |
-          The agent certification will be automatic renewed **6 months** before its expiration date. If it isn't renewed, ensure the network connection of the agent is stable. Restart the agent services or update to the latest version may also solve the issue.
+          The agent certification will be automatically renewed **6 months** before its expiration date. If it isn't renewed, ensure the network connection of the agent is stable. Restart the agent services or update to the latest version may also solve the issue.
           
 additionalContent: |