updates per request

Author: katarzyna-koltun-mx

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md

@@ -7,7 +7,7 @@ weight: 30
 
 ## Introduction
 
-When running the Mendix Operator in Global mode, one installation of the Mendix Operator and Agent is sufficient to manage applications across multiple namespaces. This Operator mode is recommended for new customers, or customers that want to streamline and simplify their deployments and operations. For existing customers, and for use cases that require having a separate Operator instance for every namespace, the [Standard mode](/developerportal/deploy/standard-operator/) is still available and supported.
+When running the Mendix Operator in Global mode, one installation of the Mendix Operator and Agent is sufficient to manage applications across multiple namespaces.
 
 {{% alert color="warning" %}}
 It is essential to ensure that each namespace is exclusively managed by a single Operator. The deployment of two Operators, particularly with distinct versions, to manage the same namespace, may lead to conflicts, resulting in the cancellation and rollback of each operator's modifications.

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

@@ -40,6 +40,7 @@ For information on the current status of deployment to Mendix on Kubernetes and
 * 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.
+* Emails are now supported in Japanese and Korean languages, based on the language set in **User Settings**.
 
 ### August 7, 2025