You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by gg...@apache.org on 2013/10/07 21:47:43 UTC
svn commit: r1530040 -
/logging/log4j/log4j2/trunk/src/site/xdoc/manual/architecture.xml
Author: ggregory
Date: Mon Oct 7 19:47:42 2013
New Revision: 1530040
URL: http://svn.apache.org/r1530040
Log:
[LOG4J2-417] Fix Event Level / LoggerConfig Level table at the architecture documentation page.
Modified:
logging/log4j/log4j2/trunk/src/site/xdoc/manual/architecture.xml
Modified: logging/log4j/log4j2/trunk/src/site/xdoc/manual/architecture.xml
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/manual/architecture.xml?rev=1530040&r1=1530039&r2=1530040&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/architecture.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/architecture.xml Mon Oct 7 19:47:42 2013
@@ -370,7 +370,7 @@ Logger y = Logger.getLogger("wombat");
<code>X.Y</code>
since tokens after periods must match exactly.
</p>
- <p>The table below provides illustrates how Level filtering works. In the table, the vertical
+ <p>The table below illustrates how Level filtering works. In the table, the vertical
header shows the Level of the LogEvent, while the horizontal header shows the Level associated
with the appropriate LoggerConfig. The intersection identifies whether the LogEvent would
be allowed to pass for further processing (Yes) or discarded (No).