Merge pull request #299928 from jaganth/docs-editor/apache-kafka-troubleshooting-g-1747350368

Update apache-kafka-troubleshooting-guide.md

Author: prmerger-automator[bot]

articles/event-hubs/apache-kafka-troubleshooting-guide.md

@@ -10,7 +10,7 @@ ms.date: 03/06/2025
 This article provides troubleshooting tips for issues that you might run into when using Event Hubs for Apache Kafka. 
 
 ## Server Busy exception
-You might receive Server Busy exception because of Kafka throttling. With AMQP clients, Event Hubs immediately returns a **server busy** exception upon service throttling. It's equivalent to a "try again later" message. In Kafka, messages are delayed before being completed. The delay length is returned in milliseconds as `throttle_time_ms` in the produce/fetch response. In most cases, these delayed requests aren't logged as server busy exceptions on Event Hubs dashboards. Instead, the response's `throttle_time_ms` value should be used as an indicator that throughput has exceeded the provisioned quota.
+You might see ThrottledRequests metrics because of Kafka throttling. With AMQP clients, Event Hubs immediately returns a **server busy** exception upon service throttling. It's equivalent to a "try again later" message. In Kafka, incoming messages are delay before being acknowledged while outgoing message will see delayed delivery. The delay length is returned in milliseconds as `throttle_time_ms` in the produce/fetch response. In most cases, these delayed requests aren't logged as ThrottledRequests metrics on Event Hubs dashboards. Instead, the response's `throttle_time_ms` value should be used as an indicator that throughput has exceeded the provisioned quota.
 
 If the traffic is excessive, the service has the following behavior: