Change info note about DataStorage_QueryPlan from trace to debug and reword messages

Author: passalaqua

content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md

@@ -173,10 +173,10 @@ The database follows the below process:
 
 Even though the query is using a view that also includes address information, the database ignores this information, as it is not relevant when counting customers by age.
 
-If you set the `DataStorage_QueryPlan` log node to Trace, you see the query plan for your all your queries in the Mendix Runtime log.
+If you set the `DataStorage_QueryPlan` log node to Debug, you see the query plan for all your queries in the Mendix Runtime log.
 
 {{% alert color="warning" %}}
-The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.
+The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production.
 {{% /alert %}}
 
 ## Read More

content/en/docs/refguide10/modeling/domain-model/entities/view-entities/use-view-entities.md

@@ -127,7 +127,7 @@ Even though the query is using a view that also includes address information, th
 If you set the `DataStorage_QueryPlan` log node to Trace, you see the query plan for all your queries in the Mendix Runtime log.
 
 {{% alert color="warning" %}}
-The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.
+The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production.
 {{% /alert %}}
 
 ## Read More

content/en/docs/refguide10/runtime/logging/_index.md

@@ -64,7 +64,7 @@ This list is currently incomplete and is being updated.
 | Connector | Logs when standard or custom request handlers (added through Core#addRequestHandler) are registered, or when a path is called that does not have a registered request handler. |
 | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. |
 | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. |
-| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.{{% /alert %}} |
+| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production.{{% /alert %}} |
 | DocumentExporter | Logs messages related to the templating engine that generates documents. |
 | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). |
 | InvalidRequestLimiter | Logs messages related to responses being throttled due to invalid requests. |

content/en/docs/refguide8/runtime/logging.md

@@ -61,7 +61,7 @@ This list is currently incomplete and is being worked on.
 | Connector | |
 | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. |
 | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. |
-| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.{{% /alert %}} 
+| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production.{{% /alert %}} |
 | DocumentExporter | Logs messages related to the templating engine that generates documents. |
 | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). |
 | I18NProcessor | Logs messages related to translation of the app. |

content/en/docs/refguide9/runtime/logging.md

@@ -64,7 +64,7 @@ This list is currently incomplete and is being updated.
 | Connector | |
 | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. |
 | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. |
-| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.{{% /alert %}} 
+| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production.{{% /alert %}} |
 | DocumentExporter | Logs messages related to the templating engine that generates documents. |
 | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). |
 | IDResolution | Information on retrieval queries and runtime operations that are being executed. |