Clarify ZDT setup and deployment instructions

ZDT doesn't need to be enabled by the TC. If a deployment is eligible for ZDT, the option becomes available. If it isn't eligible, the TC won't be able to select the option.

Author: feddovanede

content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md

@@ -24,17 +24,17 @@ To leverage the benefits of zero-downtime deployment, your Mendix application an
 * **Deployment platform** – Must be deployed on Mendix Cloud(Kubernetes).
 
 {{% alert color="info" %}}
-No special setup is required to enable ZDT. When your application and deployment meet these prerequisites, ZDT is automatically applied for eligible changes and can be controlled directly by Technical Contacts through the [Environment Settings](/developerportal/deploy/environments/#environment-settings).
+No special setup is required to enable ZDT. When your application and deployment meet these prerequisites, ZDT is automatically available for eligible changes.
 {{% /alert %}}
 
 ## How Zero-Downtime Deployment Works
 
 <!-- Diagram provided by the deployment team. Contact the team for updates or questions  -->
 {{< figure src="/attachments/deployment/mendix-cloud-deploy/zero-downtime/zdt-process-success-flow.png" alt="Sequence diagram illustrating the Zero-Downtime Deployment process, showing the Technical Contact initiating deployment, Mendix Cloud starting a new app version in the background while the current version serves users, the new version preparing configuration and reporting ready, Mendix Cloud gracefully stopping the old version, and finally directing traffic to the new version without user interruption." >}}
 
-When an eligible configuration change is deployed with ZDT enabled, Mendix Cloud orchestrates the following steps:
+When an eligible configuration change is deployed with ZDT, Mendix Cloud orchestrates the following steps:
 
-1. **Initiate deployment** – The Technical Contact triggers deployment with **Deploy without Downtime** enabled in Mendix Cloud.
+1. **Initiate deployment** – The Technical Contact triggers deployment with **Deploy without Downtime** in Mendix Cloud.
 2. **Current version active** – The existing application version continues to serve all user traffic without interruption.
 3. **New version spin-up** – A new instance of your application starts, adding the updated configuration, in the background. This new version prepares its configuration.
 4. **Health check & readiness** – Once the new instance is fully operational and passes all internal health checks, it reports its readiness to Mendix Cloud.
@@ -46,10 +46,10 @@ When an eligible configuration change is deployed with ZDT enabled, Mendix Cloud
 
 By default, this option is off. In this state, your app will use the standard restart process during deployment. This default setting ensures stability and compatibility with existing application behavior.
 
-Technical Contacts can decide whether to attempt a zero-downtime deployment by selecting the **Deploy without downtime** option on the **Other Options** tab when [deploying a package](/developerportal/deploy/environments/#deploy-wizard). If you enable this option, Mendix Cloud will attempt a zero-downtime deployment, if your environment meets eligibility criteria.
+Technical Contacts can decide whether to attempt a zero-downtime deployment by selecting the **Deploy without downtime** option on the **Other Options** tab when [deploying a package](/developerportal/deploy/environments/#deploy-wizard). If you select this option, Mendix Cloud will attempt a zero-downtime deployment, if your environment meets eligibility criteria.
 
 {{% alert color="info" %}}
-When a Technical Contact enables ZDT, the Cloud Portal displays a reminder to review any custom **before-shutdown** or **after-startup** microflows. This is crucial to ensure these microflows won’t cause conflicts during periods when two versions of your application might be running concurrently.
+When a Technical Contact selects ZDT, the Cloud Portal displays a reminder to review any custom **before-shutdown** or **after-startup** microflows. This is crucial to ensure these microflows won’t cause conflicts during periods when two versions of your application might be running concurrently.
 {{% /alert %}}
 
 ### When ZDT Applies {#zdt-application}