Fixed comments from JanaH.

Author: harneshalaka

tasks/systemd-journald-troubleshooting.xml

@@ -27,14 +27,19 @@ in the assembly -->
       </abstract>
   </info>
 <procedure>
-  <title>Troubleshoot <command>journalctl</command> errors</title>
-  <step><para>Identify the severity and content of the error.The errors are marked with priority level:</para>
+  <title>View &systemd; errors</title>
+  <step><para>View the list of failed &systemd; units:</para>
+  <screen>systemctl --failed</screen>
+<para>The list of all failed services appear.</step>
+  <step><para>Identify the severity and content of the error.</para>
+    <screen>journalctl -p 0..7 -b</screen>
+    <para>The list of errors with priority level <literal>0 to 7 appears. The errors are marked with priority level:</para>
 <itemizedlist><listitem><para><guimenu>0-2</guimenu>: <command>emerg, alert, crit</command>: Critical issues, system collapse imminent.</para></listitem>
   <listitem><para><guimenu>3</guimenu>: <command>err (Error)</command>: A service or application failed to complete a requested operation.</para></listitem>
    <listitem><para><guimenu>4</guimenu>: <command>warning </command>: Something undesirable happened but is not an immediate failure.</para></listitem>
  <listitem><para><guimenu>5-7</guimenu>: <command>notice, info, debug</command>: Normal operational information and developer diagnostics.</para></listitem></itemizedlist>
 </step>
-<step><para>Identify the failing unit using the following command:</para>
+<step><para>View the error log for the failing service using the following command:</para>
 <screen>journalctl -u &lt;failing_service_name&gt;</screen>
 <para>The lines preceding the termination message includes information on the error.</para>
 <itemizedlist><listitem><para><guimenu>Exit Status</guimenu>: f a service stops, look for a message like Process xxx exited with status 1/FAILURE. A status of 0 is success. Any non-zero status indicates an error. </para></listitem>
@@ -43,26 +48,26 @@ in the assembly -->
  </itemizedlist></step>
 <step><para>Use detailed views of logs to get detailed information on the error.</para>
 <screen>journalctl -xe</screen>
-<para>To view all messages from the Apache service during the current boot, with detailed explanations, run the following command:</para>
+<para>For example, to view all messages from the Apache service during the current boot, with detailed explanations, run the following command:</para>
 <screen>journalctl -u httpd.service -b -xe</screen></step>
 </procedure>
 <section>
-  <title>Troubleshoot apache2 error</title>
+  <title>Troubleshoot &systemd; error</title>
 <procedure>
     <para>
-   This section introduces a simple example to illustrate how to find and fix
+   This section introduces an example to illustrate how to find and fix
    the error reported by &systemd; during <command>apache2</command> start-up.
   </para>
     <step>
     <para>
-     Try to start the apache2 service:
+     Start the apache2 service:
     </para>
-<screen># systemctl start apache2
+<screen>systemctl start apache2
 Job for apache2.service failed. See 'systemctl status apache2' and 'journalctl -xn' for details.</screen>
    </step>
    <step>
     <para>
-     Let us see what the service's status says:
+     View the service status:
     </para>
 <screen>&prompt.sudo;systemctl status apache2
 apache2.service - The Apache Webserver
@@ -76,7 +81,7 @@ apache2.service - The Apache Webserver
    </step>
    <step>
     <para>
-     Show the verbose version of messages related to process ID 11026:
+     View the verbose version of messages related to process ID 11026:
     </para>
 <screen>&prompt.sudo;journalctl -o verbose _PID=11026
 [...]