Author: ceki
Date: Fri Dec 5 12:36:27 2008
New Revision: 1256
Modified:
slf4j/trunk/slf4j-site/src/site/pages/faq.html
Log:
- minor rephrasing
Modified: slf4j/trunk/slf4j-site/src/site/pages/faq.html
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/pages/faq.html (original)
+++ slf4j/trunk/slf4j-site/src/site/pages/faq.html Fri Dec 5 12:36:27 2008
@@ -193,10 +193,11 @@
application is riddled with thousands of direct log4j calls,
migration to JDK 1.4 would be a relatively lengthy and
error-prone process. Even worse, you would potentially need to
- maintain two versions of your CRM. Had you been invoking SLF4J
- API instead of log4j, the migration could be completed in a
- matter of minutes by replacing one jar file with another.
- </p>
+ maintain two versions of your CRM software. Had you been
+ invoking SLF4J API instead of log4j, the migration could be
+ completed in a matter of minutes by replacing one jar file with
+ another.
+ </p>
<p>SLF4J lets component developers to defer the choice of the
logging system to the end-user but eventually a choice needs
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
