man: fix _STREAM_ID, _LINE_BREAK descriptions

Pointed out by Дилян Палаузов (https://github.com/dilyanpalauzov).
Fixes #7870.

diff --git a/man/systemd.journal-fields.xml b/man/systemd.journal-fields.xml
index b08ef1777e40980fa227b8fd1fcc92ab4c27c724..15a166280b528b30eeb6277dd616f3831fbe4711 100644 (file)
--- a/man/systemd.journal-fields.xml
+++ b/man/systemd.journal-fields.xml
@@ -339,7 +339,7 @@
       <varlistentry>
         <term><varname>_STREAM_ID=</varname></term>
         <listitem>
-          <para>Only applies to <literal>_TRANSPORT=stream</literal> records: specifies a randomized 128bit ID assigned
+          <para>Only applies to <literal>_TRANSPORT=stdout</literal> records: specifies a randomized 128bit ID assigned
           to the stream connection when it was first created. This ID is useful to reconstruct individual log streams
           from the log records: all log records carrying the same stream ID originate from the same stream.</para>
         </listitem>
@@ -347,7 +347,7 @@
       <varlistentry>
         <term><varname>_LINE_BREAK=</varname></term>
         <listitem>
-          <para>Only applies to <literal>_TRANSPORT=stream</literal> records: indicates that the log message in the
+          <para>Only applies to <literal>_TRANSPORT=stdout</literal> records: indicates that the log message in the
           standard output/error stream was not terminated with a normal newline character (<literal>\n</literal>,
           i.e. ASCII 10). Specifically, when set this field is one of <option>nul</option> (in case the line was
           terminated by a NUL byte), <option>line-max</option> (in case the maximum log line length was reached, as