Vale checks for tuning guide

xml/tuning_logfiles.xml

@@ -184,7 +184,7 @@ https://tldp.org/LDP/LGNET/148/darin.html
     </term>
     <listitem>
      <para>
-      Log messages of some boot scripts, for example the log of the DHCP
+      Log messages of certain boot scripts, for example the log of the DHCP
       client.
      </para>
     </listitem>
@@ -352,19 +352,19 @@ Is this a systemd-related change? Should this then be removed entirely?</remark>
 
   <para>
    Log files under <filename>/var/log</filename> grow on a daily basis and
-   quickly become very large. <command>logrotate</command> is a tool that
+   quickly become large. <command>logrotate</command> is a tool that
    helps you manage log files and their growth. It allows automatic
    rotation, removal, compression, and mailing of log files. Log files can
    be handled periodically (daily, weekly, or monthly) or when exceeding a
    particular size.
   </para>
 
   <para>
-   <command>logrotate</command> is usually run daily by &systemd;,
-   and thus usually modifies log files only once a day. However, exceptions
+   <command>logrotate</command> is run daily by &systemd;,
+   and thus modifies log files only once a day. However, exceptions
    occur when a log file is modified because of its size, if
    <command>logrotate</command> is run multiple times a day, or if
-   <option>--force</option> is enabled.  Use
+   <option>--force</option> is enabled. Use
    <filename>/var/lib/misc/logrotate.status</filename> to find out when a
    particular file was last rotated.
   </para>
@@ -821,8 +821,7 @@ FILES
    <command>logwatch</command> is a customizable, pluggable log-monitoring
    script. It parses system logs, extracts the important information and
    presents them in a human readable manner. To use
-   <command>logwatch</command>, install the
-   <systemitem>logwatch</systemitem> package.
+   <command>logwatch</command>, install the <package>logwatch</package> package.
   </para>
 
   <para>
@@ -868,7 +867,7 @@ logwatch --service smartd --range 'between 5/5/2005 and 5/7/2005' \
 
   <para>
    <command>logwatch</command> can be customized to great detail. However,
-   the default configuration should usually be sufficient. The default
+   the default configuration should be sufficient. The default
    configuration files are located under
    <filename>/usr/share/logwatch/default.conf/</filename>. Never change them
    because they would get overwritten again with the next update. Rather
@@ -931,8 +930,7 @@ logwatch --service smartd --range 'between 5/5/2005 and 5/7/2005' \
    mailbox and will be notified about new mail messages upon login.
   </para>
   <para>
-   These messages can contain security relevant reports and incidents that might
-   require a quick response by the system administrator. To get notified about
+   These messages can contain security relevant reports and incidents that requires a quick response by the system administrator. To get notified about
    these messages in a timely fashion, it is strongly recommended to forward
    these mails to a dedicated remote e-mail account that is regularly checked.
   </para>
@@ -1211,7 +1209,7 @@ $UDPServerRun <replaceable>PORT</replaceable><xref linkend="co-tuning-syslog-ser
     requires a certificate infrastructure.
    </para>
    <para>
-    In this configuration, all messages from remote hosts will be treated the
+    In this configuration, all messages from remote hosts are treated the
     same on the central syslog server. Consider filtering messages into separate
     files by remote host or classify them by message category.
    </para>