more clean up

Author: Glenn Gailey

articles/azure-functions/functions-scale.md

@@ -152,10 +152,7 @@ Scaling can vary on a number of factors, and scale differently based on the trig
 * For HTTP triggers, new instances are allocated, at most, once per second.
 * 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).
-
-Different triggers may also have different scaling limits as well as documented below:
-
-* [Event Hub](functions-bindings-event-hubs-trigger.md#scaling)
+* 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