From 340597298d6d604cacb9e73200544a7ea37969f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bal=C3=A1zs=20Czoma?= Date: Thu, 4 Apr 2024 08:54:08 -0400 Subject: [PATCH] Update documentation --- examples/using-substitution-expressions/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/using-substitution-expressions/README.md b/examples/using-substitution-expressions/README.md index 9cd88c7..4398fb6 100644 --- a/examples/using-substitution-expressions/README.md +++ b/examples/using-substitution-expressions/README.md @@ -16,7 +16,7 @@ Strings containing substitution expressions must be [properly escaped](https://d * `msg_vpn_name` - set to `default` in the example * `rest_delivery_point_name` -* `url` - set to `http://example.com/$${msgId()}` in the example. Notice the escape sequence, which results in `${msgId()}` configured on the broker. Substitution expressions are only suported in the path component. +* `url` - set to `http://example.com/$${msgId()}` in the example. Notice the escape sequence, which results in `${msgId()}` configured on the broker. Substitution expressions are only supported in the path component. * `queue_name` - `rdp_queue`, the queue that has been created to be used with the RDP Important: The REST delivery point must have permission to consume messages from the queue — to achieve this, the queue’s owner must be set to `#rdp/` or the queue’s permissions for non-owner clients must be set to at least `consume` level access. Queue ingress and egress must also be enabled.