From e3db9b0e98f2010390ba3dfb02c108ac8accf713 Mon Sep 17 00:00:00 2001 From: Joseph Riddle Date: Tue, 29 Oct 2024 12:44:11 -0700 Subject: [PATCH] Fix queue group link in Concurrent Message Processing example (#271) --- examples/messaging/concurrent/meta.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/messaging/concurrent/meta.yaml b/examples/messaging/concurrent/meta.yaml index b1b1e8c3..216565df 100644 --- a/examples/messaging/concurrent/meta.yaml +++ b/examples/messaging/concurrent/meta.yaml @@ -2,7 +2,7 @@ title: Concurrent Message Processing description: |- By default, when a subscription is created, each message that is received it process sequentially. There can be multiple subscriptions - setup in a [queue group][queue] in which case the NATS server will + setup in a [queue group][1] in which case the NATS server will distribute messages to each member of the group. However, even within a subscription, it may be desirable to handle