Improve Logging guide regarding logging adapters

We had several complaints that it was hard to notice people would use
their favorite logging API so I made it a lot more explicit.

Also I made the APIs titles so that they could be included in the TOC.

Author: gsmet

docs/src/main/asciidoc/logging.adoc

@@ -9,21 +9,40 @@ include::_attributes.adoc[]
 :categories: core,getting-started,observability
 :diataxis-type: reference
 :topics: logging,observability
+:toclevels: 4
 
 Read about the use of logging API in {project-name}, configuring logging output, and using logging adapters to unify the output from other logging APIs.
 
 include::{includes}/observability-include.adoc[]
 
 Quarkus uses the JBoss Log Manager logging backend for publishing application and framework logs.
 Quarkus supports the JBoss Logging API and multiple other logging APIs, seamlessly integrated with JBoss Log Manager.
-You can use any of the <<logging-apis,following APIs>>:
 
-* link:https://github.com/jboss-logging/jboss-logging[JBoss Logging]
-* link:https://docs.oracle.com/en/java/javase/17/docs/api/java.logging/java/util/logging/package-summary.html[JDK `java.util.logging` (JUL)]
-* link:https://www.slf4j.org/[SLF4J]
-* link:https://commons.apache.org/proper/commons-logging/[Apache Commons Logging]
-* link:https://logging.apache.org/log4j/2.x/[Apache Log4j 2]
-* link:https://logging.apache.org/log4j/1.2/[Apache Log4j 1]
+This means you can use your favorite logging API with Quarkus, providing you add the <<logging-apis,appropriate adapter>> to your application:
+
+[cols="2,1", options="header"]
+|===
+| Logging API
+| Adapter
+
+| link:https://github.com/jboss-logging/jboss-logging[JBoss Logging]
+| Built-in
+
+| link:https://docs.oracle.com/en/java/javase/17/docs/api/java.logging/java/util/logging/package-summary.html[JDK `java.util.logging` (JUL)]
+| Built-in
+
+| link:https://www.slf4j.org/[SLF4J]
+| <<logging-adapters-slf4j,SLF4J adapter>>
+
+| link:https://commons.apache.org/proper/commons-logging/[Apache Commons Logging]
+| <<logging-adapters-commons-logging,Commons Logging adapter>>
+
+| link:https://logging.apache.org/log4j/2.x/[Apache Log4j 2]
+| <<logging-adapters-log4j2,Log4j 2 adapter>>
+
+| link:https://logging.apache.org/log4j/1.2/[Apache Log4j 1]
+| <<logging-adapters-log4j,Log4j 1 adapter>>
+|===
 
 [[jboss-logging]]
 == Use JBoss Logging for application logging
@@ -765,50 +784,59 @@ The logging implementation is not included in the native executable, but you can
 
 These adapters are available for popular open-source logging components, as explained in the next chapter.
 
+[[logging-adapters]]
 === Add a logging adapter to your application
 
-For each logging API that is not `jboss-logging`:
+For each logging API that is not JBoss Logging, add a logging adapter library to ensure that messages logged through these APIs are routed to the JBoss Log Manager backend.
+You can then verify whether the logs generated by the added library adhere to the same format as the other Quarkus logs.
 
-. Add a logging adapter library to ensure that messages logged through these APIs are routed to the JBoss Log Manager backend.
-+
 NOTE: This step is unnecessary for libraries that are dependencies of a Quarkus extension where the extension handles it automatically.
-+
-* Apache Commons Logging:
-+
+
+[[logging-adapters-slf4j]]
+==== SLF4J
+
+The SLF4J adapter is provided by the following dependency:
+
 [source,xml,role="primary asciidoc-tabs-target-sync-cli asciidoc-tabs-target-sync-maven"]
 .pom.xml
 ----
 <dependency>
-    <groupId>org.jboss.logging</groupId>
-    <artifactId>commons-logging-jboss-logging</artifactId>
+    <groupId>org.jboss.slf4j</groupId>
+    <artifactId>slf4j-jboss-logmanager</artifactId>
 </dependency>
 ----
-+
+
 [source,gradle,role="secondary asciidoc-tabs-target-sync-gradle"]
 .build.gradle
 ----
-implementation("org.jboss.logging:commons-logging-jboss-logging")
+implementation("org.jboss.slf4j:slf4j-jboss-logmanager")
 ----
 
-* Log4j:
-+
+[[logging-adapters-commons-logging]]
+==== Apache Commons Logging
+
+The Commons Logging adapter is provided by the following dependency:
+
 [source,xml,role="primary asciidoc-tabs-target-sync-cli asciidoc-tabs-target-sync-maven"]
 .pom.xml
 ----
 <dependency>
-    <groupId>org.jboss.logmanager</groupId>
-    <artifactId>log4j-jboss-logmanager</artifactId>
+    <groupId>org.jboss.logging</groupId>
+    <artifactId>commons-logging-jboss-logging</artifactId>
 </dependency>
 ----
-+
+
 [source,gradle,role="secondary asciidoc-tabs-target-sync-gradle"]
 .build.gradle
 ----
-implementation("org.jboss.logmanager:log4j-jboss-logmanager")
+implementation("org.jboss.logging:commons-logging-jboss-logging")
 ----
 
-* Log4j 2:
-+
+[[logging-adapters-log4j2]]
+==== Log4j 2
+
+The Log4j 2 adapter is provided by the following dependency:
+
 [source,xml,role="primary asciidoc-tabs-target-sync-cli asciidoc-tabs-target-sync-maven"]
 .pom.xml
 ----
@@ -817,37 +845,38 @@ implementation("org.jboss.logmanager:log4j-jboss-logmanager")
     <artifactId>log4j2-jboss-logmanager</artifactId>
 </dependency>
 ----
-+
+
 [source,gradle,role="secondary asciidoc-tabs-target-sync-gradle"]
 .build.gradle
 ----
 implementation("org.jboss.logmanager:log4j2-jboss-logmanager")
 ----
-+
+
 [NOTE]
 ====
 Do not include any Log4j dependencies, as the `log4j2-jboss-logmanager` library contains everything needed to use Log4j as a logging implementation.
 ====
 
-* SLF4J:
-+
+[[logging-adapters-log4j]]
+==== Log4j
+
+The Log4j adapter is provided by the following dependency:
+
 [source,xml,role="primary asciidoc-tabs-target-sync-cli asciidoc-tabs-target-sync-maven"]
 .pom.xml
 ----
 <dependency>
-    <groupId>org.jboss.slf4j</groupId>
-    <artifactId>slf4j-jboss-logmanager</artifactId>
+    <groupId>org.jboss.logmanager</groupId>
+    <artifactId>log4j-jboss-logmanager</artifactId>
 </dependency>
 ----
-+
+
 [source,gradle,role="secondary asciidoc-tabs-target-sync-gradle"]
 .build.gradle
 ----
-implementation("org.jboss.slf4j:slf4j-jboss-logmanager")
+implementation("org.jboss.logmanager:log4j-jboss-logmanager")
 ----
 
-. Verify whether the logs generated by the added library adhere to the same format as the other Quarkus logs.
-
 === Use MDC to add contextual log information
 
 Quarkus overrides the logging Mapped Diagnostic Context (MDC) to improve compatibility with its reactive core.