Merge pull request #234164 from ssabat/master

Fixed grammar

Author: prmerger-automator[bot]

articles/data-factory/security-and-access-control-troubleshoot-guide.md

@@ -7,7 +7,7 @@ ms.service: data-factory
 ms.subservice: integration-runtime
 ms.custom: synapse
 ms.topic: troubleshooting
-ms.date: 11/04/2022
+ms.date: 04/11/2023
 ms.author: lle
 ---
 
@@ -64,7 +64,7 @@ You created managed private endpoint from ADF and obtained an approved private e
 
 #### Cause 
 
-Currently, ADF stops pulling private end point status after the it is approved. Hence the status shown in ADF is stale.
+Currently, ADF stops pulling private end point status after it is approved. Hence the status shown in ADF is stale.
 
 ##### Resolution
 
@@ -172,7 +172,7 @@ Try to enable public network access on the user interface, as shown in the follo
 #### Cause
 Both Azure Resource Manager and the service are using the same private zone creating a potential conflict on customer’s private DNS with a scenario where the Azure Resource Manager records will not be found.
 
-#### Solution
+#### Resolution
 1. Find Private DNS zones **privatelink.azure.com** in Azure portal.
 :::image type="content" source="media/security-access-control-troubleshoot-guide/private-dns-zones.png" alt-text="Screenshot of finding Private DNS zones.":::
 2. Check if there is an A record **adf**.
@@ -201,7 +201,7 @@ For example: The Azure Blob Storage sink was using Azure IR (public, not Managed
 
 The service may still use Managed VNet IR, but you could encounter such error because the public endpoint to Azure Blob Storage in Managed VNet is not reliable based on the testing result, and Azure Blob Storage and Azure Data Lake Gen2 are not supported to be connected through public endpoint from the service's Managed Virtual Network according to [Managed virtual network & managed private endpoints](./managed-virtual-network-private-endpoint.md#outbound-communications-through-public-endpoint-from-a-data-factory-managed-virtual-network).
 
-#### Solution
+#### Resolution
 
 - Having private endpoint enabled on the source and also the sink side when using the Managed VNet IR.
 - If you still want to use the public endpoint, you can switch to public IR only instead of using the Managed VNet IR for the source and the sink. Even if you switch back to public IR, the service may still use the Managed VNet IR if the Managed VNet IR is still there.
@@ -215,7 +215,7 @@ The service may still use Managed VNet IR, but you could encounter such error be
 
 If you are performing any operations related to CMK, you should complete all operations related to the service first, and then external operations (like Managed Identities or Key Vault operations). For example, if you  want to delete all resources, you need to delete the service instance first, and then delete the key vault.  If you delete the key vault first, this error will occur since the service can't read the required objects anymore, and it won't be able to validate if deletion is possible or not. 
 
-#### Solution
+#### Resolution
 
 There are three possible ways to solve the issue. They are as follows: