[42/50] logging-log4j2 git commit: LOG4J2-1179 text clarification

[mi...@apache.org]

LOG4J2-1179 text clarification


Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/3f37f184
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/3f37f184
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/3f37f184

Branch: refs/heads/LOG4J-1181
Commit: 3f37f184fe131839323dbb927613337385bc181d
Parents: 69a1ac2
Author: rpopma <rp...@apache.org>
Authored: Thu May 5 10:06:05 2016 +0900
Committer: rpopma <rp...@apache.org>
Committed: Thu May 5 10:06:05 2016 +0900

----------------------------------------------------------------------
 src/site/xdoc/performance.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/3f37f184/src/site/xdoc/performance.xml
----------------------------------------------------------------------
diff --git a/src/site/xdoc/performance.xml b/src/site/xdoc/performance.xml
index 756f8b0..805091d 100644
--- a/src/site/xdoc/performance.xml
+++ b/src/site/xdoc/performance.xml
@@ -125,7 +125,7 @@
         an application with more threads can log more. The other logging libraries suffer
         from lock contention and total throughput stays constant or drops when more threads are logging.
         This means that with the other logging libraries, each individual thread will be able to log less.</em></p>
-      <p>Bear in mind that this is <em>peak</em> throughput: Log4j 2 gives better throughput up to a point, but
+      <p>Bear in mind that this is <em>peak</em> throughput: Log4j 2's Async Loggers give better throughput up to a point, but
         once the queue is full, the appender thread needs to wait until a slot becomes available in the queue,
         and throughput will drop to the maximum sustained throughput of the underlying appenders at best.
       </p>