We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 33dee6f commit e5e62c4Copy full SHA for e5e62c4
mercure.rst
@@ -309,10 +309,11 @@ as patterns:
309
}
310
</script>
311
312
-However, on the client side (i.e. in JavaScript's ``EventSource``), there is no built-in way
313
-to see which topic a certain message is coming from. So if this (or any other meta information)
314
-is important to you, you need to include it in the message's data (e.g. by adding a key to the
315
-JSON, or a `data-*` attribute to the HTML).
+However, on the client side (i.e. in JavaScript's ``EventSource``), there is no
+built-in way to know which topic a certain message originates from. If this (or
+any other meta information) is important to you, you need to include it in the
+message's data (e.g. by adding a key to the JSON, or a ``data-*`` attribute to
316
+the HTML).
317
318
.. tip::
319
0 commit comments