Merge pull request #272068 from spelluru/uuf0412

UUF Feedback issues

Author: prmerger-automator[bot]

articles/event-grid/create-view-manage-namespaces.md

@@ -33,7 +33,7 @@ This article shows you how to use the Azure portal to create, view and manage an
     1. Enter a **name** for the namespace.
     1. Select the region or **location** where you want to create the namespace. 
     1. If the selected region supports availability zones, the **Availability zones** checkbox can be enabled or disabled. The checkbox is selected by default if the region supports availability zones. However, you can uncheck and disable availability zones if needed. The selection cannot be changed once the namespace is created.
-    1. Use the slider or text box to specify the number of **throughput units** for the namespace.
+    1. Use the slider or text box to specify the number of **throughput units** for the namespace. Throughput units (TUs) define the ingress and egress event rate capacity in namespaces.
     1. Select **Next: Networking** at the bottom of the page. 
 
         :::image type="content" source="media/create-view-manage-namespaces/create-namespace-basics-page.png" alt-text="Screenshot showing the Basics tab of Create namespace page.":::        

articles/event-grid/includes/limits.md

@@ -15,7 +15,7 @@ ms.custom: include file, ignite-2023
 
 ## Event Grid throttle limits
 
-Event Grid offers a standard tier and basic tier. Event Grid standard tier enables pub-sub using MQTT broker functionality and pull-delivery of messages through the Event Grid namespace. Event Grid basic tier enables push delivery using Event Grid custom topics, Event Grid system topics, Event domains, and Event Grid partner topics. See [Choose the right Event Grid tier](../choose-right-tier.md). This article describes the quota and limits for both tiers.
+Event Grid offers a standard tier and basic tier. Event Grid standard tier enables pub-sub using Message Queuing Telemetry Transport (MQTT) broker functionality and pull-delivery of messages through the Event Grid namespace. Event Grid basic tier enables push delivery using Event Grid custom topics, Event Grid system topics, Event domains, and Event Grid partner topics. See [Choose the right Event Grid tier](../choose-right-tier.md). This article describes the quota and limits for both tiers.
 
 ## Event Grid Namespace resource limits
 
@@ -32,18 +32,21 @@ The following limits apply to namespace resources in Azure Event Grid.
 
 The following limits apply to MQTT in Azure Event Grid namespace resource.
 
+> [!NOTE]
+> Throughput units (TUs) define the ingress and egress event rate capacity in namespaces. They allow you to control the capacity of your namespace resource for message ingress and egress. 
+
 | Limit description                            | Limit                                                                             |
 |----------------------------------------------|-----------------------------------------------------------------------------------|
-| MQTT sessions per Event Grid namespace               | 10,000 per TU                                                                     |
+| MQTT sessions per Event Grid namespace               | 10,000 per throughput unit (TU)                                                                     |
 | Sessions per Event Grid namespace                       | 10,000 per TU                                                                     |
 | Session Expiry Interval                      | 8 hours, [configurable on the Event Grid namespace](../mqtt-support.md#maximum-session-expiry-interval-configuration)|
-| Inbound MQTT publish requests per Event Grid namespace  | 1,000 messages per second per TU                                                         |
+| Inbound MQTT publishing requests per Event Grid namespace  | 1,000 messages per second per TU                                                         |
 | Inbound MQTT bandwidth per Event Grid namespace         | 1 MB per second per TU                                                            |
-| Inbound MQTT publish requests per session | 100 messages per second                                                           |
+| Inbound MQTT publishing requests per session | 100 messages per second                                                           |
 | Inbound MQTT bandwidth per session        | 1 MB per second                                                                   |
-| Outbound MQTT publish requests per Event Grid namespace | 1,000 messages per second per TU                                                         |
+| Outbound MQTT publishing requests per Event Grid namespace | 1,000 messages per second per TU                                                         |
 | Outbound MQTT bandwidth per Event Grid namespace        | 1 MB per second per TU                                                            |
-| Outbound MQTT publish requests per session| 100 messages per second                                                           |
+| Outbound MQTT publishing requests per session| 100 messages per second                                                           |
 | Outbound MQTT bandwidth per session       | 1 MB per second                                                                   |
 | Max message size                             | 512 KB                                                                            |
 | Segments per topic/ topic filter             | 8                                                                                 |
@@ -93,7 +96,7 @@ The following limits apply to Azure Event Grid custom topic, system topic, and p
 |--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|
 | Custom topics per Azure subscription                   | 100<br/>When the limit is reached, you can consider a different region or consider using domains, which can support 100,000 topics. |
 | Event subscriptions per topic                          | 500<br/>This limit can’t be increased.                                                                                              |
-| Publish rate for a custom or a partner topic (ingress) | 5,000 events of 64 KB size per second or 5 MB per second (whichever comes first). An event is counted for limits and pricing purposes as a 64KB data chunk. So, if the event is 128KB, it counts as two events. |
+| Publish rate for a custom or a partner topic (ingress) | 5,000 events of 64 KB size per second or 5 MB per second (whichever comes first). An event is counted for limits and pricing purposes as a 64KB data chunk. So, if the event is 128 KB, it counts as two events. |
 | Event size                                             | 1 MB<br/>This limit can’t be increased.                                                                                             |
 | Maximum event retention on topics              | 1 day. This limit can't be increased. |
 | Number of incoming events per batch                    | 5,000<br/>This limit can’t be increased                                                                                             |
@@ -110,7 +113,7 @@ The following limits apply to Azure Event Grid domain resource.
 | Topics per domain                             | 100,000                                                            |
 | Event subscriptions per topic within a domain | 500<br/>This limit can’t be increased                              |
 | Domain scope event subscriptions              | 50<br/>This limit can’t be increased                               |
-| Publish rate for a domain (ingress)           | 5,000 events of 64 KB size per second or 5 MB per second (whichever comes first). An event is counted for limits and pricing purposes as a 64KB data chunk. So, if the event is 128KB, it counts as two events. |
+| Publish rate for a domain (ingress)           | 5,000 events of 64 KB size per second or 5 MB per second (whichever comes first). An event is counted for limits and pricing purposes as a 64KB data chunk. So, if the event is 128 KB, it counts as two events. |
 | Maximum event retention on domain topics              | 1 day. This limit can't be increased. |
 | Private endpoint connections per domain       | 64                                                                 |
 | IP Firewall rules per topic                   | 128                                                                |