edit

Author: ConnorLand

content/en/docs/releasenotes/studio-pro/11/11.6.md

@@ -25,10 +25,10 @@ Portable App Distribution revolutionizes server deployments and simplifies local
 
 - We introduced an opt-in runtime setting `MaxRetrieveAmount` that limits the maximum amount of objects retrieved by database datasource operation. (Tickets 236618, 247111)
 - We now clean up pending `MendixRuntime-UpdateScheduledEvent` and `MendixRuntime-DeleteScheduledEvent` system tasks before synchronizing scheduled events. (Tickets 261783, 268157, 268325, 268970, 269591, 270061, 270125, 271453, 272736, 273833, 273982)
-- We improved the resizing behavior of object list grids when editing pluggable widget properties in Studio Pro. These grids now resize when their dialog box is resized. This enhancement, for example, improves the resizing of **Columns** grids in data grid 2.
+- We improved the resizing behavior of object list grids when editing pluggable widget properties in Studio Pro. These grids now resize when their dialog box is resized. This enhancement, for example, improves the resizing of columns' grids in data grid 2.
 - We updated the .NET runtime version installed with Studio Pro to .NET 10.0.3.
 - We no longer create ProcessedTask entries for the `MendixRuntime-UpdateScheduledEvent` and `MendixRuntime-DeleteScheduledEvent` system tasks.
-- We have changed the level of log messages on the `SystemTask` log node to debug. For non-development deployments this log node was set to `info`, which was causing too many messages.
+- We have changed the level of log messages on the `SystemTask` log node to `debug` (for non-development deployments this log node was set to `info`, which was causing too many messages).
 - We changed how popups are initially rendered in the React client. They will now not be available to UI testing frameworks until they are actually ready to be used.
 
 ### Fixes
@@ -45,8 +45,8 @@ Portable App Distribution revolutionizes server deployments and simplifies local
 - We fixed an issue where an incorrect runtime warning was thrown for missing parameters during database retrieval with an XPath constraint, even though those parameters were omitted from the client request because they were empty. (Ticket 269590, Ticket 269780)
 - We fixed an issue where a snippet variable was not available in expressions for conditional visibility and editability. (Ticket 270419)
 - We fixed an issue where an OQL with a `UNION` of more than two `NULL` and non-`NULL` expressions could fail. For example, a `UNION` query of three `SELECT`s with two `NULL`s and a numeric value or object ID no longer fails in PostgreSQL. (Ticket 273187)
-- We fixed an issue where snippet variables were not working properly in conditional settings in snippets. (Ticket 273971)
 - We fixed an issue in offline apps where database retrievals using reverse associations returned empty or incorrect results. (Ticket 273198)
+- We fixed an issue where snippet variables were not working properly in conditional settings in snippets. (Ticket 273971)
 - We now ensure all columns in all branches of the top level `UNION` in an OQL query have a name or alias to avoid issues with databases that require them, like SQL Server.
 - The Workflow Commons module URL now correctly respects the `MarketplaceUrlP` configuration variable.
 - We fixed an issue where the automatic update of conditional settings was not triggered correctly when using invalid local variables.