From: Marcin Siodelski Date: Tue, 23 Sep 2014 13:59:10 +0000 (+0200) Subject: [3536] Fixed a few editorial nits. X-Git-Tag: rt3470_base~14^2~1 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=b4fe1c31cd466fd09553c2bec36dec25c096618e;p=thirdparty%2Fkea.git [3536] Fixed a few editorial nits. --- diff --git a/doc/guide/logging.xml b/doc/guide/logging.xml index b6394ea83e..d28fe641d1 100644 --- a/doc/guide/logging.xml +++ b/doc/guide/logging.xml @@ -27,7 +27,7 @@ severity (some are more important than others) and source (some are produced by specific components, e.g. hooks). It is useful to understand which log messages are needed and which are not and configure your - logging appropriately. For example debug level messages can be safely + logging appropriately. For example, debug level messages can be safely ignored in a typical deployment. They are, however, very useful when debugging a problem. @@ -35,9 +35,9 @@ The logging system in Kea is configured through the Logging structure in your configuration - file. All daemons (e.g. a DHCPv4 and DHCPv6 servers) will look at the + file. All daemons (e.g. DHCPv4 and DHCPv6 servers) will use the configuration in the Logging structure to see - what should be logged and to where. This allows sharing identical + what should be logged and to where. This allows for sharing identical logging configuration between daemons. @@ -56,7 +56,7 @@ In the Logging structure in a configuration file you can specify the configuration for zero or more loggers. If there are - no specified loggers, the code will use default values which + no loggers specified, the code will use default values which cause Kea to log messages on at least INFO severity to standard output.