[logging-log4j2] branch master updated: LOG4J2-3473 (DOC) fix version number

[rp...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rpopma pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


The following commit(s) were added to refs/heads/master by this push:
     new b1e6f2654e LOG4J2-3473 (DOC) fix version number
b1e6f2654e is described below

commit b1e6f2654ec3cdedbe926ddc02b1d74058ec6739
Author: Remko Popma <re...@yahoo.com>
AuthorDate: Wed Apr 27 14:41:06 2022 +0900

    LOG4J2-3473 (DOC) fix version number
    
    fix version number when default waitstrategy is garbage-free
---
 src/site/asciidoc/manual/garbagefree.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/site/asciidoc/manual/garbagefree.adoc b/src/site/asciidoc/manual/garbagefree.adoc
index 9ae92a189c..d08a9564a4 100644
--- a/src/site/asciidoc/manual/garbagefree.adoc
+++ b/src/site/asciidoc/manual/garbagefree.adoc
@@ -100,7 +100,7 @@ NOTE: As of version 2.6, a Log4j configuration containing a
 `<Properties>` section will result in temporary objects being created
 during steady-state logging.
 
-NOTE:  as of version 2.17.3, the default Async Logger wait strategy used by Log4j
+NOTE:  as of version 2.18.0, the default Async Logger wait strategy used by Log4j
 (Timeout) is garbage-free. Some of the wait strategies included in LMAX disruptor 3.4.4,
 especially `TimeoutBlockingWaitStrategy` and `BlockingWaitStrategy` (Block)
 are not garbage-free since they