[Auto] Lint docs

content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/pipeline-api-v2.md

@@ -26,4 +26,4 @@ For information about Pipeline API version 1, see [Pipeline API - Version 1](/ap
 
 ## API Reference
 
-{{< swaggerui src="/openapi-spec/openapi-pipeline-v2.yaml"  >}}
+{{< swaggerui src="/openapi-spec/openapi-pipeline-v2.yaml"  >}}

content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api-v2.md

@@ -32,4 +32,4 @@ For information about Project API version 1, see [Project API - Version 1](/apid
 
 ## API Reference
 
-{{< swaggerui src="/openapi-spec/openapi-project-v2.yaml"  >}}
+{{< swaggerui src="/openapi-spec/openapi-project-v2.yaml"  >}}

content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api.md

@@ -31,4 +31,4 @@ For information about Project API version 2, see [Project API - Version 2](/apid
 
 ## API Reference
 
-{{< swaggerui src="/openapi-spec/openapi-project-v1.yaml"  >}}
+{{< swaggerui src="/openapi-spec/openapi-project-v1.yaml"  >}}

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/consistency-checks.md

@@ -279,7 +279,6 @@ export const component: IComponent = {
 };
 ```
 
-
 Replace your `src/model/PersonInfo.ts` file with the following:
 
 ```typescript {hl_lines=["6-10"]}
@@ -416,7 +415,6 @@ export const component: IComponent = {
 };
 ```
 
-
 Return `dependentElementIds` to tell Studio Pro which elements your document depends on. When those elements change, your checks rerun automatically.
 
 {{% alert color="info" %}}
@@ -487,7 +485,6 @@ async function checkDependencyWasChanged(dependencies: Dependency[], documents:
 
 By checking whether any of the changed documents from the event payload are included in your dependencies, you can trigger the consistency checks to run again by updating the content of your blob document using `studioPro.app.model.customBlobDocuments.updateDocumentContent`. This ensures your checks run again whenever one of your dependencies is modified in Studio Pro.
 
-
 ### Renamed Elements
 
 If one of your dependencies gets renamed, you may need to update the dependency names in your document. Studio Pro cannot automatically rename your dependencies; it can only notify you that the document matching the ID now has a new name. It is up to you to update your dependency's name.

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/permissions.md

@@ -90,6 +90,7 @@ export const component: IComponent = {
     }
 };
 ```
+
 The `permissionsChanged` event fires for all extensions whenever any permission is granted or revoked anywhere in the system, not just for your extension. This means multiple extensions may respond to the same event simultaneously.
 
 To check if a change affects your extension, compare the old granted state against the new one for each permission name your extension declared. Without this check, your extension fires a notification every time any permission changes, including changes unrelated to your extension.

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md

@@ -485,7 +485,7 @@ if (selection.type === "Single") {
 
 ## Exposed Modules
 
- ### Session {#session}
+### Session {#session}
 
 The Mendix Platform exposes a `mendix/session` module for inspecting the current user session. It is available in both web and native.
 

content/en/docs/catalog/_index.md

@@ -54,7 +54,6 @@ From the **Home** screen, you can do the following:
 
 The Catalog is also integrated in Mendix Studio Pro to find and connect to shared services in your apps. For further details on using Catalog in Studio Pro, see [Integration Pane](/refguide/integration-pane/) in the *Studio Pro Guide*.
 
-
 ## Information Available in the Catalog {#available-info}
 
 In the Catalog, all the information for registered assets is displayed in the [Catalog search details](/catalog/manage/search/#search-details) screen. This information comes from the metadata in the OData service contract, and also from additional metadata that is added when registered assets are curated. Registered assets can be curated by owners, [Curators](/catalog/manage/user-roles/#curator), and [Mendix Admins](/catalog/manage/user-roles/#admin).

content/en/docs/control-center/maia/_index.md

@@ -10,4 +10,4 @@ no_list: false
 
 The **Maia** section allows you to manage, control, and monitor Maia resources and behavior on Mendix Portal.
 
-## Documents in This Category
+## Documents in This Category

content/en/docs/control-center/security/policies.md

@@ -43,41 +43,41 @@ You can create a policy by defining your own details.
 
 2. On the **Policy Definition** tab, fill in the following details:
 
-* **Policy Name** – A relevant name for your policy, such as one indicating what the policy checks.
-* **Description** – A description of the goal of the policy, which covers why it needs to be adhered to, and how to fix its violations.
-* **Policy Conditions** – Define the conditions under which the policy is considered violated. These are the available conditions and their values:
+    * **Policy Name** – A relevant name for your policy, such as one indicating what the policy checks.
+    * **Description** – A description of the goal of the policy, which covers why it needs to be adhered to, and how to fix its violations.
+    * **Policy Conditions** – Define the conditions under which the policy is considered violated. These are the available conditions and their values:
 
-    * **Any finding severity is** – Choose which severity level violates the policy. You can select one or more of the following values:
+        * **Any finding severity is** – Choose which severity level violates the policy. You can select one or more of the following values:
 
-        * **LOW**
-        * **MEDIUM**
-        * **HIGH**
-        * **CRITICAL**
+            * **LOW**
+            * **MEDIUM**
+            * **HIGH**
+            * **CRITICAL**
 
-        For example, if you select **CRITICAL**, apps with critical findings violate this policy.
+            For example, if you select **CRITICAL**, apps with critical findings violate this policy.
 
-    * **Mendix runtime version is lower than** – Indicate which Mendix version is the minimum that your apps must use.
+        * **Mendix runtime version is lower than** – Indicate which Mendix version is the minimum that your apps must use.
 
-    * **Marketplace component license is not** – Select the licenses that are acceptable. If a Marketplace component has a license which is not one of the ones you select here, the policy is violated. These are the possible values:
+        * **Marketplace component license is not** – Select the licenses that are acceptable. If a Marketplace component has a license which is not one of the ones you select here, the policy is violated. These are the possible values:
 
-        * MIT
-        * BSD_2_0
-        * APACHE_V2
-        * APACHE_1_0
-        * MENDIX_EULA
-        * PARTNER_LICENSES
-        * CREATIVE_COMMONS_CC0
-        * GNU_GENERAL_PUBLIC_LICENSE_V3
-        * MENDIX_MARKETPLACE_CONTENT_TERMS
+            * MIT
+            * BSD_2_0
+            * APACHE_V2
+            * APACHE_1_0
+            * MENDIX_EULA
+            * PARTNER_LICENSES
+            * CREATIVE_COMMONS_CC0
+            * GNU_GENERAL_PUBLIC_LICENSE_V3
+            * MENDIX_MARKETPLACE_CONTENT_TERMS
 
-    * **Marketplace component support is not** – Select the support types that are acceptable. If a Marketplace component has a support type which is not one of the ones you select here, the policy is violated. These are the possible values:
+        * **Marketplace component support is not** – Select the support types that are acceptable. If a Marketplace component has a support type which is not one of the ones you select here, the policy is violated. These are the possible values:
 
-        * PARTNER
-        * SIEMENS
-        * PLATFORM
-        * COMMUNITY
+            * PARTNER
+            * SIEMENS
+            * PLATFORM
+            * COMMUNITY
 
-* **Checkpoints & Action(s)** – Select the trigger which causes the policy to be checked, and the action that is taken if the policy is violated. Currently, policy violations are checked at the time of package creation, and violations generate warnings.
+    * **Checkpoints & Action(s)** – Select the trigger which causes the policy to be checked, and the action that is taken if the policy is violated. Currently, policy violations are checked at the time of package creation, and violations generate warnings.
 
 3. On the **Policy Scope** tab, select whether you want the policy to apply to all licensed apps, or only to specific apps in your environment.
 

content/en/docs/deployment/general/subscription-management/user-metering/implementing-user-metering.md

@@ -119,7 +119,6 @@ The improved user metering capabilities are introduced in Mendix 11. These capab
 | Multi-app user identification | `system.user.name` | `system.user.name` or `NamedUserIdentifier` in User Commons v2.2.0 and above |
 | SCIM-based user deactivation | SCIM v3.0.0 and above | SCIM v4.0.0 and above |
 
-
 ## Domain Model Entities {#domain-model-entities}
 
 This section explains the entities and their attributes in your application domain model that are relevant for user metering.

content/en/docs/deployment/mendix-cloud-deploy/deploy-apis-with-ai-agents.md

@@ -45,7 +45,6 @@ Replace the following placeholders with your credentials:
 * `{Mendix-Username}` – the login name of the user making the request, with the required privileges in the Mendix Platform
 * `{Mendix-ApiKey}` – the API key associated with that user
 
-
 To verify the connection, run the following command:
 
 ```bash
@@ -161,7 +160,6 @@ Two authentication methods are used depending on the API:
 Include all three headers in your connection configuration to ensure all tools work correctly.
 {{% /alert %}}
 
-
 ## Client Compatibility {#compatibility}
 
 The Mendix MCP integration works with any MCP-compatible client that supports HTTP transport (streamable HTTP) and custom headers for authentication.

content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/opentelemetry.md

@@ -150,7 +150,7 @@ These variables control the resource attributes attached to all telemetry. They
 | `MX_OTEL_SERVICE_NAME` | App subdomain | Service name (`service.name` attribute). Defaults to the subdomain of the app's first route (for example, `my-app` from `my-app.mendixcloud.com`). Set this variable to override it. |
 | `MX_OTEL_SERVICE_VERSION` | Model version | Service version (`service.version` attribute). Defaults to the Mendix model version. Falls back to the `version` application tag if set, otherwise `unversioned`. |
 | `MX_OTEL_DEPLOYMENT_ENV` | `env` tag or `none` | Deployment environment (`deployment.environment.name` attribute). Defaults to the `env` application tag if set, otherwise `none`. |
-| `MX_OTEL_RESOURCE_ATTRIBUTES` | _(from app tags)_ | Additional resource attributes as comma-separated `key=value` pairs. Automatically populated from the application tags set in the Developer Portal. Can be set directly to override the tag-derived value. |
+| `MX_OTEL_RESOURCE_ATTRIBUTES` | *(from app tags)* | Additional resource attributes as comma-separated `key=value` pairs. Automatically populated from the application tags set in the Developer Portal. Can be set directly to override the tag-derived value. |
 
 ### OpenTelemetry Issues
 

content/en/docs/deployment/on-premises-design/linux/linux.md

@@ -14,7 +14,6 @@ With the release of [Mendix Portable Runtime](https://docs.mendix.com/developerp
 For more information, see [Mendix Portable Runtime: Deployment, Simplified](https://www.mendix.com/blog/mendix-portable-runtime/).
 {{% /alert %}}
 
-
 ## Introduction
 
 Mendix can be installed on premises on systems running Linux. The installation consists of the following:

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

@@ -71,4 +71,4 @@ Dynatrace offers the following features:
 
 ### Installing and Monitoring Docker Containers with Dynatrace
 
-To integrate Dynatrace with your Docker environment for comprehensive monitoring, see [Set up Dynatrace on Docker](https://docs.dynatrace.com/docs/ingest-from/setup-on-container-platforms/docker) in Dynatrace documentation.
+To integrate Dynatrace with your Docker environment for comprehensive monitoring, see [Set up Dynatrace on Docker](https://docs.dynatrace.com/docs/ingest-from/setup-on-container-platforms/docker) in Dynatrace documentation.

content/en/docs/deployment/pad/pad-troubleshooting.md

@@ -94,4 +94,4 @@ The value of `M2EE_ADMIN_PASS` is not set.
 
 ### Solution
 
-Set the value of `M2EE_ADMIN _PASS`. For more information, see [Mendix Portable Runtime: Deploying Locally](/developerportal/deploy/portable-app-distribution-deploy/#deploy-local).
+Set the value of `M2EE_ADMIN _PASS`. For more information, see [Mendix Portable Runtime: Deploying Locally](/developerportal/deploy/portable-app-distribution-deploy/#deploy-local).

content/en/docs/deployment/private-cloud/private-cloud-operator.md

@@ -240,8 +240,8 @@ You must make the following changes:
 * **environmentVariables** - Set the environment variables for the Mendix app container, and JVM arguments through the `JAVA_TOOL_OPTIONS` environment variable.
 * **clientCertificates** - Specify client certificates to be used for TLS calls to Web Services and REST services.
 
-   * When **key** and **password** are specified, will use the client TLS certificate specified directly in the **MendixApp** CR.
-   * When **certificateSecret** is specified without a **key** and **password**, will load a client TLS certificate from the specified Kubernetes Secret. This feature requires Mendix Operator 2.27 or newer.
+    * When **key** and **password** are specified, will use the client TLS certificate specified directly in the **MendixApp** CR.
+    * When **certificateSecret** is specified without a **key** and **password**, will load a client TLS certificate from the specified Kubernetes Secret. This feature requires Mendix Operator 2.27 or newer.
 
 * **runtimeMetricsConfiguration** - Specify how metrics should be collected. Any non-empty values override the [default values](/developerportal/deploy/private-cloud-cluster/#customize-runtime-metrics) from `OperatorConfiguration`. Refer to [Monitoring Environments in Mendix on Kubernetes](/developerportal/deploy/private-cloud-monitor/) for details on how to monitor your environment.
 * **runtimeLeaderSelection** - Specify how the leader replica should be selected. The following options are available:
@@ -343,7 +343,6 @@ If you read the secret and see `data` instead of `stringData`, the values of the
 This ensures that a binary PKCS12 file can be safely stored and edited as a plaintext string.
 {{% /alert %}}
 
-
 ```yaml
 apiVersion: privatecloud.mendix.com/v1alpha1
 kind: MendixApp

content/en/docs/developerportal/maia-plan/maia-plan-mcp/_index.md

@@ -128,6 +128,7 @@ To configure Visual Studio Code Copilot to connect to the Maia Plan MCP server,
       }
     }
     ```
+
 3. In Visual Studio Code, follow these steps:
 
     1. Open **Command Palette**.

content/en/docs/genai/_index.md

@@ -106,4 +106,4 @@ In addition to the models listed above, you can also connect to other models by
 
 If you have any questions, encounter errors, or want to share feedback, reach out in the [#genai-connectors](https://mendixcommunity.slack.com/archives/C07P8NRBLN9) channel in the Mendix Community Slack workspace. To sign up for this workspace, use [this invitation link](https://mendixcommunity.slack.com/join/shared_invite/zt-270ys3pwi-kgWhJUwWrKMEMuQln4bqrQ#/shared-invite/email).
 
-## Documents in This Category
+## Documents in This Category

content/en/docs/genai/v1/_index.md

@@ -82,4 +82,4 @@ Older versions of some modules and the GenAI Showcase App are available in Studi
 
 * [Release and Migration Guide for GenAI Modules](/agents/agents-kit-1/reference-guide/migration-guide/)
 
-    Describes the combined releases of various GenAI-related modules and their inter-module dependencies. Also includes migration steps and notices about deprecations and removals.
+    Describes the combined releases of various GenAI-related modules and their inter-module dependencies. Also includes migration steps and notices about deprecations and removals.

content/en/docs/genai/v1/how-to/creating-agents/shared-setup.md

@@ -73,6 +73,7 @@ The agent interacts with data from a knowledge base and the Mendix app. To make
 Each of these steps is described in the following sections.
 
 To define the agent and generate responses, the steps differ based on your chosen approach and are covered in separate documents.
+
 ### Ingesting Data Into Knowledge Base {#ingest-knowledge-base}
 
 Ingest Mendix ticket data into the knowledge base. For a detailed guide, see [Grounding Your LLM in Data](/agents/agents-kit-1/how-to/howto-groundllm/#demodata). The following steps explain the process at a higher level by modifying logic imported from the [GenAI Showcase App](https://marketplace.mendix.com/link/component/220475). You can find the sample data used in this document in the GenAI Showcase App or use your own data.

content/en/docs/genai/v1/reference-guide/mcp-modules/mcp-client.md

@@ -100,4 +100,3 @@ There are several possible reasons why the client cannot connect to your server.
 * The [GenAI Showcase App](https://marketplace.mendix.com/link/component/220475) provides an example on how to expose microflows as tools via the MCP Server module. 
 * The official [MCP docs](https://modelcontextprotocol.io/introduction)
 * The [MCP Java SDK GitHub Repository](https://github.com/modelcontextprotocol/java-sdk)
-

content/en/docs/genai/v2/how-to/creating-agents/shared-setup.md

@@ -70,6 +70,7 @@ The agent interacts with data from a knowledge base and the Mendix app. To make
 Each of these steps is described in the following sections.
 
 To define the agent and generate responses, the steps differ based on your chosen approach and are covered in separate documents.
+
 ### Ingesting Data Into Knowledge Base {#ingest-knowledge-base}
 
 Ingest Mendix ticket data into the knowledge base. For a detailed guide, see [Grounding Your LLM in Data](/agents/agents-kit-2/how-to/howto-groundllm/#demodata). The following steps explain the process at a higher level by modifying logic imported from the [GenAI Showcase App](https://marketplace.mendix.com/link/component/220475). You can find the sample data used in this document in the GenAI Showcase App or use your own data.

content/en/docs/genai/v2/reference-guide/mcp-modules/mcp-client.md

@@ -98,4 +98,3 @@ There are several possible reasons why the client cannot connect to your server.
 * The [GenAI Showcase App](https://marketplace.mendix.com/link/component/220475) provides an example on how to expose microflows as tools via the MCP Server module. 
 * The official [MCP docs](https://modelcontextprotocol.io/introduction)
 * The [MCP Java SDK GitHub Repository](https://github.com/modelcontextprotocol/java-sdk)
-

content/en/docs/genai/v2/release-guide.md

@@ -63,4 +63,4 @@ Agents Kit 2 modules are compatible with [Atlas UI 4](/refguide/frontend/atlas4-
 
 * Feature parity between Agent Builder in Runtime and Agent Editor in Studio Pro is still in progress, particularly for external provider support and human-in-the-loop capabilities.
 * The [RFP Assistant Starter App](https://marketplace.mendix.com/link/component/235917) now supports Studio Pro agents and requires [Mendix Cloud GenAI](/agents/mx-cloud-genai/).
-* The latest version of the [AI Bot Starter App](https://marketplace.mendix.com/link/component/227926) remains available in Studio Pro 10.24 and has not been upgraded for Agents Kit 2, as its use case does not rely on agents.
+* The latest version of the [AI Bot Starter App](https://marketplace.mendix.com/link/component/227926) remains available in Studio Pro 10.24 and has not been upgraded for Agents Kit 2, as its use case does not rely on agents.

content/en/docs/marketplace/manage-content/_index.md

@@ -11,4 +11,4 @@ description_list: true
 
 This section provides information about creating content, uploading it to Mendix Marketplace, and deprecating it if necessary.
 
-## Documents in This Category
+## Documents in This Category

content/en/docs/marketplace/platform-supported-content/widgets/fieldset.md

@@ -17,4 +17,3 @@ The [Fieldset](https://marketplace.mendix.com/link/component/113922/Mendix/Field
 ## Limitations
 
 * This widget should only be used to group widgets belonging to a form
-