Update mendix-for-private-cloud.md

Author: katarzyna-koltun-mx

content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md

@@ -12,31 +12,33 @@ For information on the current status of deployment to Mendix on Kubernetes and
 
 ## 2025
 
-### August ???, 2025
+### August 29, 2025
 
 #### Mendix Operator v2.23.0 {#2.23.0}
 
-* We added a  new `leaderless` deployment mode for the `runtimeLeaderSelection` option. This mode is currently in preview.
-   * This is a new option that can be used, in addition of the current `assigned` and `none` modes.
-   * Setting `runtimeLeaderSelection` to `leaderless` will only use one Deployment instead of `master` and `worker`. Mendix Runtime nodes will decide which one gets to run any exclusive task.
-   * This mode uses a simplified Java launch process and uses a more efficient way of generating JSON logs.
-   * To use `leaderless` mode, the Mendix app needs to be based on Mendix 10.24 or a higher version.
-* We have adjusted the Runtime liveness and readiness probes; in `leaderless` deployment mode, the Mendix Runtime's built-in self-test will be used for the liveness and readiness probes.
-* We have addressed a few redundant API calls to reduce API calls in a few scenarios.
-* We fixed an issue when a Prometheus metrics scaper would reject metrics from Mendix 11 apps.
+* In addition to the current `assigned` and `none` modes, we have added a new `leaderless` deployment mode for the `runtimeLeaderSelection` option. This mode is currently in preview.
+
+    Setting `runtimeLeaderSelection` to `leaderless` uses only one Deployment instead of `master` and `worker`. Mendix Runtime nodes decide which one gets to run any exclusive task. The mode uses a simplified Java launch process and uses a more efficient way of generating JSON logs. To use `leaderless` mode, the Mendix app needs to be based on Mendix 10.24 or a higher version.
+  
+* We have adjusted the Runtime liveness and readiness probes. In `leaderless` deployment mode, the Mendix Runtime's built-in self-test is now used for the liveness and readiness probes.
+* We have addressed a few redundant API calls to reduce API calls in a small number of scenarios.
+* We have fixed an issue when a Prometheus metrics scaper would reject metrics from Mendix 11 apps.
 * We have added a workaround to improve handling of bucket prefixes containing `/` characters.
-* We have improved logging of some startup and other errors - to provide clearer error messages and more relevant context.
-* We removed license checks from the Mendix Operator. Starting version 2.23.0 of the Mendix Opeartor, only Runtime licenses are required (to remove [trial restrictions](/developerportal/deploy/licensing-apps-outside--mxcloud/) from the Mendix Runtime). The Operator will show its status as **Licensed** even when no Operator license is applied.
+* To provide clearer error messages and more relevant context, we have improved the logging of some startup and other errors.
+* We have removed license checks from the Mendix Operator. Starting version 2.23.0 of the Mendix Opeartor, only Runtime licenses are required (to remove [trial restrictions](/developerportal/deploy/licensing-apps-outside--mxcloud/) from the Mendix Runtime). The Operator will show its status as **Licensed** even when no Operator license is applied.
 * We updated internal handling logic for the `MendixApp`, `Build` and `Runtime` CRD controllers (Ticket 251404).
-  * The `Build` controller now only checks pod attributes that are necessary to complete a build.
-  * The `MendixApp` and `Runtime` controllers now allow processing of some chnages if a build fails.
-    For example, it's possible to start an environment or change the **MxAdmin** password even when the build fails - in this case, the previous build will be used instead.
-* When enabling the *Prevent data deletion* option, Mendix 9.6 (or newer) apps will no longer try to delete files from unreferenced *System.FileDocument*, so that Mendix apps would be able to run without permissions to delete files.
+
+    * The `Build` controller now only checks pod attributes that are necessary to complete a build.
+    * The `MendixApp` and `Runtime` controllers now allow processing of some chnages if a build fails.
+
+        For example, it is possible to start an environment or change the **MxAdmin** password even when the build fails - in this case, the previous build will be used instead.
+
+* When enabling the **Prevent data deletion** option, Mendix 9.6 (or newer) apps will no longer try to delete files from unreferenced *System.FileDocument*, so that Mendix apps would be able to run without permissions to delete files.
 * We have updated components to use Go 1.24 and the latest dependency versions in order to improve security score ratings for container images.
 * We have updated documentation that OpenShift 4.19 is supported by the Mendix Operator.
 * We have deprecated support for Tencent COS storage.
-* If an app pod crashes or restarts, the MendixApp CR will show the reason for the restart and the Mendix Runtime's UNIX exit code.
-* We have addressed a rare bug where the Agent sometimes crashed with a panic when a network connection is lost.
+* If an app pod crashes or restarts, the MendixApp CR now shows the reason for the restart and the Mendix Runtime's UNIX exit code.
+* We have addressed a rare bug where the Agent sometimes crashed with a panic when a network connection was lost.
 * Upgrading to Mendix Operator v2.23.0 from a previous version will restart environments managed by that version of the Operator. Environments with two or more replicas and a **PreferRolling** update strategy are restarted without downtime.
 
 ### August 7, 2025