Two spaces after fullstop.

syslog.conf.5

@@ -25,8 +25,8 @@ The
 .I syslog.conf
 file is the main configuration file for the
 .BR syslogd (8)
-which logs system messages on *nix systems. This file specifies rules
-for logging. For special features see the
+which logs system messages on *nix systems.  This file specifies rules
+for logging.  For special features see the
 .BR sysklogd (8)
 manpage.
 
@@ -34,8 +34,8 @@ Every rule consists of two fields, a
 .I selector
 field and an
 .I action 
-field. These two fields are separated by one or more spaces or
-tabs. The selector field specifies a pattern of facilities and
+field.  These two fields are separated by one or more spaces or
+tabs.  The selector field specifies a pattern of facilities and
 priorities belonging to the specified action.
 
 Lines starting with a hash mark (``#'') and empty lines are ignored.
@@ -53,7 +53,7 @@ and a
 .IR priority ,
 separated by a period (``.'').
 Both parts are case insensitive and can also be specified as decimal
-numbers, but don't do that, you have been warned. Both facilities and
+numbers, but don't do that, you have been warned.  Both facilities and
 priorities are described in 
 .BR syslog (3).
 The names mentioned below correspond to the similar 
@@ -72,8 +72,8 @@ The keyword
 should not be used anymore and
 .B mark
 is only for internal use and therefore should not be used in
-applications. Anyway, you may want to specify and redirect these
-messages here. The
+applications.  Anyway, you may want to specify and redirect these
+messages here.  The
 .I facility
 specifies the subsystem that produced the message, i.e. all mail
 programs log with the mail facility
@@ -88,13 +88,13 @@ is one of the following keywords, in ascending order:
 .BR alert ", " emerg ", " panic " (same as " emerg ).
 The keywords
 .BR error ", " warn " and " panic
-are deprecated and should not be used anymore. The
+are deprecated and should not be used anymore.  The
 .I priority
 defines the severity of the message
 
 The behavior of the original BSD syslogd is that all messages of the
 specified priority and higher are logged according to the given
-action. This
+action.  This
 .BR syslogd (8)
 behaves the same, but has some extensions.
 
@@ -102,12 +102,12 @@ In addition to the above mentioned names the
 .BR syslogd (8)
 understands the following extensions: An asterisk (``*'') stands for
 all facilities or all priorities, depending on where it is used
-(before or after the period). The keyword
+(before or after the period).  The keyword
 .B none
 stands for no priority of the given facility.
 
 You can specify multiple facilities with the same priority pattern in
-one statement using the comma (``,'') operator. You may specify as
+one statement using the comma (``,'') operator.  You may specify as
 much facilities as you want.  Remember that only the facility part from
 such a statement is taken, a priority part would be skipped.
 
@@ -116,33 +116,33 @@ Multiple selectors may be specified for a single
 using the semicolon (``;'') separator.  Remember that each selector in
 the 
 .I selector
-field is capable to overwrite the preceding ones. Using this
+field is capable to overwrite the preceding ones.  Using this
 behavior you can exclude some priorities from the pattern.
 
 This 
 .BR syslogd (8)
 has a syntax extension to the original BSD source, that makes its use
-more intuitively. You may precede every priority with an equation sign
+more intuitively.  You may precede every priority with an equation sign
 (``='') to specify only this single priority and not any of the
-above. You may also (both is valid, too) precede the priority with an
+above.  You may also (both is valid, too) precede the priority with an
 exclamation mark (``!'') to ignore all that priorities, either exact
-this one or this and any higher priority. If you use both extensions
+this one or this and any higher priority.  If you use both extensions
 than the exclamation mark must occur before the equation sign, just
 use it intuitively.
 
 .SH ACTIONS
 The action field of a rule describes the abstract term
-``logfile''. A ``logfile'' need not to be a real file, btw. The
+``logfile''.  A ``logfile'' need not to be a real file, btw.  The
 .BR syslogd (8)
 provides the following actions.
 
 .SS Regular File
-Typically messages are logged to real files. The file has to be
+Typically messages are logged to real files.  The file has to be
 specified with full pathname, beginning with a slash ``/''.
 
 You may prefix each entry with the minus ``-'' sign to omit syncing
-the file after every logging. Note that you might lose information if
-the system crashes right behind a write attempt. Nevertheless this
+the file after every logging.  Note that you might lose information if
+the system crashes right behind a write attempt.  Nevertheless this
 might give you back some performance, especially if you run programs
 that use logging in a very verbose manner.
 
@@ -150,9 +150,9 @@ that use logging in a very verbose manner.
 This version of
 .BR syslogd (8)
 has support for logging output  to
