Merge pull request #215933 from spelluru/patch-125

freshness review

Author: prmerger-automator[bot]

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

@@ -2,7 +2,7 @@
 title: Service Bus dead-letter queues | Microsoft Docs
 description: Describes dead-letter queues in Azure Service Bus. Service Bus queues and topic subscriptions provide a secondary subqueue, called a dead-letter queue.
 ms.topic: article
-ms.date: 08/30/2021
+ms.date: 10/25/2022
 ms.custom: "fasttrack-edit, devx-track-csharp"
 ---
 
@@ -79,4 +79,4 @@ As there can be valuable business data in messages that ended up in the dead-let
 Tools like [Azure Service Bus Explorer](./explorer.md) enable manual moving of messages between queues and topics. If there are many messages in the dead-letter queue that need to be moved, [code like this](https://stackoverflow.com/a/68632602/151350) can help move them all at once. Operators will often prefer having a user interface so they can troubleshoot which message types have failed processing, from which source queues, and for what reasons, while still being able to resubmit batches of messages to be reprocessed. Tools like [ServicePulse with NServiceBus](https://docs.particular.net/servicepulse/intro-failed-messages) provide these capabilities.
 
 ## Next steps
-See [Enable dead lettering for a queue or subscription](enable-dead-letter.md) to learn about different ways of configuring the **dead lettering on message expiration** setting.
+See [Enable dead lettering for a queue or subscription](enable-dead-letter.md) to learn about different ways of configuring the **dead lettering on message expiration** setting.