From e7c036c9a34c39f2ca776c15a379cffedcb9867a Mon Sep 17 00:00:00 2001
From: Wolfgang Schueschen <76775650+WolfgangSn@users.noreply.github.com>
Date: Sat, 20 Mar 2021 12:17:34 +0100
Subject: [PATCH] Update logging.md (#1515)

Both, the text description and the example output talk about logging level debug for the heating rule but the statement to set the log level used level info instead of level debug.
To match the description and the example output it has to be log:set debug org.openhab.core.model.script.heating

Signed-off-by: Wolfgang Schlueschen github@ncc1701d.33mail.com
---
 administration/logging.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/administration/logging.md b/administration/logging.md
index 3db1e3211..75683b003 100644
--- a/administration/logging.md
+++ b/administration/logging.md
@@ -161,7 +161,7 @@ logDebug("heating", "Bedroom: Temperature: {}, Mode: {}", Bedroom_Temp.state, Be
 The main package of all script/rules based log entries is predefined as `org.openhab.core.model.script`.
 The chosen subpackage is appended to the end of the main package.
 It can be useful for filtering or package-based log level settings.
-For example you can use `log:set info org.openhab.core.model.script` and `log:set info org.openhab.core.model.script.heating` while you work on the heating rules to get debug level output for heating rules and only info level for the rest of your rules files so you don't flood the log with too many entries that are irrelevant at that point in time.
+For example you can use `log:set info org.openhab.core.model.script` and `log:set debug org.openhab.core.model.script.heating` while you work on the heating rules to get debug level output for heating rules and only info level for the rest of your rules files so you don't flood the log with too many entries that are irrelevant at that point in time.
 
 An example output of the last log statement above is: