commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From denn...@apache.org
Subject svn commit: r399219 - in /jakarta/commons/proper/logging/trunk/xdocs: guide.xml tech.xml troubleshooting.xml
Date Wed, 03 May 2006 09:15:47 GMT
Author: dennisl
Date: Wed May  3 02:15:45 2006
New Revision: 399219

URL: http://svn.apache.org/viewcvs?rev=399219&view=rev
Log:
Changed the wording to make things clearer.

Modified:
    jakarta/commons/proper/logging/trunk/xdocs/guide.xml
    jakarta/commons/proper/logging/trunk/xdocs/tech.xml
    jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml

Modified: jakarta/commons/proper/logging/trunk/xdocs/guide.xml
URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/xdocs/guide.xml?rev=399219&r1=399218&r2=399219&view=diff
==============================================================================
--- jakarta/commons/proper/logging/trunk/xdocs/guide.xml (original)
+++ jakarta/commons/proper/logging/trunk/xdocs/guide.xml Wed May  3 02:15:45 2006
@@ -147,7 +147,7 @@
 When such a file exists, every entry in the properties file becomes an "attribute"
 of the LogFactory. When there is more than one such file in the classpath, releases
 of commons-logging prior to 1.1 simply use the first one found. From release 1.1,
-each file may define a <code>priority</code> key in each file, and the file with
+each file may define a <code>priority</code> key, and the file with
 the highest priority is used (no priority definition implies priority of zero).
 When multiple files have the same priority, the first one found is used.
 </p>

Modified: jakarta/commons/proper/logging/trunk/xdocs/tech.xml
URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/xdocs/tech.xml?rev=399219&r1=399218&r2=399219&view=diff
==============================================================================
--- jakarta/commons/proper/logging/trunk/xdocs/tech.xml (original)
+++ jakarta/commons/proper/logging/trunk/xdocs/tech.xml Wed May  3 02:15:45 2006
@@ -646,7 +646,7 @@
 	This is the strategy adopted by JCL.
 			</p>
 			<p>
-	JCL uses the context classloader to use the <code>Log</code> implementation.

+	JCL uses the context classloader to load the <code>Log</code> implementation.

 			</p>
     	</subsection>
 	</section>

Modified: jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml
URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml?rev=399219&r1=399218&r2=399219&view=diff
==============================================================================
--- jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml (original)
+++ jakarta/commons/proper/logging/trunk/xdocs/troubleshooting.xml Wed May  3 02:15:45 2006
@@ -88,7 +88,7 @@
     </subsection>
     <subsection name='Diagnostic Message Prefix'>
       <p>
-Each diagnostic message is prefixed with details of the class being logger in a standard
format.
+Each diagnostic message is prefixed with details of the relevant class in a standard format.
 This takes the form:
     </p>
 <code><pre>



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message