From f7b9b8b37d8cf299836d84d43e8bb675772ab716 Mon Sep 17 00:00:00 2001 From: Yogesh Vaishnav Date: Mon, 5 May 2025 20:33:56 +0530 Subject: [PATCH] doc(architecture): fix the ordering of vertical and horizontal header statement at Level filtering --- src/site/antora/modules/ROOT/pages/manual/architecture.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/site/antora/modules/ROOT/pages/manual/architecture.adoc b/src/site/antora/modules/ROOT/pages/manual/architecture.adoc index c98172be67d..fd6fe926a6b 100644 --- a/src/site/antora/modules/ROOT/pages/manual/architecture.adoc +++ b/src/site/antora/modules/ROOT/pages/manual/architecture.adoc @@ -281,8 +281,8 @@ it doesn't have a LoggerConfig with a name that exactly matches. It too inherits its logging level from LoggerConfig X. The table below 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 +the vertical header shows the Level associated with the appropriate LoggerConfig, while the horizontal +header shows the Level of the LogEvent. The intersection identifies whether the LogEvent would be allowed to pass for further processing (Yes) or discarded (No).