minor doc changes

qos-ch · Jun 17, 2021 · 6f23d94 · 6f23d94
1 parent ba62fdc
commit 6f23d94
Show file tree

Hide file tree

Showing 2 changed files with 25 additions and 21 deletions.
diff --git a/slf4j-site/src/site/pages/manual.html b/slf4j-site/src/site/pages/manual.html
@@ -242,7 +242,8 @@ <h3 class="doAnchor" name="fluent">Fluent Logging API</h3>
       pairs as separates objects. The default implementation as
       shipping in the <code>org.slf4j.Logger</code> class
       <em>prefixes</em> key-value pairs to the message.  Logging
-      backends are free to customize the output as they see fit.</p>
+      backends are free and even encouraged to offer a more
+      customizable behaviour.</p>
 
 
       <h3 class="doAnchor" name="swapping">Binding with a logging

diff --git a/slf4j-site/src/site/pages/news.html b/slf4j-site/src/site/pages/news.html
@@ -44,6 +44,26 @@ <h1>SLF4J News</h1>
 
    <h3>XXth of June, 2021 - Release of SLF4J 2.0.0-alpha2</h3>
 
+   <p class="highlight">The the 2.0.x series requires Java&nbsp;8 and
+   adds a backward-compatible <a
+   href="manual.html#fluent">fluent logging api</a>.
+   <br/>   <br/>
+   Moreover, SLF4J has been modularized per <a
+   href="http://openjdk.java.net/projects/jigsaw/spec/">JPMS/Jigsaw</a>
+   specificaton. The resulting internal changes are <a class="big
+   bold" href="faq.html#changesInVersion18">detailed</a> in the FAQ
+   page.
+   </p>
+
+   <p>SLF4J version 2.0.0 requires Java 8. It builds upon the 1.8.x
+   series and adds a backward-compatible <a
+   href="manual.html#fluent">fluent logging api</a>.  By
+   backward-compatible, we mean that existing logging frameworks do
+   not have to be changed for the user to benefit from the fluent
+   logging API.
+   </p>
+
+
    <p>Fixed important bug in the fluent API. The
    <code>LoggingEventBuilder.addArgument(Supplier)</code> method now
    takes <code>Supplier&lt;?&gt;</code> and not
@@ -100,33 +120,16 @@ <h3>31st of October, 2019 - Release of SLF4J 1.7.29</h3>
 
    <h3>October 1st, 2019  - Release of SLF4J 2.0.0-alpha1</h3>
 
-   <p class="highlight">The the 2.0.x series requires Java&nbsp;8 and
-   adds a backward-compatible <a
-   href="manual.html#fluent">fluent logging api</a>.
-   <br/>   <br/>
-   Moreover, SLF4J has been modularized per <a
-   href="http://openjdk.java.net/projects/jigsaw/spec/">JPMS/Jigsaw</a>
-   specificaton. The resulting internal changes are <a class="big
-   bold" href="faq.html#changesInVersion18">detailed</a> in the FAQ
-   page.
-   </p>
-
-   <p>SLF4J version 2.0.0 requires Java 8. It builds upon the 1.8.x
-   series and adds a backward-compatible <a
-   href="manual.html#fluent">fluent logging api</a>.  By
-   backward-compatible, we mean that existing logging frameworks do
-   not have to be changed for the user to benefit from the fluent
-   logging API.
-   </p>
 
    <p>&bull; Refactored the fluent-api in
    <code>org.slf4j.Logger</code> interface to ease the work required
    by downstream implementations.
    </p>
 
-   <p>&bull; By default, when using the fluent-API
+   <p>&bull; <em>By default</em>, when using the fluent-API
    <code>org.slf4j.Logger</code> will merge into the message part any
-   marker and key-value data passed to it.</p>
+   marker and key-value data passed to it. Non default implementation
+   are encouraged to implement a more customizable behavior.</p>
 
    <p>&bull; Fix the double back-end initializatoin problem reported
    in <a href="https://jira.qos.ch/browse/SLF4J-463">SLF4J-463</a> by