Add a note that obfuscate literals does not work with malformed queries (neo4j#2318) (neo4j#2326)

Author: renetapopova

modules/ROOT/pages/configuration/configuration-settings.adoc

@@ -2616,6 +2616,10 @@ a|A boolean.
 m|+++false+++
 |===
 
+[NOTE]
+====
+Keep in mind that if Neo4j receives a malformed query that cannot be parsed, it cannot obfuscate its literals (because it does not know which parts are literals) and, therefore, the query text will not be included in any logging.
+====
 
 [role=label--dynamic]
 [[config_db.logs.query.parameter_logging_enabled]]

modules/ROOT/pages/monitoring/logging.adoc

@@ -840,8 +840,10 @@ This is useful when Cypher queries expose sensitive information.
 ====
 Node labels, relationship types, and map property keys are still shown.
 Changing the setting does not affect cached queries.
-Therefore, if you want the switch to have an immediate effect, you must also clear the query cache; `CALL db.clearQueryCaches()`.
+Therefore, if you want the switch to have an immediate effect, you must also clear the query cache; `CALL db.clearQueryCaches()`. +
+Also, keep in mind that if Neo4j receives a malformed query that cannot be parsed, it cannot obfuscate its literals (because it does not know which parts are literals) and, therefore, the query text will not be included in any logging.
 ====
+
 [WARNING]
 ====
 This does not obfuscate literals in parameters.