</para>
<programlisting>dlt-daemon -d</programlisting>
<para>
- Afterwards, the <literal>dlt-receive</literal> can be used to forward all
- messages logged via the DLT to a specific file. The following command attaches
+ Afterwards, the <literal>dlt-receive</literal> tool can be used to forward all
+ messages logged via DLT to a specific file. The following command attaches
the <literal>dlt-receive</literal> tool to the <literal>dlt-daemon</literal>
running on the same machine and writes all output to
<literal>/tmp/dlt.log</literal>:
</para>
<programlisting>12 2012/08/01 10:30:32.247913 17066086 006 ECU1 <emphasis role="bold">NSC- CTRL</emphasis> log info V 1 <emphasis role="bold">[Active state of unit "node-startup-controller.service" changed to active]</emphasis></programlisting>
<para>
- The fields we are interested for debugging and testing in are the Apid
- (Application ID), Ctid (Context ID) and the Payload. The test cases described
- in the following chapters include the exact log values for these fields needed
- to verify the correctness of behaviour of the Node Startup Controller.
+ The fields relevant to debugging and testing in are the Apid (Application ID), Ctid
+ (Context ID) and the Payload. The test cases described in the following chapters
+ include the exact log values for these fields needed to verify the the Node Startup
+ Controller is behaving correctly.
</para>
</refsect1>
</refentry>