Merge pull request #109841 from TimShererWithAquent/us1679050cq

Change SSL to TLS per 1679050

Author: PRMerger9

articles/event-hubs/event-hubs-features.md

@@ -42,7 +42,7 @@ Any entity that sends data to an event hub is an event producer, or *event publi
 
 You can publish an event via AMQP 1.0, Kafka 1.0 (and later), or HTTPS. Event Hubs provides [client libraries and classes](event-hubs-dotnet-framework-api-overview.md) for publishing events to an event hub from .NET clients. For other runtimes and platforms, you can use any AMQP 1.0 client, such as [Apache Qpid](https://qpid.apache.org/). You can publish events individually, or batched. A single publication (event data instance) has a limit of 1 MB, regardless of whether it is a single event or a batch. Publishing events larger than this threshold results in an error. It is a best practice for publishers to be unaware of partitions within the event hub and to only specify a *partition key* (introduced in the next section), or their identity via their SAS token.
 
-The choice to use AMQP or HTTPS is specific to the usage scenario. AMQP requires the establishment of a persistent bidirectional socket in addition to transport level security (TLS) or SSL/TLS. AMQP has higher network costs when initializing the session, however HTTPS requires additional SSL overhead for every request. AMQP has higher performance for frequent publishers.
+The choice to use AMQP or HTTPS is specific to the usage scenario. AMQP requires the establishment of a persistent bidirectional socket in addition to transport level security (TLS) or SSL/TLS. AMQP has higher network costs when initializing the session, however HTTPS requires additional TLS overhead for every request. AMQP has higher performance for frequent publishers.
 
 ![Event Hubs](./media/event-hubs-features/partition_keys.png)
 

articles/event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md

@@ -41,7 +41,7 @@ When you create a **standard** tier Event Hubs namespace, the Kafka endpoint for
 
 3. Update the configuration details for the producer in `src/main/resources/producer.config` as follows:
 
-    **SSL:**
+    **TLS/SSL:**
 
     ```xml
     bootstrap.servers=NAMESPACENAME.servicebus.windows.net:9093
@@ -71,7 +71,7 @@ When you create a **standard** tier Event Hubs namespace, the Kafka endpoint for
 
 6. Update the configuration details for the consumer in `src/main/resources/consumer.config` as follows:
 
-    **SSL:**
+    **TLS/SSL:**
 
     ```xml
     bootstrap.servers=NAMESPACENAME.servicebus.windows.net:9093