formatting

Author: spelluru

articles/service-bus-messaging/includes/common-limits.md

@@ -9,7 +9,7 @@ ms.author: spelluru
 The following limits are common across all tiers. 
 
 | Quota name | Value | Notes | 
-| --- | --- |  --- |
+| --- | --- | --- |
 | Maximum number of namespaces per Azure subscription | 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. |
 | Number of concurrent connections on a 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 | 5,000 | Subsequent receive requests are rejected. This quota applies to the combined number of concurrent receive operations across all subscriptions on a topic. |

articles/service-bus-messaging/includes/tier-limits.md

@@ -12,11 +12,11 @@ The following table shows limits that are different for Basic, Standard, and Pre
 
 | Quota name | Basic | Standard | Premium | Notes | 
 | --- | --- | --- | --- | --- |
-| Queue or topic size | <p>1, 2, 3, 4 GB or 5 GB</p> | <p>1, 2, 3, 4 GB or 5 GB (if partitioning isn't enabled)</p><p>80 GB, if the partitioning is enabled.</p> | <p>1, 2, 3, 4 GB or 5 GB (if partitioning isn't enabled)</p><p>80 GB, if the partitioning is enabled.</p> | Defined upon creation/updation of the queue or topic. <p>Total size of all entities in a namespace can't exceed the namespace size limit documented in the next row.</p><p>Subsequent incoming messages are rejected, and the calling code receives an exception.</p> <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>|
+| Queue or topic size | <p>1, 2, 3, 4 GB or 5 GB</p> | <p>1, 2, 3, 4 GB or 5 GB <br/>(if partitioning isn't enabled)</p><p>80 GB <br/>(If the partitioning is enabled)</p> | <p>1, 2, 3, 4 GB or 5 GB <br/>(if partitioning isn't enabled)</p><p>80 GB <br/>(If the partitioning is enabled)</p> | Defined upon creation/updation of the queue or topic. <p>Total size of all entities in a namespace can't exceed the namespace size limit documented in the next row.</p><p>Subsequent incoming messages are rejected, and the calling code receives an exception.</p> <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>|
 | Namespace size | | 400 GB | 1 TB per [messaging unit](/azure/service-bus-messaging/service-bus-premium-messaging).| Total size of all entities in a namespace can't exceed this limit. | 
 | Number of topics or queues per namespace | 10,000 | 10000 | 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, the calling code receives an exception. |
 | Number of [partitioned topics or queues](/azure/service-bus-messaging/service-bus-partitioning) per namespace | 100 | 100 | N/A | Each partitioned queue or topic counts toward the quota of 1,000 entities per namespace. <p>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> <p>If you want to have more partitioned entities in a basic or a standard tier namespace, create additional namespaces. </p>|
-| Message size or batch size for a queue, topic, or subscription entity | | 256 KB | 100 MB on AMQP, and 1 MB for on HTTP and SBMP | The message size includes the size of properties (system and user) and the size of payload. The size of system properties varies depending on your scenario. Incoming messages that exceed these quotas are rejected, and the calling code receives an exception. | 
+| Message size or batch size for a queue, topic, or subscription entity | | 256 KB | 100 MB on AMQP<br/><br/>1 MB for on HTTP and SBMP | The message size includes the size of properties (system and user) and the size of payload. The size of system properties varies depending on your scenario. Incoming messages that exceed these quotas are rejected, and the calling code receives an exception. | 
 | Number of subscriptions per topic | | 2,000 | 2000 | Subsequent requests for creating additional subscriptions for the topic are rejected. As a result, if configured through the portal, an error message is shown. If called from the management API, the calling code receives an exception. |