svn commit: r39901 - head/en_US.ISO8859-1/books/handbook/config

[Warren Block]

Author: wblock
Date: Thu Nov  1 17:00:30 2012
New Revision: 39901
URL: http://svn.freebsd.org/changeset/doc/39901

Log:
  Whitespace-only fixes.  Translators, please ignore.

Modified:
  head/en_US.ISO8859-1/books/handbook/config/chapter.xml

Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/config/chapter.xml	Thu Nov  1 16:29:14 2012	(r39900)
+++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml	Thu Nov  1 17:00:30 2012	(r39901)
@@ -191,7 +191,7 @@
 	  should be 256 megabytes.  Systems with less memory may
 	  perform better with more swap.  Less than 256 megabytes
 	  of swap is not recommended and memory expansion should be
-	  considered. The kernel's VM paging algorithms are tuned to
+	  considered.  The kernel's VM paging algorithms are tuned to
 	  perform best when the swap partition is at least two times
 	  the size of main memory.  Configuring too little swap can
 	  lead to inefficiencies in the VM page scanning code and
@@ -540,12 +540,12 @@ HOME=/var/log
 
     <calloutlist>
       <callout arearefs="co-comments">
-	<para>Like most &os; configuration files, lines that begin with the
-	  <literal>#</literal> character are comments.  A
+	<para>Like most &os; configuration files, lines that begin
+	  with the <literal>#</literal> character are comments.  A
 	  comment can be placed in the file as a reminder of what and
-	  why a desired action is performed. Comments cannot be on the
-	  same line as a command or else they will be interpreted as
-	  part of the command; they must be on a new line.  Blank
+	  why a desired action is performed.  Comments cannot be on
+	  the same line as a command or else they will be interpreted
+	  as part of the command; they must be on a new line.  Blank
 	  lines are ignored.</para>
       </callout>
 
@@ -608,10 +608,9 @@ HOME=/var/log
     <para>This is the basic setup for every
       <filename>crontab</filename> file, although there is one thing
       different about this one.  Field number six, where we specified
-      the username, only exists in the system <filename>crontab</filename>.
-      This field should be
-      omitted for individual user <filename>crontab</filename>
-      files.</para>
+      the username, only exists in the system
+      <filename>crontab</filename>.  This field should be omitted for
+      individual user <filename>crontab</filename> files.</para>
 
     <sect2 id="configtuning-installcrontab">
       <title>Installing a Crontab</title>
@@ -1495,7 +1494,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 n
 	log messages from <replaceable>facility</replaceable> at level
 	<replaceable>level</replaceable> or higher.  It is also
 	possible to add an optional comparison flag before the level
-	to specify more precisely what is logged. Multiple
+	to specify more precisely what is logged.  Multiple
 	selector fields can be used for the same action, and are
 	separated with a semicolon (<literal>;</literal>).  Using
 	<literal>*</literal> will match everything.
@@ -1640,10 +1639,10 @@ cron.*                                  
 	  owner, permissions, and when to rotate that file, as well as
 	  optional flags that affect the log rotation (such as
 	  compression) and programs to signal when the log is
-	  rotated. As an example, here is the default configuration
+	  rotated.  As an example, here is the default configuration
 	  in &os;:</para>
 
-        <programlisting># configuration file for newsyslog
+	<programlisting># configuration file for newsyslog
 # $&os;$
 #
 # Entries which do not specify the '/pid_file' field will cause the