Merge pull request #14499 from TimShererWithAquent/us1679050eq

Change SSL to TLS per 1679050

Author: PRMerger20

docs/connect/jdbc/fips-mode.md

@@ -19,7 +19,7 @@ The Microsoft JDBC Driver for SQL Server supports running in JVMs configured to
 #### Prerequisites
 
 - FIPS configured JVM
-- Appropriate SSL Certificate
+- Appropriate TLS/SSL Certificate
 - Appropriate policy files
 - Appropriate Configuration parameters
 
@@ -32,11 +32,11 @@ To see the approved modules for FIPS Configuration, refer to [Validated Modules
 Vendors may have some additional steps to configure a JVM with FIPS.
 
 ## Appropriate SSL certificate
-In order to connect to SQL Server in FIPS mode, a valid SSL Certificate is required. Install or import it into the Java Key Store on the client machine (JVM) where FIPS is enabled.
+In order to connect to SQL Server in FIPS mode, a valid TLS/SSL Certificate is required. Install or import it into the Java Key Store on the client machine (JVM) where FIPS is enabled.
 
 ### Importing SSL certificate in Java keyStore
 For FIPS, most likely you need to import the certificate (.cert) in either PKCS or a provider-specific format.
-Use the following snippet to import the SSL certificate and store it in a working directory with the appropriate KeyStore format. _TRUST\_STORE\_PASSWORD_ is your password for Java KeyStore.
+Use the following snippet to import the TLS/SSL certificate and store it in a working directory with the appropriate KeyStore format. _TRUST\_STORE\_PASSWORD_ is your password for Java KeyStore.
 
 ```java
 public void saveGenericKeyStore(
@@ -66,7 +66,7 @@ private Certificate getCertificate(String pathName)
 }
 ```
 
-The following example is importing an Azure SSL Certificate in PKCS12 format with the BouncyCastle Provider. The certificate is imported in the working directory named _MyTrustStore\_PKCS12_ by using the following snippet:
+The following example is importing an Azure TLS/SSL Certificate in PKCS12 format with the BouncyCastle Provider. The certificate is imported in the working directory named _MyTrustStore\_PKCS12_ by using the following snippet:
 
 `saveGenericKeyStore(BCFIPS, PKCS12, "SQLAzure SSL Certificate Name", "SQLAzure.cer");`
 

docs/database-engine/configure-windows/configure-the-network-packet-size-server-configuration-option.md

@@ -49,7 +49,7 @@ ms.author: mikeray
 -   The maximum network packet size for encrypted connections is 16,383 bytes.  
 
 > [!NOTE]  
-> If MARS is enabled, the SMUX provider will add a 16-byte header to the packet before SSL encryption, reducing the maximum network packet size to 16368 bytes.
+> If MARS is enabled, the SMUX provider will add a 16-byte header to the packet before TLS encryption, reducing the maximum network packet size to 16368 bytes.
    
 ###  <a name="Recommendations"></a> Recommendations  
 

docs/relational-databases/polybase/polybase-configuration.md

@@ -19,7 +19,7 @@ This article provides a reference for various configuration settings that affect
 
 ## <a id="rpcprotection"></a> Hadoop.RPC.Protection setting
 
-A common way to secure communication in a hadoop cluster is by changing the hadoop.rpc.protection configuration to 'Privacy' or 'Integrity'. By default, PolyBase assumes the configuration is set to 'Authenticate'. To override this default, add the following property to the core-site.xml file. Changing this configuration will enable secure data transfer among the hadoop nodes and SSL connection to SQL Server.
+A common way to secure communication in a hadoop cluster is by changing the hadoop.rpc.protection configuration to 'Privacy' or 'Integrity'. By default, PolyBase assumes the configuration is set to 'Authenticate'. To override this default, add the following property to the core-site.xml file. Changing this configuration will enable secure data transfer among the hadoop nodes and TLS connection to SQL Server.
 
 ```xml
 <!-- RPC Encryption information, PLEASE FILL THESE IN ACCORDING TO HADOOP CLUSTER CONFIG -->