Merge pull request #109671 from TimShererWithAquent/us1679050cj

Change SSL to TLS per 1679050

Author: PRMerger12

articles/sql-database/sql-database-gateway-migration.md

@@ -48,7 +48,7 @@ You will not be impacted if you have :
 
 We recommend that you allow outbound traffic to IP addresses for all the [Azure SQL Database gateway IP addresses](sql-database-connectivity-architecture.md#azure-sql-database-gateway-ip-addresses) in the region on TCP port 1433, and port range 11000-11999. This recomendation is applicable to clients connecting from on-premises and also those connecting via Service Endpoints. For more information on port ranges, see [Connection policy](sql-database-connectivity-architecture.md#connection-policy).
 
-Connections made from applications using Microsoft JDBC Driver below version 4.0 might fail certificate validation. Lower versions of Microsoft JDBC rely on Common Name (CN) in the Subject field of the certificate. The mitigation is to ensure that the hostNameInCertificate property is set to *.database.windows.net. For more information on how to set the hostNameInCertificate property, see [Connecting with SSL Encryption](/sql/connect/jdbc/connecting-with-ssl-encryption).
+Connections made from applications using Microsoft JDBC Driver below version 4.0 might fail certificate validation. Lower versions of Microsoft JDBC rely on Common Name (CN) in the Subject field of the certificate. The mitigation is to ensure that the hostNameInCertificate property is set to *.database.windows.net. For more information on how to set the hostNameInCertificate property, see [Connecting with Encryption](/sql/connect/jdbc/connecting-with-ssl-encryption).
 
 If the above mitigation doesn't work, file a support request for SQL Database using the following URL: https://aka.ms/getazuresupport