From 65794f3f19662c45154b4a9bf20abb65348ac202 Mon Sep 17 00:00:00 2001
From: Antonio Goncalves <antonio.goncalves@gmail.com>
Date: Mon, 6 Apr 2020 16:13:56 +0200
Subject: [PATCH] Update docs/src/main/asciidoc/logging.adoc

Clearer

Co-Authored-By: David M. Lloyd <david.lloyd@redhat.com>
---
 docs/src/main/asciidoc/logging.adoc | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/src/main/asciidoc/logging.adoc b/docs/src/main/asciidoc/logging.adoc
index d10dc9f7253898..ec611c80285ae7 100644
--- a/docs/src/main/asciidoc/logging.adoc
+++ b/docs/src/main/asciidoc/logging.adoc
@@ -61,12 +61,12 @@ There are several log levels you can use:
 [cols="<m,<5",options="header"]
 |===
 |Level|Description
-|FATAL|For events that indicate a critical service failure
-|ERROR|To indicate a disruption in a request or the inability to service a request
-|WARN|May indicate a non-critical service error
-|INFO|For crucial related information
-|DEBUG|For messages that convey extra information
-|TRACE|Log low-level priority messages
+|FATAL|A critical service failure/complete inability to service requests of any kind
+|ERROR|A significant disruption in a request or the inability to service a request
+|WARN|A non-critical service error or problem that may not require immediate correction
+|INFO|Service lifecycle events or important related very-low-frequency information
+|DEBUG|Messages that convey extra information regarding lifecycle or non-request-bound events which may be helpful for debugging
+|TRACE|Messages that convey extra per-request debugging information that may be very high frequency
 |===
 
 [id="format-string"]