[logback-dev] svn commit: r1875 - logback/trunk/logback-site/src/site/pages/manual

[noreply.ceki at qos.ch]

Author: ceki
Date: Mon Oct 27 13:15:05 2008
New Revision: 1875

Modified:
   logback/trunk/logback-site/src/site/pages/manual/mdc.html

Log:
- minor rewording in the docs

Modified: logback/trunk/logback-site/src/site/pages/manual/mdc.html
==============================================================================
--- logback/trunk/logback-site/src/site/pages/manual/mdc.html	(original)
+++ logback/trunk/logback-site/src/site/pages/manual/mdc.html	Mon Oct 27 13:15:05 2008
@@ -51,10 +51,11 @@
 		</p>
 		
 		<p>To uniquely stamp each request, the user puts contextual
-		information into the <code><a
-		href="http://www.slf4j.org/api/org/slf4j/MDC.html">MDC</a></code>,
-		the abbreviation of Mapped Diagnostic Context.  The salient parts
-		of the MDC class is shown below.
+		information into the <code>MDC</code>, the abbreviation of Mapped
+		Diagnostic Context.  The salient parts of the MDC class are shown
+		below. Please refer to the <a
+		href="http://www.slf4j.org/api/org/slf4j/MDC.html">MDC
+		javadocs</a> for a complete list of methods.
 		</p>
 
 <div class="source"><pre>package org.slf4j;
@@ -75,18 +76,17 @@
 }</pre></div>
 
 		<p>The <code>MDC</code> class contains only static methods.  It
-			lets the developer place information in a <em>diagnostic
-			context</em> that can be subsequently retrieved by certain
-			logback components. The <code>MDC</code> manages contextual
-			information on a <em>per thread basis</em>.  A child thread *
-			automatically inherits a <em>copy</em> of the mapped diagnostic
-			context of * its parent. Typically, while starting to service a
-			new client request, the developer will insert pertinent
-			contextual information, such as the client id, client's IP
-			address, request parameters etc. into the
-			<code>MDC</code>. Logback components, if appropriately
-			configured, will automatically include this information in each
-			log entry.
+		lets the developer place information in a <em>diagnostic
+		context</em> that can be subsequently retrieved by certain logback
+		components. The <code>MDC</code> manages contextual information on
+		a <em>per thread basis</em>.  A child thread automatically
+		inherits a <em>copy</em> of the mapped diagnostic context of its
+		parent. Typically, while starting to service a new client request,
+		the developer will insert pertinent contextual information, such
+		as the client id, client's IP address, request parameters
+		etc. into the <code>MDC</code>. Logback components, if
+		appropriately configured, will automatically include this
+		information in each log entry.
 		</p>
 
 		<p>