[UIA-1274] Highlight private PDF service

Author: ozgeMendix

content/en/docs/marketplace/platform-supported-content/modules/document-generation.md

@@ -25,8 +25,9 @@ The [PDF Document Generation](https://marketplace.mendix.com/link/component/2115
     * [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/)
     * [Mendix Cloud Dedicated](/developerportal/deploy/mendix-cloud-deploy/)
     * [Mendix on Kubernetes Connected](/developerportal/deploy/private-cloud/)
+    * [Private PDF Document Generation Service](#run-private-service)
     * [On-Premises](/developerportal/deploy/on-premises-design/)
-    * A privately hosted Docker containerized PDF Document Generation service. It is available starting with module versions 1.11.0 for Studio Pro 9 and 2.1.0 for Studio Pro 10. For more information, refer to [Private PDF Document Generation Service](/appstore/services/private-document-generation-service/).
+
     {{% alert color="info" %}}We only support apps that allow bi-directional communication with the PDF Service in Mendix Cloud for all deployment types except for on-premises, and for the [Private PDF Document Generation Service](/appstore/services/private-document-generation-service/).{{% /alert %}}
 * The maximum file size is 25 MB per document. If your document exceeds this limit, the action will result in an exception. We recommend compressing high-resolution images to reduce their file size.
 * If your app is configured to [restrict access for incoming requests](/developerportal/deploy/access-restrictions/) using client certificates, our cloud service will not be able to reach your app, and the module will not work properly.
@@ -72,7 +73,8 @@ Follow the instructions in [How to Use Marketplace Content](/appstore/use-conten
         * [Mendix Cloud Dedicated](/developerportal/deploy/mendix-cloud-deploy/)
         * [Mendix on Kubernetes Connected](/developerportal/deploy/private-cloud/)
 
-    2. [Running On-Premises](#run-on-premises) using a local version of the PDF service. This option is available for apps that are deployed to the following environments:
+    2. [Running on self-hosted for airgapped and on-premises](#run-private-service-and-on-premises) using a local version of the PDF service. This option is available for apps that are deployed to the following environments:
+        * [Private PDF Document Generation Service](#run-private-service)
         * [Microsoft Windows](/developerportal/deploy/deploy-mendix-on-microsoft-windows/)
         * [Linux](/developerportal/deploy/linux/)
 
@@ -156,39 +158,47 @@ To allow the module to send and receive document generation requests on your Men
 
 If your app is configured to [restrict access for incoming requests](/developerportal/deploy/access-restrictions/) using IP restrictions, you must add the [outbound IP addresses of the DocGen service](/developerportal/deploy/mendix-ip-addresses/#global-platform-ips-outbound) to the list of allowed addresses.
 
-### Running On-Premises {#run-on-premises}
+### Running on self-hosted for airgapped and on-premises {#run-private-service-and-on-premises}
+
+#### Running Private PDF Document Generation Service {#run-private-service}
+
+When access to the public Mendix PDF generation service is restricted, particularly in isolated or air-gapped environments, Mendix offers a privately hosted, Docker containerized PDF Document Generation service as an alternative. 
+
+It is available starting with module versions 1.11.0 for Studio Pro 9 and 2.1.0 for Studio Pro 10. For more information, refer to [Private PDF Document Generation Service](/appstore/services/private-document-generation-service/).
+
+#### Running On-Premises {#run-on-premises}
 
 To configure the module to generate documents on your on-premises environments, you need to perform the following steps:
 
 1. Make sure that you have the prerequisite software installed.
 2. Configure the module to use the local service.
 3. Enable the DocGen request handler.
 
-#### Installing the Prerequisite Software {#install-prerequisites}
+##### Installing the Prerequisite Software {#install-prerequisites}
 
 You should pre-install and actively maintain the following software. Mendix does not provide support for the installation, configuration, and maintenance of these packages.
 
-##### Chromium
+###### Chromium
 
 You should have installed a stable release of the Chromium browser. The currently supported stable release is 112.0.5615.0 ([Windows](https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/1109252/). [Linux](https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/1109252/)).
 
 {{% alert color="info" %}}Even though we advise using Chromium, you can also use Google Chrome instead. The configuration remains the same.{{% /alert %}}
 
-##### Node.js
+###### Node.js
 
 You should have installed a stable release of [Node.js](https://nodejs.org/).  Mendix recommends installing the same version that is shipped with the Studio Pro version that is used to build the project. You can find this version by locating and executing the `node` executable within the `modeler/tools/node` folder of your Studio Pro installation.
 
 {{% alert color="info" %}}Make sure that the Mendix Runtime has the applicable permissions to run the *node* executable.{{% /alert %}}
 
-#### Configuring the Module to use the Local Service {#configure-local-service}
+##### Configuring the Module to use the Local Service {#configure-local-service}
 
 1. Set the **OverrideServiceType** constant to *Local* in the **_UseMe** > **Configuration** folder. This enforces the use of the local service instead of the cloud service.
 
 2. Configure the path to the *chrome* executable in the **CustomChromePath** constant in the **_UseMe** > **Configuration** folder.
 
 3. Configure the path to the *node* executable in the **CustomNodePath** constant in the **_UseMe** > **Configuration** folder. 
 
-#### Enabling the DocGen Request Handler {#setup-inbound-rules}
+##### Enabling the DocGen Request Handler {#setup-inbound-rules}
 
 In case you deploy on [Microsoft Windows](/developerportal/deploy/deploy-mendix-on-microsoft-windows/), you need to add the following rules when configuring the [reverse proxy inbound rules](/developerportal/deploy/deploy-mendix-on-microsoft-windows/#reverse-proxy-rules):