Merge pull request #189275 from EldertGrootenboer/patch-1

Update service-bus-dead-letter-queues.md

Author: PRMerger8

articles/service-bus-messaging/service-bus-dead-letter-queues.md

@@ -36,7 +36,7 @@ There are several activities in Service Bus that cause messages to get pushed to
 |HeaderSizeExceeded |The size quota for this stream has been exceeded. |
 |TTLExpiredException |The message expired and was dead lettered. See the [Time to live](#time-to-live) section for details. |
 |Session ID is null. |Session enabled entity doesn't allow a message whose session identifier is null. |
-|MaxTransferHopCountExceeded | The maximum number of allowed hops when forwarding between queues. Value is set to 4. |
+|MaxTransferHopCountExceeded | The maximum number of allowed hops when forwarding between queues has been exceeded. This value is set to 4. |
 | MaxDeliveryCountExceededExceptionMessage | Message couldn't be consumed after maximum delivery attempts. See the [Maximum delivery count](#maximum-delivery-count) section for details. |
 
 ## Maximum delivery count
@@ -45,7 +45,7 @@ There is a limit on number of attempts to deliver messages for Service Bus queue
 ## Time to live
 When you enable dead-lettering on queues or subscriptions, all expiring messages are moved to the DLQ. The dead-letter reason code is set to: TTLExpiredException.
 
-The deferred messages will also not be purged and moved to the dead-letter queue after they expire. This behavior is by design.
+Deferred messages will not be purged and moved to the dead-letter queue after they expire. This behavior is by design.
 
 ## Errors while processing subscription rules
 If you enable dead-lettering on filter evaluation exceptions, any errors that occur while a subscription's SQL filter rule executes are captured in the DLQ along with the offending message. Don't use this option in a production environment in which not all message types have subscribers.