Update snowflake error code

Author: jess-hu-340

articles/data-factory/connector-troubleshoot-snowflake.md

@@ -17,11 +17,11 @@ ms.custom: has-adal-ref, synapse
 
 This article provides suggestions to troubleshoot common problems with the Snowflake connector in Azure Data Factory and Azure Synapse. 
 
-## Error code: NotAllowToAccessSnowflake.
+## Error code: NotAllowToAccessSnowflake
 
 - **Symptoms**: The copy activity fails with the following error: 
 
-    `Job failed due to reason: net.snowflake.client.jdbc.SnowflakeSQLException: IP % is not allowed to access Snowflake.  Contact your local security administrator. `
+    `IP % is not allowed to access Snowflake. Contact your local security administrator. `
 
 - **Cause**: It's a connectivity issue and usually caused by firewall IP issues when integration runtimes access your Snowflake.  
 
@@ -31,7 +31,7 @@ This article provides suggestions to troubleshoot common problems with the Snowf
     - If you use an Azure Integration Runtime and the access is restricted to IPs approved in the firewall rules, you can add [Azure Integration Runtime IPs](azure-integration-runtime-ip-addresses.md) to the allowed list in Snowflake.
     - If you use a managed private endpoint and a network policy is in place on your Snowflake account, ensure Managed VNet CIDR is allowed. For more steps, refer to [How To: Set up a managed private endpoint from Azure Data Factory or Synapse to Snowflake](https://community.snowflake.com/s/article/How-to-set-up-a-managed-private-endpoint-from-Azure-Data-Factory-or-Synapse-to-Snowflake). 
 
-## Error code: SnowflakeFailToAccess .
+## Error code: SnowflakeFailToAccess
 
 - **Symptoms**:<br>
 The copy activity fails with the following error when using Snowflake as source:<br> 
@@ -43,8 +43,8 @@ The copy activity fails with the following error when using Snowflake as sink:<b
 
 - **Recommendation**: Check your source/sink to make sure that you have granted proper access permission to Snowflake. 
 
-    - Direct copy: Make sure to grant access permission to Snowflake in the other source/sink. Currently, Azure Data Factory only supports Azure Blob storage as source or sink using shared access signature authentication. When you generate the shared access signature, make sure to set the allowed permissions and IP addresses to Snowflake in the staging Azure Blob storage. For more information, see this [article](https://docs.snowflake.com/en/user-guide/data-load-azure-config.html#option-2-generating-a-sas-token). 
-    - Staged copy: The staging Azure Blob storage linked service must use shared access signature authentication. When you generate the shared access signature, make sure to set the allowed permissions and IP addresses to Snowflake in the staging Azure Blob storage. For more information, see this [article](https://docs.snowflake.com/en/user-guide/data-load-azure-config.html#option-2-generating-a-sas-token).
+    - Direct copy: Make sure to grant access permission to Snowflake in the other source/sink. Currently, only Azure Blob Storage that uses shared access signature authentication is supported as source or sink. When you generate the shared access signature, make sure to set the allowed permissions and IP addresses to Snowflake in the Azure Blob Storage. For more information, see this [article](https://docs.snowflake.com/en/user-guide/data-load-azure-config.html#option-2-generating-a-sas-token). 
+    - Staged copy: The staging Azure Blob Storage linked service must use shared access signature authentication. When you generate the shared access signature, make sure to set the allowed permissions and IP addresses to Snowflake in the staging Azure Blob Storage. For more information, see this [article](https://docs.snowflake.com/en/user-guide/data-load-azure-config.html#option-2-generating-a-sas-token).
 
 ## Next steps