Merge pull request #108998 from TimShererWithAquent/us1679050as

Change SSL to TLS per 1679050

Author: PRMerger18

articles/search/search-howto-connecting-azure-sql-iaas-to-azure-search-using-indexers.md

@@ -35,13 +35,13 @@ Azure Cognitive Search requires an encrypted channel for all indexer requests ov
    * In regedit, browse to this registry key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\[MSSQL13.MSSQLSERVER]\MSSQLServer\SuperSocketNetLib\Certificate`.
 
      The `[MSSQL13.MSSQLSERVER]` part varies based on version and instance name. 
-   * Set the value of the **Certificate** key to the **thumbprint** of the SSL certificate you imported to the VM.
+   * Set the value of the **Certificate** key to the **thumbprint** of the TLS/SSL certificate you imported to the VM.
 
      There are several ways to get the thumbprint, some better than others. If you copy it from the **Certificates** snap-in in MMC, you will probably pick up an invisible leading character [as described in this support article](https://support.microsoft.com/kb/2023869/), which results in an error when you attempt a connection. Several workarounds exist for correcting this problem. The easiest is to backspace over and then retype the first character of the thumbprint to remove the leading character in the key value field in regedit. Alternatively, you can use a different tool to copy the thumbprint.
 
 3. Grant permissions to the service account. 
 
-    Make sure the SQL Server service account is granted appropriate permission on the private key of the SSL certificate. If you overlook this step, SQL Server will not start. You can use the **Certificates** snap-in or **CertUtils** for this task.
+    Make sure the SQL Server service account is granted appropriate permission on the private key of the TLS/SSL certificate. If you overlook this step, SQL Server will not start. You can use the **Certificates** snap-in or **CertUtils** for this task.
 
 4. Restart the SQL Server service.