From f4578c9572771a34cf0bf9f12de41d869507e6b2 Mon Sep 17 00:00:00 2001 From: Mickey Maler Date: Wed, 26 Jul 2023 12:20:12 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Ladislav Thon --- docs/src/main/asciidoc/logging.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/logging.adoc b/docs/src/main/asciidoc/logging.adoc index e869134612e028..a0cd88d68ca235 100644 --- a/docs/src/main/asciidoc/logging.adoc +++ b/docs/src/main/asciidoc/logging.adoc @@ -25,7 +25,7 @@ You can use any of the <>: [[jboss-logging]] == Use JBoss Logging for application logging -Using the JBoss Logging API, your application requires no additional dependencies, as Quarkus automatically provides it. +When using the JBoss Logging API, your application requires no additional dependencies, as Quarkus automatically provides it. .An example of using the JBoss Logging API to log a message: [source,java] @@ -802,7 +802,7 @@ In Quarkus, the MDC provider has a specific implementation for handling the reac As a result, you can still access the MDC data in various scenarios: * After asynchronous calls, like for example, when a REST client returns a Uni. -* When dealing with code submitted to the `ManagedExecutor` using `@Inject org.eclipse.microprofile.context.ManagedExecutor executor`. +* In code submitted to `org.eclipse.microprofile.context.ManagedExecutor`. * In code executed with `vertx.executeBlocking()`. NOTE: NOTE: MDC data is stored in a duplicated context, isolated for processing.