Merge pull request #10028 from mendix/olu-app-node-aug25

feat: updating the docs with latest info from dev

Author: OlufunkeMoronfolu

content/en/docs/support/new-app-node-request-template.md

@@ -1,7 +1,7 @@
 ---
 title: "App Node Requests"
 url: /support/new-app-node-request-template/
-description: "Describes how to deploy a new licensed node in Mendix Cloud or on-premises/virtual Mendix on Kubernetes."
+description: "Describes how to resize environments, offboard an environment, and request a new licensed node in Mendix Cloud or on-premises/virtual Mendix on Kubernetes."
 weight: 30
 aliases:
     - /developerportal/support/new-app-request-template.html
@@ -13,46 +13,48 @@ aliases:
 
 ## Introduction
 
-There are a number of changes to licensed app nodes which you need to request outside the Mendix Portal.
-
-These changes, listed below, are described in this document.
+This document describes some changes to licensed app nodes that you can request outside the Mendix Portal. These changes are listed below.
 
 * [Requesting a New Licensed App Node](#new-node)
 * [Resizing an Existing Environment](#resize)
 * [Offboarding an Environment](#offboard)
 
 ## Requesting a New Licensed App Node{#new-node}
 
-If you want to deploy your app to a new licensed node in Mendix Cloud, Mendix Cloud Dedicated, or on-premises/virtual Mendix on Kubernetes, you can request one from Mendix Support.
+To deploy your app to a new licensed node, you will need to request a node from Mendix Support. When submitting your request, you must specify the hosting type for your application. The available options are:
 
-Fill in the required details for the new licensed app node on the [Request New App Node](https://newnode.mendix.com/) page. If your request matches your entitlements, your Mendix Cloud node is created automatically. Mendix Support will contact you via a ticket in the [Mendix Support Portal](https://support.mendix.com/) if more information is needed or to send you keys for apps deployed on-premises or to a virtual Mendix on Kubernetes.
+* **Mendix Cloud** – Select this option for apps deployed to public Mendix Cloud.
+* **Mendix Cloud Dedicated** – Select this option for apps deployed to Mendix Cloud Dedicated.
+* **Mendix for Private Cloud** – Select this option for apps deployed to Kubernetes using the Mendix Operator. Refer to [Mendix on Kubernetes](/developerportal/deploy/private-cloud/) for more information.
+* **Server-based (Windows Server)** – Select this option for apps deployed to Windows. You are required to enter the **Server ID**, which you can retrieve by following the steps in the [Windows Server](/developerportal/deploy/licensing-apps-outside-mxcloud/#windows-server) section of *Licensing Apps*.
+* **Container-based (Docker, Cloud Foundry, Kubernetes)** – Select this option for apps deployed to Docker, Cloud Foundry, or Kubernetes, without Mendix Operator.
+* **SAP** – Select this option for apps deployed to SAP.
 
-By default, all developers in your organization can create node requests. You can limit this to Mendix Admins only by contacting your Customer Success Manager or requesting it via a support ticket.
+To request your node from Mendix Support, complete the following steps:
 
-These are the hosting types that you can make requests for:
+1. **Submit the request** – On the [Request New App Node](https://newnode.mendix.com/) page, fill in the required details, including your desired hosting type.
+2. **Automatic node creation** – If your request matches your entitlements, your Mendix Cloud node will be created automatically.
+3. **Follow-up** – Mendix Support will contact you via a ticket in the [Mendix Support Portal](https://support.mendix.com/) if additional information is needed or to provide keys for apps deployed on-premises or using a virtual Mendix on Kubernetes.
 
-* **Mendix Cloud** — Select this option for apps deployed to public Mendix Cloud.
-* **Mendix Cloud Dedicated** — Select this option for apps deployed to Mendix Cloud Dedicated.
-* **Mendix for Private Cloud** — Select this option for apps deployed to Kubernetes using the Mendix Operator. Refer to [Mendix on Kubernetes](/developerportal/deploy/private-cloud/) for more information.
-* **Server-based (Windows Server)** — Select this option for apps deployed to Windows. You are required to enter the Server ID, which you can retrieve by following the steps in the [Windows Server](/developerportal/deploy/licensing-apps-outside-mxcloud/#windows-server) section of *Licensing Apps*.
-* **Container-based (Docker, Cloud Foundry, Kubernetes)** — Select this option for apps deployed to Docker, Cloud Foundry, or Kubernetes, without Mendix Operator).
-* **SAP** — Select this option for apps deployed to SAP.
+{{% alert color="info" %}}
+By default, all developers in your organization can create node requests. To restrict this ability to Mendix Admins only, contact your Customer Success Manager or submit a support ticket.
+{{% /alert %}}
 
 ## Resizing an Existing Environment{#resize}
 
-If your environment is not the right size, for example it has too little database storage, you can request a resize from Mendix Support.
+If your environment needs resizing, for example, due to insufficient database storage, you can do so using one of the following methods:
 
-Fill in the required details on the [Resize Environment](https://resize.mendix.com/index.html) page.
+* **Self-service** – If your application's tenant is self-service enabled and you are the [Technical Contact](/developerportal/general/app-roles/#technical-contact), you can resize the environment by changing its plan. For details, refer to [Changing Your Plan in Mendix Cloud](/developerportal/deploy/change-plan/).
 
-Mendix Support will contact the [Technical Contact](/developerportal/general/app-roles/#technical-contact) for the app via a ticket in the [Mendix Support Portal](https://support.mendix.com) to discuss priority and timing.
+* **Request from Mendix Support** – Fill in the required details on the [Resize Environment](https://resize.mendix.com/index.html) page. Afterwards, Mendix Support will contact the application's [Technical Contact](/developerportal/general/app-roles/#technical-contact) through a ticket in the [Mendix Support Portal](https://support.mendix.com) to discuss the request's priority and timing.
 
 {{% alert color="warning" %}}
-Resizing operations will require your app to be restarted and it will be offline for a time while it is being resized. The downtime usually lasts for approximately 30-120 minutes.
+Resizing operations requires your app to be restarted and it will be offline for some time while it is being resized. The downtime usually lasts for approximately 30-120 minutes.
 {{% /alert %}}
 
 ## Offboarding an Environment{#offboard}
 
-If you no longer need an environment, you can offboard it. Alternatively, you can reuse it for another app — see [Linking Your App to a Licensed Node](/developerportal/deploy/licensing-apps/#licensed-node) in *Licensing Mendix Cloud Apps* for more information.
+If you no longer need an environment, you can offboard it. Alternatively, you can reuse it for another app. See [Linking Your App to a Licensed Node](/developerportal/deploy/licensing-apps/#licensed-node) in *Licensing Mendix Cloud Apps* for more information.
 
 You can offboard a single environment or an entire node (all three of the test, acceptance, and production environments for example) by filling in the required details on the [Offboard Environment](https://offboard.mendix.com/index.html) page. Only the Technical Contact of the application can request (and confirm) the offboarding. Once the offboarding is confirmed, the process will take place automatically. If you cannot use the Offboard Environment page for any reason, please raise a ticket with [Mendix Support](https://support.mendix.com).