pathos 01/05/20 04:20:48
Modified: src/java/org/apache/log4j NDC.java
Log:
Documentation changes.
Revision Changes Path
1.6 +2 -2 jakarta-log4j/src/java/org/apache/log4j/NDC.java
Index: NDC.java
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/java/org/apache/log4j/NDC.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- NDC.java 2001/04/29 11:54:34 1.5
+++ NDC.java 2001/05/20 11:20:48 1.6
@@ -21,7 +21,7 @@
<p>A Nested Diagnostic Context, or NDC in short, is an instrument
to distinguish interleaved log output from different sources. Log
output is typically interleaved when a server handles multiple
- clients near-simulatanously.
+ clients near-simultaneously.
<p>Interleaved log output can still be meaningful if each log entry
from different contexts had a distinctive stamp. This is where NDCs
@@ -65,7 +65,7 @@
<p>Heavy duty systems should call the {@link #remove} method when
leaving the run method of a thread. This ensures that the memory
used by the thread can be freed by the Java garbage collector. In
- version 0.8.5, we have added a meachanism to lazily remove
+ version 0.8.5, we have added a mechanism to lazily remove
references to dead threads. In practice, this means that you can be
a little sloppy and sometimes forget to call {@link #remove} before
exiting a thread.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
