updated limit for premium tier

Author: spelluru

includes/service-bus-quotas-table.md

@@ -2,11 +2,11 @@
 title: include file
 description: include file
 services: service-bus-messaging
-author: sethmanheim
+author: spelluru
 ms.service: service-bus-messaging
 ms.topic: include
-ms.date: 06/04/2018
-ms.author: sethm
+ms.date: 08/29/2018
+ms.author: spelluru
 ms.custom: "include file"
 
 ---
@@ -20,7 +20,7 @@ The following table lists quota information specific to Service Bus messaging. F
 | Queue/topic size |Entity |Defined upon creation of the queue/topic. <br/><br/> Subsequent incoming messages are rejected and an exception is received by the calling code. |1, 2, 3, 4 GB or 5 GB.<br /><br />In the Premium SKU, as well as Standard with [partitioning](/azure/service-bus-messaging/service-bus-partitioning) enabled, the maximum queue/topic size is 80 GB. |
 | Number of concurrent connections on a namespace |Namespace |Subsequent requests for additional connections are rejected and an exception is received by the calling code. REST operations do not count towards concurrent TCP connections. |NetMessaging: 1,000<br /><br />AMQP: 5,000 |
 | Number of concurrent receive requests on a queue/topic/subscription entity |Entity |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. |5,000 |
-| Number of topics/queues per namespace |Namespace |Subsequent requests for creation of a new topic or queue on the namespace are rejected. As a result, if configured through the [Azure portal][Azure portal], an error message is generated. If called from the management API, an exception is received by the calling code. |10,000<br /><br />The total number of topics plus queues in a namespace must be less than or equal to 10,000. |
+| Number of topics/queues per namespace |Namespace |Subsequent requests for creation of a new topic or queue on the namespace are rejected. As a result, if configured through the [Azure portal][Azure portal], an error message is generated. If called from the management API, an exception is received by the calling code. |10,000 (Basic/Standard tier). The total number of topics and queues in a namespace must be less than or equal to 10,000. <br/><br/>For premium tier, 1000 per messaging unit(MU). Maximum limit is 4000. |
 | Number of [partitioned topics/queues](/azure/service-bus-messaging/service-bus-partitioning) per namespace |Namespace |Subsequent requests for creation of a new partitioned topic or queue on the namespace are rejected. As a result, if configured through the [Azure portal][Azure portal], an error message is generated. If called from the management API, a **QuotaExceededException** exception is received by the calling code. |Basic and Standard Tiers - 100<br/><br/>Partitioned entities are not supported in the [Premium](../articles/service-bus-messaging/service-bus-premium-messaging.md) tier.<br/><br />Each partitioned queue or topic counts towards the quota of 10,000 entities per namespace. |
 | Maximum size of any messaging entity path: queue or topic |Entity |- |260 characters |
 | Maximum size of any messaging entity name: namespace, subscription, or subscription rule |Entity |- |50 characters |