Author: seb Date: Fri Dec 15 18:22:59 2006 New Revision: 1089 Modified: logback/trunk/logback-site/src/site/fml/faq.fml logback/trunk/logback-site/src/site/xdocTemplates/bridge.xml Log: fixes Modified: logback/trunk/logback-site/src/site/fml/faq.fml ============================================================================== --- logback/trunk/logback-site/src/site/fml/faq.fml (original) +++ logback/trunk/logback-site/src/site/fml/faq.fml Fri Dec 15 18:22:59 2006 @@ -63,7 +63,7 @@ </p> <p> If none of these files are available, logback uses its - <code>BasicConfiguratory</code> class to create a simple default + <code>BasicConfigurator</code> class to create a simple default configuration that will only log to the console. </p> </answer> Modified: logback/trunk/logback-site/src/site/xdocTemplates/bridge.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/bridge.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/bridge.xml Fri Dec 15 18:22:59 2006 @@ -50,7 +50,7 @@ This is what it takes to make logback your logging implementation when using log4j. It will use logback's automatic basic configuration, displaying the logging requests in the console. More advanced use will require a configuration file and other jars - which are logback dependencies. In that case, a file called <em>logback.xml</em>, + which are logback dependencies. A file called <em>logback.xml</em>, placed in the application's classpath, will be automatically loaded by logback. </p>