Update how-to-managed-cluster-application-managed-identity.md

Author: abatishchev

articles/service-fabric/how-to-managed-cluster-application-managed-identity.md

@@ -27,7 +27,7 @@ Sample managed cluster templates are available here: [Service Fabric managed clu
 When a Service Fabric application is configured with [Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md) and deployed to the cluster it will trigger automatic configuration of the *Managed Identity Token Service* on the Service Fabric managed cluster. This service is responsible for the authentication of Service Fabric applications using their managed identities, and for obtaining access tokens on their behalf. Once the service is enabled, you can see it in Service Fabric Explorer under the **System** section in the left pane, running under the name **fabric:/System/ManagedIdentityTokenService**.
 
 >[!NOTE]
->The first time an application is deployed with Managed Identities you should expect to see a one-time longer deployment due to the automatic cluster configuration change. You should expect this to take from 15 minutes for a zonal cluster to 45 minutes for a zone-spanning cluster. If there are any other deployments in flight, MITS configuration will wait for those to complete first.
+>The first time an application is deployed with Managed Identities you should expect to see a one-time longer deployment due to the automatic cluster configuration change. You should expect this to take from 15 minutes for a zonal cluster to 45 minutes for a zone-spanning cluster. If there are any other deployments in flight, the Managed Identity configuration will have to wait for those to complete first.
 
 Application resource supports assignment of both SystemAssigned or UserAssigned and assignment can be done as shown in below snippet.