Skip to content

Commit a422137

Browse files
authored
fixed link
1 parent 4f48e52 commit a422137

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/service-bus-messaging/service-bus-throttling.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Understandably, some applications may be sensitive to being throttled. In that c
5959

6060
## Throttling in premium tier
6161

62-
The [Service Bus premium](service-bus-premium-messaging.md) tier allocates dedicated resources, in terms of messaging units, to each namespace setup by the customer. These dedicated resources provide predictable throughput and latency and are recommended for high throughput or sensitive production grade systems. Additionally, the premium tier also enables customers to scale up their throughput capacity when they experience spikes in the workload. For more information, see [Automatically update messaging units of an Azure Service Bus namespace](automate-update-messaging-units).
62+
The [Service Bus premium](service-bus-premium-messaging.md) tier allocates dedicated resources, in terms of messaging units, to each namespace setup by the customer. These dedicated resources provide predictable throughput and latency and are recommended for high throughput or sensitive production grade systems. Additionally, the premium tier also enables customers to scale up their throughput capacity when they experience spikes in the workload. For more information, see [Automatically update messaging units of an Azure Service Bus namespace](automate-update-messaging-units.md).
6363

6464
### How does throttling work in Service Bus Premium?
6565

@@ -75,7 +75,7 @@ There are various ways to identifying throttling in the Service Bus premium tier
7575

7676
### How can I avoid being throttled?
7777

78-
As the Service Bus premium namespace already has dedicated resources, you can reduce the possibility of getting throttled by scaling up the number of messaging units allocated to your namespace in the event (or anticipation) of a spike in the workload. For more information, see [Automatically update messaging units of an Azure Service Bus namespace](automate-update-messaging-units).
78+
As the Service Bus premium namespace already has dedicated resources, you can reduce the possibility of getting throttled by scaling up the number of messaging units allocated to your namespace in the event (or anticipation) of a spike in the workload. For more information, see [Automatically update messaging units of an Azure Service Bus namespace](automate-update-messaging-units.md).
7979

8080

8181
## FAQs

0 commit comments

Comments
 (0)