Apply review suggestions (2)

Author: ppkarwasz

src/site/antora/modules/ROOT/pages/manual/architecture.adoc

@@ -42,7 +42,7 @@ package "Configuration" as c {
 
     class Configuration {
       Appender[] appenders
-      Filter[] filters
+      Filter filter
       LoggerConfig[] loggerConfigs
       LoggerConfig getLoggerConfig(String name)
       StrSubstitutor substitutor
@@ -198,7 +198,7 @@ LoggerContext --> "0..*" Logger
 
 class Configuration {
   Appender[] appenders
-  Filter[] filters
+  Filter filter
   LoggerConfig[] loggerConfigs
   LoggerConfig getLoggerConfig(String name)
   StrSubstitutor substitutor
@@ -237,7 +237,7 @@ LoggerContext --> Configuration
 
 class Configuration #line.bold {
   Appender[] appenders
-  Filter[] filters
+  Filter filter
   LoggerConfig[] loggerConfigs
   LoggerConfig getLoggerConfig(String name)
   StrSubstitutor substitutor
@@ -397,7 +397,7 @@ A `LoggerConfig` essentially contains
 
 class Configuration {
   Appender[] appenders
-  Filter[] filters
+  Filter filter
   LoggerConfig[] loggerConfigs
   LoggerConfig getLoggerConfig(String name)
   StrSubstitutor substitutor
@@ -541,13 +541,13 @@ In addition to <<LoggerConfig,the level-based filtering facilitated by `LoggerCo
 
 class Configuration {
   Appender[] appenders
-  Filter[] filters
+  Filter filter
   LoggerConfig[] loggerConfigs
   LoggerConfig getLoggerConfig(String name)
   StrSubstitutor substitutor
 }
 
-Configuration --> "0..*" Filter
+Configuration --> Filter
 
 Configuration --> "0..*" LoggerConfig
 
@@ -575,6 +575,10 @@ class AppenderRef {
   Filter filter
 }
 
+class AppenderControl {
+  Filter filter
+}
+
 AppenderRef --> Filter
 
 AppenderControl --> Filter
@@ -599,7 +603,7 @@ See xref:manual/appenders.adoc[] for the complete guide.
 
 class Configuration {
   Appender[] appenders
-  Filter[] filters
+  Filter filter
   LoggerConfig[] loggerConfigs
   LoggerConfig getLoggerConfig(String name)
   StrSubstitutor substitutor

src/site/antora/modules/ROOT/pages/manual/filters.adoc

@@ -21,11 +21,13 @@
 
 Filters are Log4j plugins that evaluate the parameters of a logging call or a log event and return one of three results:
 
-ACCEPT:: The log event is accepted by the filter and goes to the next stage of the logging pipeline.
+ACCEPT:: The filter accepts the log event.
+Other filters in the same filtering stage are not evaluated.
 
-DENY:: The log event is unconditionally dropped.
+DENY:: The filter drops the log event.
 
 NEUTRAL:: Log4j behaves as if the filter was not present.
+It is evaluated by the next filter in the filter chain.
 
 Filters can be used at each level of the
 xref:manual/architecture.adoc#architecture-diagram[logging pipeline]:
@@ -118,6 +120,8 @@ xref:manual/appenders.adoc#AsyncAppender[asynchronous appenders].
 ....
 @startuml
 start
+:LogEvent;
+
 group LoggerConfig
 repeat
 
@@ -151,8 +155,9 @@ until it reaches the logger that references the chosen appender.
 [plantuml]
 ....
 @startuml
-!pragma useVerticalIf on
 start
+:LogEvent;
+
 group AppenderControl
 
 :AppenderControl#callAppender();
@@ -190,9 +195,9 @@ of the appender reference.
 ....
 @startuml
 start
-group Appender
+:LogEvent;
 
-:Appender#append();
+group Appender
 
 if (Apply appender filter) then (DENY)
     #pink:Discard;
@@ -202,7 +207,7 @@ else (not DENY)
     label a1
 endif
 end group
-#palegreen:Log message;
+#palegreen:Appender#append();
 @enduml
 ....
 
@@ -323,7 +328,7 @@ The `Filters` plugin sequentially evaluates each sub-filter and:
 * if the sub-filter return `NEUTRAL`, the `Filters` plugin evaluates the next sub-filter in the chain.
 * if the last sub-filter returns `NEUTRAL`, the `Filters` plugin returns `NEUTRAL`.
 
-The `Filters` plugin together with the ternary logic of filters, can be used to express all the boolean operators.
+The `Filters` plugin together with the ternary logic of filters, can be used to express most boolean operators.
 In the following examples `A` and `B` are two filters.
 
 `NOT A`::