From c7fbd9ea13d11b0659695974daa82718ada41734 Mon Sep 17 00:00:00 2001 From: Chris Little Date: Thu, 11 Jan 2024 21:26:59 +0000 Subject: [PATCH] Update clause_9_pubsub-message-payload.adoc --- .../standard/sections/clause_9_pubsub-message-payload.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extensions/pubsub/standard/sections/clause_9_pubsub-message-payload.adoc b/extensions/pubsub/standard/sections/clause_9_pubsub-message-payload.adoc index 6e32275b2..c2776cc93 100644 --- a/extensions/pubsub/standard/sections/clause_9_pubsub-message-payload.adoc +++ b/extensions/pubsub/standard/sections/clause_9_pubsub-message-payload.adoc @@ -7,7 +7,7 @@ include::../requirements/requirements_class_pubsub_message_payload.adoc[] A key component of Pub/Sub workflows is the message payload. Once a client subscribes to one or more channels from a given Pub/Sub server, notifications messages are sent using a given -representation or encoding. Notification messages can be put forth using any encoding that is deemed +representation or encoding. Notification messages can be issued using any encoding that is deemed suitable by a given publisher. While the Publish-Subscribe (Pub/Sub) Requirements Class recommends a machine-readable message payload,