(activemq-artemis) branch main updated: NO-JIRA fix STOMP doc formatting

[jb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jbertram pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-artemis.git


The following commit(s) were added to refs/heads/main by this push:
     new 311e9382a2 NO-JIRA fix STOMP doc formatting
311e9382a2 is described below

commit 311e9382a28100afe97fb81b377332a337a9c50c
Author: Justin Bertram <jb...@apache.org>
AuthorDate: Thu Feb 8 11:28:10 2024 -0600

    NO-JIRA fix STOMP doc formatting
---
 docs/user-manual/stomp.adoc | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/docs/user-manual/stomp.adoc b/docs/user-manual/stomp.adoc
index 7dcda48822..706c428a9b 100644
--- a/docs/user-manual/stomp.adoc
+++ b/docs/user-manual/stomp.adoc
@@ -46,15 +46,13 @@ Follow xref:logging.adoc#configuring-a-specific-level-for-a-logger[these steps]
 The STOMP specification is intentionally ambiguous about message routing semantics.
 When providing an overview of the protocol the STOMP 1.2 specification https://stomp.github.io/stomp-specification-1.2.html#Protocol_Overview[says]:
 
-----
+____
 A STOMP server is modelled as a set of destinations to which messages can be sent.
-The STOMP protocol treats destinations as opaque string and their syntax is
-server implementation specific. Additionally STOMP does not define what the
-delivery semantics of destinations should be. The delivery, or
-"message exchange", semantics of destinations can vary from server to server and
-even from destination to destination. This allows servers to be creative with the
-semantics that they can support with STOMP.
-----
+The STOMP protocol treats destinations as opaque string and their syntax is server implementation specific.
+Additionally STOMP does not define what the delivery semantics of destinations should be.
+The delivery, or "message exchange", semantics of destinations can vary from server to server and even from destination to destination.
+This allows servers to be creative with the semantics that they can support with STOMP.
+____
 
 Therefore, there are a handful of different ways to specify which semantics are desired both on the client-side and broker-side.