Update spell

Author: jess-hu-340

articles/data-factory/connector-troubleshoot-azure-data-lake.md

@@ -114,7 +114,7 @@ This article provides suggestions to troubleshoot common problems with the Azure
 
 - **Cause**: There are two possible causes:
 
-    1. The integration runtime is blocked by network access in Azure Storage account firewall settings.
+    1. The integration runtime is blocked by network access in Azure storage account firewall settings.
     2. The service principal or managed identity doesn’t have enough permission to access the data.
 
 - **Recommendation**:
@@ -123,11 +123,11 @@ This article provides suggestions to troubleshoot common problems with the Azure
 
     1. If you have enabled selected virtual networks and IP addresses in your Azure storage account network setting:
 
-        1. It's possible because some IP address ranges of your integration runtime are not allowed by your storage account firewall settings. Add the Azure integration runtime IP addresses or the self-hosted integration runtime IP address to your storage account firewall. For Azure integration runtime IP addresses, see  [Azure Integration Runtime IP addresses](azure-integration-runtime-ip-addresses.md), and to learn how to add IP ranges in storage account firewall,   see [Managing IP network rules](../storage/common/storage-network-security.md#managing-ip-network-rules).
+        1. It's possible because some IP address ranges of your integration runtime are not allowed by your storage account firewall settings. Add the Azure integration runtime IP addresses or the self-hosted integration runtime IP address to your storage account firewall. For Azure integration runtime IP addresses, see  [Azure Integration Runtime IP addresses](azure-integration-runtime-ip-addresses.md), and to learn how to add IP ranges in the storage account firewall,   see [Managing IP network rules](../storage/common/storage-network-security.md#managing-ip-network-rules).
 
-        1. If you allow trusted Azure services to access this storage account in the firewall, you must use [System-assigned managed identity authentication](connector-azure-data-lake-storage.md#managed-identity) in copy activity.
+        1. If you allow trusted Azure services to access this storage account in the firewall, you must use [managed identity authentication](connector-azure-data-lake-storage.md#managed-identity) in copy activity.
 
-         For more information about the Azure Storage account firewalls settings, see [Configure Azure Storage firewalls and virtual networks](../storage/common/storage-network-security.md).
+         For more information about the Azure storage account firewalls settings, see [Configure Azure Storage firewalls and virtual networks](../storage/common/storage-network-security.md).
 
     1. If you use service principal or managed identity authentication, grant service principal or managed identity appropriate permissions to do copy. For source, at least the **Storage Blob Data Reader** role. For sink, at least the **Storage Blob Data Contributor** role. For more information, see [Copy and transform data in Azure Data Lake Storage Gen2](connector-azure-data-lake-storage.md#service-principal-authentication).