Merge branch 'development' into kk-snow-mcp

Author: katarzyna-koltun-mx

content/en/docs/deployment/docker-deploy/docker-pad.md

@@ -35,7 +35,7 @@ Portable App Distribution offers a more agile, user-centric, and efficient deplo
 
 Before you begin, ensure you have the following:
 
-* Mendix Studio Pro version 11.19, 11.6.5, or above
+* Mendix Studio Pro version 10.24.19, 11.19, 11.6.5, or above
 * A Mendix app that you want to deploy
 * Docker installed on your system (for building and running Docker images)
 * Access to a container registry (for pushing and pulling Docker images)

content/en/docs/deployment/general/pad/_index.md

@@ -33,7 +33,7 @@ To license a Mendix app on the Portable App Distribution, add it to your configu
 
 ## Prerequisites
 
-The Portable App Distribution functionality is available for Mendix Studio Pro version 11.9, 11.6.5 MTS, or above. The functionality will be enabled for more Studio Pro versions in future releases.
+The Portable App Distribution functionality is available in Mendix Studio Pro versions 10.24.19 LTS, 11.9, 11.6.5 MTS, and above. The functionality will be enabled for more Studio Pro versions in future releases.
 
 You must also ensure that you have the supported version of [Java Runtime Environment](/refguide/system-requirements/#java).
 

content/en/docs/deployment/mendix-cloud-deploy/change-plan.md

@@ -130,6 +130,10 @@ If the Technical Contact cancels a request, the plan change process is canceled
 
 ## Scheduling a Plan Change {#scheduling-a-plan-change}
 
+{{% alert color="warning" %}}
+Before scheduling a plan change request, check the [Mendix Status Page](https://status.mendix.com) for planned platform maintenance or Cloud Portal releases. Scheduling a plan change during maintenance windows may cause the request to fail.
+{{% /alert %}}
+
 If your request status is **Pending Schedule**:
 
 1. Open **Request Details** by clicking **Details** in the **Change Requests** tab.

content/en/docs/deployment/mx-azure/mx-azure-export-logs.md

@@ -46,6 +46,28 @@ To deploy your app to Cloud Foundry, perform the following steps:
       services:
       env:
     ```
-  
+
+    An example manifest file can look like the following:
+
+    ``` yaml
+    applications:
+    - name: mx-java-app
+      path: <path-to-zip>
+        memory: 1G
+        buildpacks:
+        - java_buildpack
+        services:
+        - <service instance_id to be bind>
+        - <service instance_id to be bind>
+        env:
+          JBP_CONFIG_OPEN_JDK_JRE: '{ jre: { version: 21.+}}'
+          JBP_LOG_LEVEL: INFO 
+          JAVA_OPTS: >
+            -Xmx512m
+            -Xms512m
+            -XX:MaxDirectMemorySize=20M
+            -XX:MaxMetaspaceSize=128M
+       ``` 
+
 5. Run the `cf push` command.
 6. Verify that the Mendix app has started successfully.

content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy-pad.md

@@ -56,7 +56,7 @@ To use the Conversational UI module, your Mendix Studio Pro version must be 10.2
 
 You must also ensure you have the other prerequisite modules that Conversational UI requires. These modules are included by default in the [Blank GenAI App](https://marketplace.mendix.com/link/component/227934), the [AI Bot Starter App](https://marketplace.mendix.com/link/component/227926), the [Support Assistant Starter App](https://marketplace.mendix.com/link/component/231035), and the [RFP Assistant Starter App](https://marketplace.mendix.com/link/component/235917). If not, you need to install them manually.
 
-* [GenAI Commons](https://marketplace.mendix.com/link/239448)
+* [GenAI Commons](https://marketplace.mendix.com/link/component/239448)
 * [Agent Commons](https://marketplace.mendix.com/link/component/240371)
 * [Atlas Core](https://marketplace.mendix.com/link/component/117187)
 * [Data Widgets](https://marketplace.mendix.com/link/component/116540) 

content/en/docs/marketplace/genai/reference-guide/conversational-ui.md

@@ -1,19 +1,19 @@
 ---
 title: "Consumed REST Service"
 url: /refguide/consumed-rest-services/
-description: "Presents an overview of consumed REST services and JSON in Mendix."
+description: "Describes how to interact with REST APIs in Mendix and build REST requests."
 weight: 15
 #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
 ---
 
 ## Consumed REST Services
 
-Mendix offers different features which allow you to interact with any REST API. You can use them to build and test your REST requests or create data structures in your project.
+Mendix offers features that allow you to interact with any REST API. You can use them to build and test your REST requests or create data structures in your project.
 
 ## Read More
 
-* [Consumed REST Service](/refguide/consumed-rest-service/), an overview on how to Consume a REST Service document
-* [Import an OpenAPI/Swagger contract](/refguide/consumed-rest-service/#installation), instructions on how to create a Consumed REST Service from an OpenAPI/Swagger contract
-* [Call REST Service](/refguide/call-rest-action/), a description of the microflow action
-* [Use Call REST Service Action in a Microflow](/refguide/integration/use-call-rest-action-in-microflow/), instructions on how to use the Call REST Service action in a microflow
-* [HttpRequest and HttpResponse System Entities](/refguide/http-request-and-response-entities/), an overview of these system entities in your domain model
+* [Consumed REST Service](/refguide/consumed-rest-service/) – Describes how to consume a REST service
+* [Import an OpenAPI/Swagger contract](/refguide/consumed-rest-service/#installation) – Describes how to create a consumed REST service from an OpenAPI/Swagger contract
+* [Call REST Service](/refguide/call-rest-action/) – Describes the Call REST Service microflow action
+* [Use Call REST Service Action in a Microflow](/refguide/integration/use-call-rest-action-in-microflow/) – Describes how to use the Call REST Service action in a microflow
+* [HttpRequest and HttpResponse System Entities](/refguide/http-request-and-response-entities/) – Describes these system entities in your domain model