X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=scpubgit%2FObject-Remote.git;a=blobdiff_plain;f=lib%2FObject%2FRemote%2FLogging.pm;h=7e030ff49a5c8108d278ee89431e0a2876ed6cc1;hp=e049769296f246d7ecc8412722d41e4d90c5fcc6;hb=f21127fd8c611eee83f769422168bb7bf3b25f0a;hpb=455d031ccaa22069757d53cac1e90fda622b80d0

diff --git a/lib/Object/Remote/Logging.pm b/lib/Object/Remote/Logging.pm
index e049769..7e030ff 100644
--- a/lib/Object/Remote/Logging.pm
+++ b/lib/Object/Remote/Logging.pm
@@ -169,20 +169,20 @@ environment variable on the local interpreter will cause it to be propagated to
 remote interpreter so all logs will be formated the same way.
 
 This class is designed so any module can create their own logging sub-class using it.
-With out any additional configuration consumers of this logging class will automatically
-be enabled via OBJECT_REMOTE_LOG_LEVEL and formated with OBJECT_REMOTE_LOG_FORMAT but
-those additional log messages are not sent to STDERR. By setting the 
-OBJECT_REMOTE_LOG_SELECTIONS environment variable to a list of class names seperated 
-by spaces then logs generated by packages that use those classes will be sent to STDERR.
-This is also a configuration item that is forwarded to the remote interpreters so all
-logging is consistent.
+With out any additional configuration the consumers of this logging class will
+automatically be enabled via OBJECT_REMOTE_LOG_LEVEL and formated with 
+OBJECT_REMOTE_LOG_FORMAT but those additional log messages are not sent to STDERR. 
+By setting the  OBJECT_REMOTE_LOG_SELECTIONS environment variable to a list of
+class names seperated by spaces then logs generated by packages that use those classes
+will be sent to STDERR. This is also a configuration item that is forwarded to the
+remote interpreters so all logging is consistent.
 
 Regardless of OBJECT_REMOTE_LOG_LEVEL the logging system is still active and loggers
 can access the stream of log messages to format and output them. Internally
 OBJECT_REMOTE_LOG_LEVEL causes an L<Object::Remote::Logging::Logger> to be built
 and connected to the L<Object::Remote::Logging::Router> instance. It is also possible
 to manually build a logger instance and connect it to the router. See the documentation
-for the router and logger class.
+for the logger and router classes.
 
 The logging system also supports a method of forwarding log messages from remote
 interpreters to the local interpreter. Forwarded log messages are generated in the