-named pipes (fifos). A fifo or named pipe can be used as
+named pipes (fifos).  A fifo or named pipe can be used as
 a destination for log messages by prepending a pipe symbol (``|'') to
-the name of the file. This is handy for debugging. Note that the fifo
+the name of the file.  This is handy for debugging.  Note that the fifo
 must be created with the  
 .BR mkfifo (1)
 command  before
@@ -170,33 +170,33 @@ This
 provides full remote logging, i.e. is able to send messages to a
 remote host running 
 .BR syslogd (8)
-and to receive messages from remote hosts. The remote
+and to receive messages from remote hosts.  The remote
 host won't forward the message again, it will just log them
-locally. To forward messages to another host, prepend the hostname
+locally.  To forward messages to another host, prepend the hostname
 with the at sign (``@'').
 
 Using this feature you're able to control all syslog messages on one
-host, if all other machines will log remotely to that. This tears down
+host, if all other machines will log remotely to that.  This tears down
 administration needs.
 
 .SS List of Users
 Usually critical messages are also directed to ``root'' on that
-machine. You can specify a list of users that shall get the message by
-simply writing the login. You may specify more than one user by
-separating them with commas (``,''). If they're logged in they
-get the message. Don't think a mail would be sent, that might be too
+machine.  You can specify a list of users that shall get the message by
+simply writing the login.  You may specify more than one user by
+separating them with commas (``,'').  If they're logged in they
+get the message.  Don't think a mail would be sent, that might be too
 late.
 
 .SS Everyone logged on
 Emergency messages often go to all users currently online to notify
-them that something strange is happening with the system. To specify
+them that something strange is happening with the system.  To specify
 this
 .IR wall (1)-feature
 use an asterisk (``*'').
 
 .SH EXAMPLES
 Here are some example, partially taken from a real existing site and
-configuration. Hopefully they rub out all questions to the
+configuration.  Hopefully they rub out all questions to the
 configuration, if not, drop me (Joey) a line.
 .IP
 .nf
@@ -229,9 +229,9 @@ file
 
 The second statement directs all kernel messages of the priority
 .B crit
-and higher to the remote host finlandia. This is useful, because if
+and higher to the remote host finlandia.  This is useful, because if
 the host crashes and the disks get irreparable errors you might not be
-able to read the stored messages. If they're on a remote host, too,
+able to read the stored messages.  If they're on a remote host, too,
 you still can try to find out the reason for the crash.
 
 The third rule directs these messages to the actual console, so the
@@ -258,7 +258,7 @@ This directs all messages that uses
 .BR mail.info " (in source " LOG_MAIL " | " LOG_INFO )
 to
 .IR /dev/tty12 , 
-the 12th console. For example the tcpwrapper
+the 12th console.  For example the tcpwrapper
 .BR tcpd (8)
 uses this as it's default.
 
@@ -273,7 +273,7 @@ This pattern matches all messages that come with the
 .B mail
 facility, except for the
 .B info
-priority. These will be stored in the file
+priority.  These will be stored in the file
 .IR /var/adm/mail .
 
 .IP
@@ -333,7 +333,7 @@ facility will not be stored.
 .LP
 This rule tells the
 .B syslogd
-to write all emergency messages to all currently logged in users. This
+to write all emergency messages to all currently logged in users.  This
 is the wall action.
 
 .IP
@@ -355,14 +355,14 @@ and ``joey'' if they're logged in.
 .fi
 .LP
 This rule would redirect all messages to a remote host called
-finlandia. This is useful especially in a cluster of machines where
+finlandia.  This is useful especially in a cluster of machines where
 all syslog messages will be stored on only one machine.
 
 .SH CONFIGURATION FILE SYNTAX DIFFERENCES
 .B Syslogd
 uses a slightly different syntax for its configuration file than
-the original BSD sources. Originally all messages of a specific priority
-and above were forwarded to the log file. The modifiers ``='', ``!''
+the original BSD sources.  Originally all messages of a specific priority
+and above were forwarded to the log file.  The modifiers ``='', ``!''
 and ``-'' were added to make the
 .B syslogd
 more flexible and to use it in a more intuitive manner.
@@ -377,7 +377,7 @@ Configuration file for
 .B syslogd
 
 .SH BUGS
-The effects of multiple selectors are sometimes not intuitive. For
+The effects of multiple selectors are sometimes not intuitive.  For
 example ``mail.crit,*.err'' will select ``mail'' facility messages at
 the level of ``err'' or higher, not at the level of ``crit'' or
 higher.