review feedback

Author: Glenn Gailey

articles/azure-functions/functions-scale.md

@@ -149,9 +149,9 @@ The unit of scale for Azure Functions is the function app. When the function app
 Scaling can vary on a number of factors, and scale differently based on the trigger and language selected. There are a few intricacies of scaling behaviors to be aware of:
 
 * A single function app only scales out to a maximum of 200 instances. A single instance may process more than one message or request at a time though, so there isn't a set limit on number of concurrent executions.
-* For HTTP triggers, new instances are allocated, at most, once per second.
+* For HTTP triggers, new instances are allocated, at most, once per second. Scaling is faster when running in a [Premium plan](#premium-plan).
 * For non-HTTP triggers, new instances are allocated, at most, once every 30 seconds.
-* For Service Bus triggers, use _Manage_ rights on resources for the most efficient scaling. With _Listen_ rights, scaling won't be as accurate. To learn more about setting rights in Service Bus access policies, see [Shared Access Authorization Policy](../service-bus-messaging/service-bus-sas.md#shared-access-authorization-policies).
+* For Service Bus triggers, use _Manage_ rights on resources for the most efficient scaling. With _Listen_ rights, scaling isn't as accurate because the queue length can't be used to inform scaling decisions. To learn more about setting rights in Service Bus access policies, see [Shared Access Authorization Policy](../service-bus-messaging/service-bus-sas.md#shared-access-authorization-policies).
 * For Event Hub triggers, see the [scaling guidance](functions-bindings-event-hubs-trigger.md#scaling) in the reference article. 
 
 ### Best practices and patterns for scalable apps