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/05 00:01:05 UTC

svn commit: r1529327 - /logging/log4j/log4j2/trunk/src/site/xdoc/manual/architecture.xml

Author: ggregory
Date: Fri Oct  4 22:01:05 2013
New Revision: 1529327

URL: http://svn.apache.org/r1529327
Log:
Fix typo.

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=1529327&r1=1529326&r2=1529327&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/architecture.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/architecture.xml Fri Oct  4 22:01:05 2013
@@ -368,7 +368,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. Im the table, the vertical
+        <p>The table below provides 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).