update verbs

Author: markwahl-msft

articles/active-directory/app-provisioning/on-premises-ecma-troubleshoot.md

@@ -153,7 +153,7 @@ The ECMA Host has a cache of users in your application that is updated according
 ## Target attribute is missing 
 The provisioning service automatically discovers attributes in your target application. If you see that a target attribute is missing in the target attribute list in the Azure portal, perform the following troubleshooting step:
 
- 1. Review the **Select Attributes** page of your ECMA host configuration to check that the attribute has been selected, so that it will exposed to the Azure portal.
+ 1. Review the **Select Attributes** page of your ECMA host configuration to check that the attribute has been selected, so that it will be exposed to the Azure portal.
  1. Ensure that the ECMA host service is running.
  1. Review the ECMA host logs to check that a /schemas request was made, and review the attributes in the response. This information will be valuable for support to troubleshoot the issue.
 
@@ -186,7 +186,7 @@ After the ECMA Connector Host schema mapping has been configured, start the serv
 
 Requests made by Azure AD to the provisioning agent and connector host use the SCIM protocol. Requests made from the host to apps use the protocol the app supports. The requests from the host to the agent to Azure AD rely on SCIM. You can learn more about the SCIM implementation in [Tutorial: Develop and plan provisioning for a SCIM endpoint in Azure Active Directory](use-scim-to-provision-users-and-groups.md).
 
-The Azure AD provisioning service generally makes a get-user call to check for a [dummy user](use-scim-to-provision-users-and-groups.md#request-3) in three situations: at the beginning of each provisioning cycle, before performing on-demand provisioning and when **test connection** is selected. This check ensure the target endpoint is available and returning SCIM-compliant responses to the Azure AD provisioning service.
+The Azure AD provisioning service generally makes a get-user call to check for a [dummy user](use-scim-to-provision-users-and-groups.md#request-3) in three situations: at the beginning of each provisioning cycle, before performing on-demand provisioning and when **test connection** is selected. This check ensures the target endpoint is available and returning SCIM-compliant responses to the Azure AD provisioning service.
 
 
 ## How do I troubleshoot the provisioning agent?
@@ -272,7 +272,7 @@ By using Azure AD, you can monitor the provisioning service in the cloud and col
 ### I am getting an Invalid LDAP style DN error when trying to configure the ECMA Connector Host with SQL
 By default, the generic SQL connector expects the DN to be populated using the LDAP style (when the 'DN is anchor' attribute is left unchecked in the first connectivity page). In the error message `Invalid LDAP style DN` or `Target Site: ValidByLdapStyle`, you may see that the DN field contains a user principal name (UPN), rather than an LDAP style DN that the connector expects.
 
-To resolve this, ensure that **Autogenerated** is selected on the object types page when you configure the connector.
+To resolve this error message, ensure that **Autogenerated** is selected on the object types page when you configure the connector.
 
 For more information, see [About anchor attributes and distinguished names](on-premises-application-provisioning-architecture.md#about-anchor-attributes-and-distinguished-names).