Final markups

Author: Kishan Odedra

articles/operator-insights/managed-identity.md

@@ -41,7 +41,7 @@ You use Microsoft Entra ID to manage user-assigned managed identities. For more
 
 Azure Operator Insights Data Products don't support system-assigned managed identities.
 
-Azure Operator Insights ingestion agents on Azure VMs support system-assigned managed identites, see [Use a managed identity for authentication](set-up-ingestion-agent.md#use-a-managed-identity-for-authentication).
+Azure Operator Insights ingestion agents on Azure VMs support system-assigned managed identities. See [Use a managed identity for authentication](set-up-ingestion-agent.md#use-a-managed-identity-for-authentication).
 
 ## Related content
 

articles/operator-insights/set-up-ingestion-agent.md

@@ -49,7 +49,7 @@ Links to the current and previous releases of the agents are available below the
 The ingestion agent must be able to authenticate with the Azure Key Vault created by the Data Product to retrieve storage credentials. The method of authentication can either be:
 
 - Service principal with certificate credential. This must be used if the ingestion agent is running outside of Azure, such as an on-premises network. 
-- Managed identity. This can be used as an alternative to a service principal if the ingestion agent is running on an Azure VM, it removes the need to handle any credentials.
+- Managed identity. If the ingestion agent is running on an Azure VM, we recommend this method. It does not require handling any credentials (unlike a service principal).
 
 > [!IMPORTANT]
 > You may need a Microsoft Entra tenant administrator in your organization to perform this setup for you.