Merge pull request #295397 from EldertGrootenboer/patch-5

Update service-bus-quotas-table.md

Author: prmerger-automator[bot]

includes/service-bus-quotas-table.md

@@ -14,8 +14,8 @@ The following table lists quota information specific to Azure Service Bus messag
 | --- | --- | --- | --- |
 | Maximum number of namespaces per Azure subscription |Namespace |  1000 (default and maximum) | This limit is based on the `Microsoft.ServiceBus` provider, not based on the tier. Therefore, it's the total number of namespaces across all tiers. Subsequent requests for additional namespaces are rejected. |
 | Queue or topic size |Entity | <p>1, 2, 3, 4 GB or 5 GB</p><p>In the Premium SKU, and the Standard SKU with [partitioning](/azure/service-bus-messaging/service-bus-partitioning) enabled, the maximum queue or topic size is 80 GB.</p><p>Total size limit for a premium namespace per [messaging unit](/azure/service-bus-messaging/service-bus-premium-messaging) is 1 TB. Total size of all entities in a namespace can't exceed this limit.</p> | Defined upon creation/updation of the queue or topic. <br/><br/> Subsequent incoming messages are rejected, and an exception is received by the calling code. <p>Currently, a large message (size \> 1 MB) sent to a queue is counted twice. And, a large message (size \> 1 MB) sent to a topic is counted X + 1 times, where X is the number of subscriptions to the topic. </p>|
-| Number of concurrent connections on a namespace |Namespace |Net Messaging: 1,000.<br /><br />AMQP: 5,000. | Subsequent requests for additional connections are rejected, and an exception is received by the calling code. REST operations don't count toward concurrent TCP connections. |
-| Number of concurrent receive requests on a queue, topic, or subscription entity |Entity | 5,000 |Subsequent receive requests are rejected, and an exception is received by the calling code. This quota applies to the combined number of concurrent receive operations across all subscriptions on a topic. |
+| Number of concurrent connections on a namespace |Namespace |Net Messaging: 1,000.<br /><br />AMQP: 5,000. | Subsequent requests for additional connections are rejected. REST operations don't count toward concurrent TCP connections. |
+| Number of concurrent receive requests on a queue, topic, or subscription entity |Entity | 5,000 |Subsequent receive requests are rejected. This quota applies to the combined number of concurrent receive operations across all subscriptions on a topic. |
 | Number of topics or queues per namespace |Namespace | 10,000 for the Basic or Standard tier. The total number of topics and queues in a namespace must be less than or equal to 10,000. <br/><br/>For the Premium tier, 1,000 per messaging unit (MU). | Subsequent requests for creation of a new topic or queue on the namespace are rejected. As a result, if configured through the [Azure portal], an error message is generated. If called from the management API, an exception is received by the calling code. |
 | Number of [partitioned topics or queues](/azure/service-bus-messaging/service-bus-partitioning) per namespace |Namespace | Basic and Standard tiers: 100. Each partitioned queue or topic counts toward the quota of 1,000 entities per namespace. | Subsequent requests for creation of a new partitioned topic or queue in the namespace are rejected. As a result, if configured through the [Azure portal], an error message is generated. If called from the management API, the exception **QuotaExceededException** is received by the calling code. <p>If you want to have more partitioned entities in a basic or a standard tier namespace, create additional namespaces. </p>|
 | Maximum size of any messaging entity path: queue or topic |Entity | 260 characters. | &nbsp; |