trying to fix the build errors again

Author: katarzyna-koltun-mx

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

@@ -17,7 +17,7 @@ Mendix offers two options for Docker deployments: Portable App Distribution or t
 
 ### Portable App Distribution
 
-[Portable App Distribution](/developerportal/deploy/portable-app-distribution/) allows users to generate their portable app with a single MxBuild command. It requires fewer manual steps than the Docker Buildpack, simpler environment configuration, and no `rootfs` preparation. Running Portable App Distribution can take as little as 3-6 minutes (the time may vary based on the application's size and complexity).
+[Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/) allows users to generate their portable app with a single MxBuild command. It requires fewer manual steps than the Docker Buildpack, simpler environment configuration, and no `rootfs` preparation. Running Portable App Distribution can take as little as 3-6 minutes (the time may vary based on the application's size and complexity).
 
 ### Docker Buildpack
 

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

@@ -7,7 +7,7 @@ description: "Describes how to deploy using a Docker image by using Portable App
 
 ## Introduction
 
-This guide provides a walkthrough for deploying your Mendix application using [Portable App Distribution](/developerportal/deploy/portable-app-distribution/) with Docker. This approach is particularly useful for containerized environments, and can significantly ease your CI/CD setup.
+This guide provides a walkthrough for deploying your Mendix application using [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/) with Docker. This approach is particularly useful for containerized environments, and can significantly ease your CI/CD setup.
 
 {{% alert color="info" %}}
 This document is not an official Mendix implementation, or a substitute for recommended production deployment strategies. For more features, such as app management or governance, we suggest using [Mendix on Kubernetes](/developerportal/deploy/private-cloud/) or [Mendix on Azure](/developerportal/deploy/mendix-on-azure/), which offer a structured, tested experience with cloud infrastructure. 
@@ -29,7 +29,7 @@ The Portable App Distribution feature in Mendix Studio Pro provides you with the
 
 To deploy your app to Docker, perform the following steps:
 
-1. Generate the application files. For more information, see [Portable App Distribution](/developerportal/deploy/portable-app-distribution/).
+1. Generate the application files. For more information, see [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/).
 
     These files are the core of your Mendix application and are ready to be included in a Docker image.
 

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

@@ -5,7 +5,6 @@ weight: 15
 description: "Describes the Portable App Distribution deployment method for Mendix apps."
 no_list: false 
 description_list: true
-beta: true
 ---
 
 ## Introduction

content/en/docs/refguide/general/mxbuild.md

@@ -68,7 +68,7 @@ Command-line options are described in the table below:
 | `-h`, `--help` | Prints a short description of the MxBuild and a list of all available options. |
 | `--java-home=DIRECTORY` | (Required). The directory in which the JDK is installed.<br/>For example, `--java-home=/usr/lib/jvm/java-8-oracle`.<br/>For Windows, *DIRECTORY* should be enclosed in double-quotes `"`. |
 | `--java-exe-path=FILENAME` | (Required). The full path to the Java executable.<br/>For example, `--java-exe-path=/usr/lib/jvm/java-8-oracle/bin/java`.<br/>For Windows, *DIRECTORY* should be enclosed in double-quotes `"` and must contain the complete file name `...\java.exe`. |
-| <code>––target=[package&#124;deploy]</code> | `package`: default if option is omitted; creates a deployment package (*.mda file*).<br/>`portable-app-package`: creates a [Portable App Distribution](/developerportal/deploy/portable-app-distribution/) package<br/>`deploy`: deploys the app without making a deployment package.<br/>`sbom`: generates a [Software Bill of Materials](/refguide/sbom-generation/) (SBOM) in the CycloneDX format for the app. |
+| <code>––target=[package&#124;deploy]</code> | `package`: default if option is omitted; creates a deployment package (*.mda file*).<br/>`portable-app-package`: creates a [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/) package<br/>`deploy`: deploys the app without making a deployment package.<br/>`sbom`: generates a [Software Bill of Materials](/refguide/sbom-generation/) (SBOM) in the CycloneDX format for the app. |
 | `--loose-version-check` | Creates a deployment package from an app which was created with a lower Mendix version.<br/>The app will be upgraded to the MxBuild version before the deployment package is created.<br /> Any changes included as a result of this upgrade will not be stored in your app. |
 | `--write-errors=FILENAME` | Writes all errors, warnings, and deprecations encountered during deployment of the app to the specified file in JSON format.<br />This file is only written when the app contains errors.<br />If the file already exists, it will be overwritten without a warning.<br />For a description of the format of this file, see the [App Errors](#app-errors) section below. |
 | `--generate-sbom` | Generates a Software Bill of Materials (SBOM) file as a part of the `package` and `deployment` targets. The SBOM will be included in the deployment package if this option is used and is saved under its default location: `deployment\sbom.json` |