Merge pull request #220566 from WilliamDAssafMSFT/patch-3

20221206 correct link phrasing

Author: prmerger-automator[bot]

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-troubleshoot-connectivity.md

@@ -22,11 +22,11 @@ Check to see if the service is available. In the Azure portal, go to the dedicat
 
 ![Select Resource health](./media/sql-data-warehouse-troubleshoot-connectivity/diagnostics-link.png)
 
-The status of your dedicated SQL pool  (formerly SQL DW) will be shown here. If the service isn't showing as **Available**, check further steps.
+The status of your dedicated SQL pool (formerly SQL DW) will be shown here. If the service isn't showing as **Available**, check further steps.
 
 ![Service Available](./media/sql-data-warehouse-troubleshoot-connectivity/resource-health.png)
 
-Additional information about Resource Health can be found [here](/articles/service-health/resource-health-overview.md).
+For more information, see [Resource Health](/articles/service-health/resource-health-overview.md).
 
 ## Check for paused or scaling operation
 
@@ -42,11 +42,11 @@ Otherwise, check with your IT administrator to verify that this maintenance isn'
 
 ## Check your firewall settings
 
-The dedicated SQL pool (formerly SQL DW) database communicates over port 1433.  If you're trying to connect from within a corporate network, outbound traffic over port 1433 might not be allowed by your network's firewall. In that case, you can't connect to your [logical server](/azure/azure-sql/database/logical-servers) unless your IT department opens port 1433. Additional information on firewall configurations can be found [here](/azure/azure-sql/database/firewall-configure?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#create-and-manage-ip-firewall-rules).
+The dedicated SQL pool (formerly SQL DW) database communicates over port 1433.  If you're trying to connect from within a corporate network, outbound traffic over port 1433 might not be allowed by your network's firewall. In that case, you can't connect to your [logical server](/azure/azure-sql/database/logical-servers) unless your IT department opens port 1433. For more information, see [firewall configurations](/azure/azure-sql/database/firewall-configure?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#create-and-manage-ip-firewall-rules).
 
 ## Check your VNet/Service Endpoint settings
 
-If you're receiving Errors 40914 and 40615, see [error description and resolution here](/azure/azure-sql/database/vnet-service-endpoint-rule-overview?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#errors-40914-and-40615).
+If you're receiving Errors 40914 and 40615, see [vNET service endpoint rules](/azure/azure-sql/database/vnet-service-endpoint-rule-overview?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#errors-40914-and-40615).
 
 ## Check for the latest drivers
 
@@ -69,7 +69,7 @@ Check to make sure you're using the latest driver versions.  Using an older ve
 
 ## Check your connection string
 
-Check to make sure your connection strings are set properly.  Below are some samples.  You can find additional information around [connection strings here](sql-data-warehouse-connection-strings.md).
+Check to make sure your connection strings are set properly.  Below are some samples. For more information, see [connection strings](sql-data-warehouse-connection-strings.md).
 
 ADO.NET connection string
 
@@ -101,7 +101,7 @@ Check to see if you're experiencing heavy load on the server with a high number
 
 ## Common error messages
 
-Errors 40914 and 40615, see the [error description and resolution here](/azure/azure-sql/database/vnet-service-endpoint-rule-overview?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#errors-40914-and-40615).
+For more information on errors 40914 and 40615, refer to [vNet service endpoint rules](/azure/azure-sql/database/vnet-service-endpoint-rule-overview?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json#errors-40914-and-40615).
 
 ## Still having connectivity issues?