Author: seb Date: Mon Jan 8 11:54:27 2007 New Revision: 1169 Modified: logback/trunk/logback-site/src/site/xdocTemplates/access.xml logback/trunk/logback-site/src/site/xdocTemplates/demo.xml logback/trunk/logback-site/src/site/xdocTemplates/manual/joran.xml logback/trunk/logback-site/src/site/xdocTemplates/shortIntro.xml Log: Sentences fixed Modified: logback/trunk/logback-site/src/site/xdocTemplates/access.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/access.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/access.xml Mon Jan 8 11:54:27 2007 @@ -319,7 +319,7 @@ <div class="source"><pre>jconsole &</pre></div> <p> - The user might prefer to access her components thanks to a web-based solution using MX4J. + The user might prefer to access her components via a web-based solution using MX4J. In that case, here are the required steps: </p> Modified: logback/trunk/logback-site/src/site/xdocTemplates/demo.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/demo.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/demo.xml Mon Jan 8 11:54:27 2007 @@ -75,7 +75,7 @@ </p> <p> -Now, the <em>View logs</em> page looks prettier. Thanks to the <code>CyclicBufferAppender</code>, +Now, the <em>View logs</em> page looks prettier. By virtue of the <code>CyclicBufferAppender</code>, this page can fetch the last events and present them through a servlet. </p> Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/joran.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/joran.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/joran.xml Mon Jan 8 11:54:27 2007 @@ -69,14 +69,14 @@ <h2>Configuration in logback</h2> <p> -Logback can be configured both programmatically and thanks to an xml configuration +Logback can be configured both programmatically and with an xml configuration file. Here are the steps that logback follows to try to configure itself: </p> <ul> <p>Logback tries to find a file called <em>logback.xml</em> within the classpath.</p> <p>If no such file is found, it checks for another file called <em>logback-test.xml</em>.</p> - <p>In case none of these files are found, logback configures itself automatically thanks to the + <p>In case none of these files are found, logback configures itself automatically using the <a href="../xref/ch/qos/logback/classic/BasicConfigurator.html"><code>BasicConfigurator</code> </a> class.</p> </ul> @@ -955,7 +955,7 @@ <p>As we've seen, logback relies on Joran, a mature, flexible and powerful configuration framework. Many of the -capabilities offered by logback modules are possible thanks to Joran. +capabilities offered by logback modules are possible with the help of Joran. </p> <p>Joran is actually a generic configuration system which can be used Modified: logback/trunk/logback-site/src/site/xdocTemplates/shortIntro.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/shortIntro.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/shortIntro.xml Mon Jan 8 11:54:27 2007 @@ -171,10 +171,10 @@ <p> Launching the <code>HelloWorld1</code> - application will produce a very simple output. This it thanks - to logback's default configuration policy. When nothing is found to - configure logback explicitly, logback will configure itself with - a simple output to the console, as shown below. + application will output a single line on the console. By virtue of + to logback's default configuration policy, when no default file + is found to configure logback explicitely, logback will add a + <code>ConsoleAppender</code> to the root logger. </p> <div class="source"><pre>20:49:07.962 [main] DEBUG chapter1.HelloWorld1 - Hello world.</pre></div>