[logging-log4j2] 14/16: [DOC] fix property name, should be `enableJndiContextSelector`

[ck...@apache.org]

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

ckozak pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git

commit 8868bac2b9636e87f5e999187b462ad31de618b8
Author: Remko Popma <re...@yahoo.com>
AuthorDate: Sat Dec 18 09:53:09 2021 +0900

    [DOC] fix property name, should be `enableJndiContextSelector`
---
 src/site/xdoc/manual/logsep.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/site/xdoc/manual/logsep.xml b/src/site/xdoc/manual/logsep.xml
index a0ae707..17dc7dd 100644
--- a/src/site/xdoc/manual/logsep.xml
+++ b/src/site/xdoc/manual/logsep.xml
@@ -111,9 +111,9 @@
                   to use JNDI to locate each web application's <code>LoggerContext</code>. Be sure to set the
                   <code>isLog4jContextSelectorNamed</code> context parameter to <kbd>true</kbd> and also set the
                   <code>log4jContextName</code> and <code>log4jConfiguration</code> context parameters.
-                  Note that the JndiContextSelector will not work unless <code>log4j2.enableJndiJava=true</code> is set as a
+                  Note that the JndiContextSelector will not work unless <code>log4j2.enableJndiContextSelector=true</code> is set as a
                   system property or environment variable. See the
-                  <a href="./configuration.html#enableJndiJava">enableJndiJava</a> system property.
+                  <a href="./configuration.html#enableJndiContextSelector">enableJndiContextSelector</a> system property.
                 </li>
               </ol>
             <p>