Update use-managed-identity.md

TomGeske · web-flow · commit d81289005c5b · 2020-04-23T09:38:05.000+02:00
removed Service term as suggested.
diff --git a/articles/aks/use-managed-identity.md b/articles/aks/use-managed-identity.md
@@ -57,7 +57,7 @@ A successful cluster creation using managed identities contains this service pri
 > [!NOTE]
 > For creating and using your own VNet, static IP address, or attached Azure disk where the resources are outside of the MC_* resource group, use the PrincipalID of the cluster System Assigned Managed Identity to perform a role assignment. For more information on role assignment, see [Delegate access to other Azure resources](kubernetes-service-principal.md#delegate-access-to-other-azure-resources).
 >
-> Permission grants to cluster Managed Service Identity used by Azure Cloud provider may take up 60 minutes to populate.
+> Permission grants to cluster Managed Identity used by Azure Cloud provider may take up 60 minutes to populate.
 
 Finally, get credentials to access the cluster:
 

Original file line number	Diff line number	Diff line change
`@@ -57,7 +57,7 @@ A successful cluster creation using managed identities contains this service pri`
`57`	`57`	`> [!NOTE]`
`58`	`58`	`> For creating and using your own VNet, static IP address, or attached Azure disk where the resources are outside of the MC_* resource group, use the PrincipalID of the cluster System Assigned Managed Identity to perform a role assignment. For more information on role assignment, see [Delegate access to other Azure resources](kubernetes-service-principal.md#delegate-access-to-other-azure-resources).`
`59`	`59`	`>`
`60`		`-> Permission grants to cluster Managed Service Identity used by Azure Cloud provider may take up 60 minutes to populate.`
	`60`	`+> Permission grants to cluster Managed Identity used by Azure Cloud provider may take up 60 minutes to populate.`
`61`	`61`
`62`	`62`	`Finally, get credentials to access the cluster:`
`63`	`63`