mendix · github-actions · Mar 1, 2026
diff --git a/content/en/docs/control-center/security/certificate-management.md b/content/en/docs/control-center/security/certificate-management.md
@@ -63,4 +63,4 @@ For detailed information about how Mendix Admins can use the **Certificate Manag
 
 * [Certificates](/developerportal/deploy/certificates/)
 * [Application-Level Certificates](/developerportal/deploy/application-level-certificates/)
-* [Custom Domains](/developerportal/deploy/custom-domains/)
+* [Custom Domains](/developerportal/deploy/custom-domains/)
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md b/content/en/docs/deployment/mendix-cloud-deploy/backups/create-backup.md
@@ -34,7 +34,6 @@ To create a backup archive of a licensed app, follow these steps:
 
    {{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/create-backup/backup-rds-window-failure.png"  >}}
 
-
 Once you have created a backup archive, you can download it by clicking **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) then selecting **Download**. For more information, see [Downloading a Backup](/developerportal/operate/download-backup/).
 
 {{% alert color="info" %}}

diff --git a/...ent/en/docs/deployment/mendix-cloud-deploy/certificates/central-certificates.md b/...ent/en/docs/deployment/mendix-cloud-deploy/certificates/central-certificates.md
@@ -117,4 +117,4 @@ Every hostname covered by the existing certificate must be included in the Subje
 
 * [Certificates](/developerportal/deploy/certificates/)
 * [Certificate Management](/control-center/certificate-management/)
-* [Custom Domains](/developerportal/deploy/custom-domains/)
+* [Custom Domains](/developerportal/deploy/custom-domains/)
diff --git a/...en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md b/...en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/dynatrace-metrics.md
@@ -39,7 +39,7 @@ To start sending your Mendix app's metrics to Dynatrace, you need to set some en
     | Variable                 | Required? | Description                                                                                                            | Details                                                                                                                                                                                                                                                                                                                                           |
     |--------------------------|-----------|------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
     | `DT_SAAS_URL`            | Yes       | The URL of Dynatrace environment                                                                                       | The format when using the Dynatrace SaaS environment is similar to `https://<your-environment-id>.live.dynatrace.com`. If you are using a Dynatrace managed environment, just provide the full URL of the Dynatrace domain, like `https://<your-dynatrace-domain>`.                                                                               |
-    | `DT_TENANT`              | Yes       | The Dynatrace Environment ID                                                                                           | For more information, see the [Environment ID](https://docs.dynatrace.com/docs/discover-dynatrace/get-started/monitoring-environment#environment-id) section of _Dynatrace_.                                                                                                                                                                                 |
+    | `DT_TENANT`              | Yes       | The Dynatrace Environment ID                                                                                           | For more information, see the [Environment ID](https://docs.dynatrace.com/docs/discover-dynatrace/get-started/monitoring-environment#environment-id) section of *Dynatrace*.                                                                                                                                                                                 |
     | `DT_PAAS_TOKEN`          | Yes       | The access token for integrating your Mendix app with Dynatrace                                                        | Create this on the Dynatrace environment. For more information, see [Generate an Access Token](https://www.dynatrace.com/support/help/get-started/access-tokens#create-api-token). The token must include the `PaaS integration - Installer download` and `Ingest metrics` scopes. For logging integration, `Ingest logs` scope is also required. |
     | `DT_ENABLE_LOGS`         | No        | Set this to `true` to enable logging                                                                                   | Only supported for Dynatrace SaaS. `Ingest logs` scope is required to be included in the access token.                                                                                                                                                                                                                                            |
     | `DT_IS_MANAGED`          | No        | Set this to `true` if you are using Dynatrace Managed. The default is assumed to be Dynatrace SaaS and set to `false`. | This variable is only needed for custom application metrics ingestion.                                                                                                                                                                                                                                                                            |

diff --git a/content/en/docs/deployment/mx-azure/mx-azure-backups.md b/content/en/docs/deployment/mx-azure/mx-azure-backups.md
@@ -150,4 +150,3 @@ As a workaround, you can restore a backup across clusters by performing the foll
 1. Download the backup snapshot from your source environment to your local machine.
 2. Upload the downloaded backup snapshot from your local machine to the target environment.
 3. Begin the restore process within the target environment using the newly uploaded backup snapshot.
-
diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md
@@ -1369,7 +1369,7 @@ You can invite additional members to the namespace, and configure their role dep
 
 {{% alert color="info" %}}The **Automatically accept invites** option is applicable only when the invited users have the same email domain as yours.{{% /alert %}}
 
-5. Give them the rights they need. This can be:
+1. Give them the rights they need. This can be:
 
     1. **Developer** – a standard set of rights needed by a developer, these are listed on the screen
     2. **Administrator** – a standard set of rights needed by an administrator, these are listed on the screen
@@ -1384,11 +1384,11 @@ If an application is in the Stopped state, the scaling does not come into effect
 Along with this, we have also decoupled the permission for modifying the MxAdmin password and managing environments.
 {{% /alert %}}
 
-6. Click **Send Invite** to send an invite to this person.
+1. Click **Send Invite** to send an invite to this person.
 
     {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/AutoAcceptInvite.png" class="no-border" >}}
 
-7. If you have not enabled the **Automatically accept invites** option, the user will receive an email and will be required to follow a link to confirm that they want to join this namespace. They will need to be logged in to Mendix when they follow the confirmation link.
+2. If you have not enabled the **Automatically accept invites** option, the user will receive an email and will be required to follow a link to confirm that they want to join this namespace. They will need to be logged in to Mendix when they follow the confirmation link.
 
 ##### Editing and Removing Members
 

diff --git a/...t/en/docs/marketplace/platform-supported-content/modules/data-widgets/_index.md b/...t/en/docs/marketplace/platform-supported-content/modules/data-widgets/_index.md
@@ -11,18 +11,18 @@ description: "Describes the configuration and usage of the Data Widgets module,
 
 This module contains the following widgets:
 
-- [Data Grid 2](/appstore/modules/data-grid-2/)
-- [Data Grid 2 Properties](/appstore/modules/data-grid-2-properties/)
-- [Drop-Down Sort](/appstore/modules/gallery/#dropdown)
-- [Filters](/appstore/modules/data-grid-2/#filters)
-- [Gallery](/appstore/modules/gallery/)
-- [Selection helper](/appstore/modules/selection-helper/)
-- [Tree node](/appstore/modules/tree-node/)
+* [Data Grid 2](/appstore/modules/data-grid-2/)
+* [Data Grid 2 Properties](/appstore/modules/data-grid-2-properties/)
+* [Drop-Down Sort](/appstore/modules/gallery/#dropdown)
+* [Filters](/appstore/modules/data-grid-2/#filters)
+* [Gallery](/appstore/modules/gallery/)
+* [Selection helper](/appstore/modules/selection-helper/)
+* [Tree node](/appstore/modules/tree-node/)
 
 ## Migration
 
 If you were previously using the Data Grid 2 module, you must follow these steps before updating it to the new [Data Widgets](https://marketplace.mendix.com/link/component/116540) module:
 
-1. Rename the current **DataGrid** module (under **Marketplace** modules) to _DataWidgets_ in Studio Pro.
+1. Rename the current **DataGrid** module (under **Marketplace** modules) to *DataWidgets* in Studio Pro.
 1. Open the Marketplace and search for **Data Widgets**.
 1. Download and replace the current (renamed) DataWidgets module.
diff --git a/...place/platform-supported-content/modules/data-widgets/data-grid-2-properties.md b/...place/platform-supported-content/modules/data-widgets/data-grid-2-properties.md
@@ -27,8 +27,8 @@ The time (in seconds) the grid waits between refreshing the data. Auto-refreshin
 
 This property controls row selection capabilities. Selection is turned off by default, but can be enabled by choosing ether **Single** or **Multi**:
 
-- The **Single** selection is selection type where only one row can be selected at the time
-- The **Multi** type support selecting several rows at the time
+* The **Single** selection is selection type where only one row can be selected at the time
+* The **Multi** type support selecting several rows at the time
 
 {{% alert color="info" %}}
 Data grid currently supports in-memory selection. When the **Keep Selection** property is disabled, selection is limited to visible rows and will be cleared when you change a data grid page or reload the browser window. When **Keep Selection** is enabled, selections persist across page navigation, data refreshes, filter operations, and sorting changes.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -34,7 +34,6 @@ To create a backup archive of a licensed app, follow these steps:

		{{< figure src="/attachments/deployment/mendix-cloud-deploy/backups/create-backup/backup-rds-window-failure.png" >}}


		Once you have created a backup archive, you can download it by clicking More Options ({{% icon name="three-dots-menu-horizontal" %}}) then selecting Download. For more information, see [Downloading a Backup](/developerportal/operate/download-backup/).

		{{% alert color="info" %}}
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -150,4 +150,3 @@ As a workaround, you can restore a backup across clusters by performing the foll
		1. Download the backup snapshot from your source environment to your local machine.
		2. Upload the downloaded backup snapshot from your local machine to the target environment.
		3. Begin the restore process within the target environment using the newly uploaded backup snapshot.