1 files changed, 11 insertions, 9 deletions
diff --git a/plugins/InspectionGadgets/src/inspectionDescriptions/LogStatementGuardedByLogCondition.html b/plugins/InspectionGadgets/src/inspectionDescriptions/LogStatementGuardedByLogCondition.html
index bc16a72efc06..dd4a0b561feb 100644
--- a/plugins/InspectionGadgets/src/inspectionDescriptions/LogStatementGuardedByLogCondition.html
+++ b/plugins/InspectionGadgets/src/inspectionDescriptions/LogStatementGuardedByLogCondition.html
@@ -1,17 +1,19 @@
 <html>
 <body>
-Reports log statements with non-constant arguments which are not
-surrounded by a guard condition.
-The evaluation of the arguments of a log statement can be expensive.
-Surrounding a log statement with a guard clause prevents that cost when the logging
-is disabled for the level used by the logging statement. This is especially for the
-least serious level (trace, debug, finest) of logging statements, because those are
+Reports logging calls with non-constant arguments which are not surrounded by a guard condition.
+The evaluation of the arguments of a logging call can be expensive.
+Surrounding a logging call with a guard clause prevents that cost, when the logging
+is disabled for the level used by the logging statement. This is especially useful for the
+least serious level (trace, debug, finest) of logging calls, because those are
 most often disabled in a production environment.
 <!-- tooltip end -->
 <p>
-Use the text field below to specify the logger class name used. Use the table
-to specify the log methods this inspection should warn on, with the corresponding
-logging condition text.
+Use the text field below to specify the logger class name used.
+<p>
+Use the table to specify the logging methods this inspection should warn on, with the corresponding
+log condition text.
+<p>
+Use the checkbox below to let this inspection flag all unguarded log calls, not only those with non-constant arguments.
 <p>
 <small>New in 8, Powered by InspectionGadgets</small>
 </body>