svn commit: r841903 - in /websites/production/cxf/content: cache/docs.pageCache docs/debugging-and-logging.html

[bu...@apache.org]

Author: buildbot
Date: Wed Dec 12 16:48:08 2012
New Revision: 841903

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/debugging-and-logging.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/debugging-and-logging.html
==============================================================================
--- websites/production/cxf/content/docs/debugging-and-logging.html (original)
+++ websites/production/cxf/content/docs/debugging-and-logging.html Wed Dec 12 16:48:08 2012
@@ -375,7 +375,7 @@ It is useful for debugging if the soap f
    <span class="code-tag">&lt;/bean&gt;</span>
 </pre>
 </div></div>
-<p>Spring bean creates ATOM push handler and registers it with root logger for all log levels. This setup leads to logging everything CXF, Spring and others inclued. Since batch size is not specified default value of one is used - each event is packed up as single feed pushed out to specified URL. Default conversion strategy and default WebClient-based deliver are used. </p>
+<p>Spring bean creates ATOM push handler and registers it with root logger for all log levels. This setup leads to logging everything CXF, Spring and others included. Since batch size is not specified default value of one is used - each event is packed up as single feed pushed out to specified URL. Default conversion strategy and default WebClient-based deliver are used. </p>
 
 <p>More complex example shows how to specify non-root logger and define batch size:</p>
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">