[Catalyst-commits] r12883 - trunk/Catalyst-Log-Log4perl/lib/Catalyst/Log

[jawnsy at dev.catalyst.perl.org]

Author: jawnsy
Date: 2010-02-15 23:40:22 +0000 (Mon, 15 Feb 2010)
New Revision: 12883

Modified:
   trunk/Catalyst-Log-Log4perl/lib/Catalyst/Log/Log4perl.pm
Log:
dont -> don't, adviced -> advised

Modified: trunk/Catalyst-Log-Log4perl/lib/Catalyst/Log/Log4perl.pm
===================================================================
--- trunk/Catalyst-Log-Log4perl/lib/Catalyst/Log/Log4perl.pm	2010-02-15 23:39:23 UTC (rev 12882)
+++ trunk/Catalyst-Log-Log4perl/lib/Catalyst/Log/Log4perl.pm	2010-02-15 23:40:22 UTC (rev 12883)
@@ -11,7 +11,7 @@
     use Catalyst::Log::Log4perl;
 
   # then we create a custom logger object for catalyst to use.
-  # If we dont supply any arguments to new, it will work almost
+  # If we don't supply any arguments to new, it will work almost
   # like the default catalyst-logger.
   
     __PACKAGE__->log(Catalyst::Log::Log4perl->new());
@@ -360,7 +360,7 @@
 that rely on call stack information fail to work as expected. Affected
 are the format strings %L, %F, %C, %M, %l and %T. You can instruct
 B<Catalyst::Log::Log4perl> to try to hijack these patterns which seems to
-work reasonable well, but be adviced that this feature is HIGHLY EXPERIMENTAL
+work reasonable well, but be advised that this feature is HIGHLY EXPERIMENTAL
 and relies on a few internals of L<Log::Log4perl> that might change in later
 versions of this library. Additionally, this feature is currently only tested
 with L<Log::Log4perl> version 1.08 allthough the underlying internals of