Updates to active voice for clarity.

Author: kenwith

articles/active-directory/app-provisioning/how-provisioning-works.md

@@ -230,7 +230,7 @@ The table describes how you can configure deprovisioning actions with the Azure
 
 **Known limitations**
 
-* When a user or group is unassigned from an app and no longer managed with the provisioning service then a disable request is sent. At that point, the user isn't managed by the service and a delete request isn't sent when the user is deleted from the directory.
+* When a user or group is unassigned from an app and no longer managed with the provisioning service, a disable request is sent. At that point, the service doesn't manage the user and a delete request isn't sent when the user is deleted from the directory.
 * Provisioning a user that is disabled in Azure AD isn't supported. They must be active in Azure AD before they're provisioned.
 * When a user goes from soft-deleted to active, the Azure AD provisioning service will activate the user in the target app, but won't automatically restore the group memberships. The target application should maintain the group memberships for the user in inactive state. If the target application doesn't support this, you can restart provisioning to update the group memberships.