[Auto] Lint docs

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/csharp/_index.md

@@ -66,5 +66,3 @@ Review the following reference guides to explore additional Extensibility API to
 * [Extension Points](/apidocs-mxsdk/apidocs/csharp-extensibility-api-11/extension-points/)
 * [Extensibility Services](/apidocs-mxsdk/apidocs/csharp-extensibility-api-11/services/)
 * [Extensibility Web Views](/apidocs-mxsdk/apidocs/csharp-extensibility-api-11/web-views/)
-
-

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

@@ -35,7 +35,6 @@ It performs the following actions:
 
 Replace your `src/main/index.ts` file with the following:
 
-
 ```typescript
 import { IComponent, getStudioProApi } from "@mendix/extensions-api";
 

content/en/docs/control-center/company/mendix-admins.md

@@ -20,4 +20,4 @@ To remove an admin, hover over their name in the list, then click **Remove**.
 It is not possible to remove yourself as a Mendix Admin.
 {{% /alert %}}
 
-If the **Add Mendix Admin** button is not displayed, your company is using a user group in your IdP to assign Mendix Admins. For more information, refer to [IdP-managed Mendix Admins](/control-center/security-settings/#idp-managed-mendix-admins).
+If the **Add Mendix Admin** button is not displayed, your company is using a user group in your IdP to assign Mendix Admins. For more information, refer to [IdP-managed Mendix Admins](/control-center/security-settings/#idp-managed-mendix-admins).

content/en/docs/marketplace/genai/mendix-cloud-genai/mendix-cloud-grp.md

@@ -29,7 +29,6 @@ Mendix Cloud Model Resource Packs provide customers with a monthly quota of inpu
 
 The Mendix Cloud GenAI Resource Packs provide access to the following models:
 
-
 * Anthropic Claude 3.7 Sonnet (Cross-region inference profile)
 * Anthropic Claude 4 Sonnet (Cross-region inference profile)
 * Cohere Embed v3 (English and multilingual options)

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

@@ -96,4 +96,4 @@ There are several possible reasons why the client cannot connect to your server.
 * Concept description of [Model Context Protocol (MCP)](/appstore/modules/genai/mcp/)
 * 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)
+* The [MCP Java SDK GitHub Repository](https://github.com/modelcontextprotocol/java-sdk)

content/en/docs/marketplace/partner-solutions/dcm/_index.md

@@ -25,6 +25,7 @@ For more information, refer to [DCM for Mendix](https://www.casefabric.com/#mend
 
 CaseFabric’s DCM solution brings powerful case modeling capabilities to Studio Pro, using the [CMMN (Case Management Model and Notation)](https://www.omg.org/spec/CMMN/1.1) standard. This means you can build flexible, event-driven case models that work seamlessly with Mendix elements like your domain model, entities, pages, and microflows, making your app smarter and more responsive.
 The Mendix DCM module provides Studio Pro with a modeler specifically for case models. This lets you:
+
 * Map your domain model to the case file model.
 * Use existing entities directly within your case model.
 * Trigger your case model based on entity changes. This currently requires explicit modeling.

content/en/docs/marketplace/platform-supported-content/modules/siemens/capital-connector.md

@@ -74,4 +74,3 @@ Some operations take an object ID as parameter. Many Capital objects have a `Bas
 ## Resources
 
 For information about the Capital REST API, please refer to the REST API documentation of your Capital instance. This is available by accessing `{protocol}://{host}:{port}/restapidocs/`.
-

content/en/docs/marketplace/platform-supported-content/widgets/document-viewer.md

@@ -53,7 +53,6 @@ The **Advanced** tab allows you to configure settings for features beyond the no
     * If left empty, the document viewer widget will retrieve PDF.js from CDN `http://unpkg.com/pdfjs-dist@4.8.69/build/pdf.worker.min.mjs`.
     * Alternatively, users can grab `pdf.worker.mjs` from `{LOCAL DEV PROJECT FOLDER HERE}/deployment/web/widgets/com/mendix/shared/pdfjs/pdf.worker.mjs`, put it into their own `App Module -> Styling/web/js/pdf.worker.mjs` file, and then set `./js/pdf.worker.mjs` as the worker URL configuration. This is the recommended practice to support [CSP](/howto/security/csp/).
 
-
 ### Common Tab
 
 For more information, see [Common Section](/refguide/common-widget-properties/#common-properties) in *Properties Common in the Page Editor*.

content/en/docs/partners/altair/_index.md

@@ -11,4 +11,4 @@ description_list: true
 
 Mendix has a strategic alliance with Altair to make Mendix the fastest and easiest way to develop enterprise-grade applications that seamlessly integrate with Altair's powerful machine learning models capabilities.
 
-## Documents in this Category 
+## Documents in this Category 

content/en/docs/partners/altair/altair-rapidminer.md

@@ -315,4 +315,4 @@ After successfully implementing this integration:
 
 * [AI Hub Documentation](https://docs.rapidminer.com/latest/hub/)
 
-* [Altair RapidMiner Showcase App](https://marketplace.mendix.com/link/component/247304)
+* [Altair RapidMiner Showcase App](https://marketplace.mendix.com/link/component/247304)

content/en/docs/refguide/modeling/domain-model/oql/oql-statements.md

@@ -147,4 +147,4 @@ WHERE ID IN (
 * OQL statements can be used only with persistable entities.
 * Entity access rules are not applied to any OQL statements.
 * No event handlers will be executed.
-* Runtime and client state will not be updated with the changes.
+* Runtime and client state will not be updated with the changes.

content/en/docs/refguide/modeling/integration/rest-services/published-rest-services/published-rest-technical-details/open-api.md

@@ -50,4 +50,3 @@ Each operation generates an `Operation` object:
 | `parameters` | The path, query, and header parameters and their location and type information. |
 | `responses` | The OK response. If security is enabled, this is also the unauthorized response. |
 | `deprecated` | Set to true when the operation is marked as deprecated. |
-

content/en/docs/refguide10/modeling/integration/rest-services/published-rest-services/published-rest-technical-details/open-api.md

@@ -54,4 +54,3 @@ Each operation generates an `Operation` object:
 | `parameters` | The path, query, and header parameters and their location and type information. |
 | `responses` | The OK response. If security is enabled, this is also the unauthorized response. |
 | `deprecated` | Set to true when the operation is marked as deprecated. |
-

content/en/docs/releasenotes/deployment/mendix-azure.md

@@ -23,7 +23,7 @@ For information on the current status of Mendix deployment, see [Mendix Status](
 
 ### Known issues:
 
- * Currently, the **updated** or **created** tags in the **Edit** screen of the cluster are not attached to the cluster resources.
+* Currently, the **updated** or **created** tags in the **Edit** screen of the cluster are not attached to the cluster resources.
 
 ### Release date: September 11, 2025
 
@@ -33,9 +33,9 @@ For information on the current status of Mendix deployment, see [Mendix Status](
 
 ### Known issues:
 
- * Currently, the **updated** or **created** tags in the **Edit** screen of the cluster are not attached to the cluster resources.
- * Support ticket visibility is currently limited to tickets created by the individual user, rather than all tickets within their subscription.
- * Currently, it is not possible to create new environments in the Mendix on Azure cluster. We are working on releasing a fix for this issue soon.
+* Currently, the **updated** or **created** tags in the **Edit** screen of the cluster are not attached to the cluster resources.
+* Support ticket visibility is currently limited to tickets created by the individual user, rather than all tickets within their subscription.
+* Currently, it is not possible to create new environments in the Mendix on Azure cluster. We are working on releasing a fix for this issue soon.
 
 ### Release date: August 7, 2025
 

content/en/docs/releasenotes/studio-pro/10/10.24.md

@@ -18,19 +18,20 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for
 
 ### Improvements
 
-- When tracing is enabled, the maximum depth of microflow calls and the maximum number of loops that are reported can be configured using the `mendix.tracing.max.microflow.depth` and `mendix.tracing.max.loop.iteration` JVM properties. The default value of these properties are `10`. The microflow call depth is calculated per runtime node and does not take into account calls made into other Mendix runtimes through REST/WebServices calls.
+* When tracing is enabled, the maximum depth of microflow calls and the maximum number of loops that are reported can be configured using the `mendix.tracing.max.microflow.depth` and `mendix.tracing.max.loop.iteration` JVM properties. The default value of these properties are `10`. The microflow call depth is calculated per runtime node and does not take into account calls made into other Mendix runtimes through REST/WebServices calls.
 
 ### Fixes
 
-- **10.24.7 Fix** — We fixed a critical issue in 10.24.7 (only) where application startup would fail when upgrading a database originally created with a Mendix version before 10.17 and using foreign key constraints.
-- We fixed an issue where changing a MxAdmin user's name in Studio Pro does not result in changing MxAdmin user's name in database. (Ticket 255505) 
-- We fixed an issue where SVG images would load with incorrect dimensions. (Ticket 258901)
-- When using Oracle, we no longer use `dbms.lob_substr` in the generated SQL for enumeration attributes with values shorter than 2000 characters. (Ticket 259283)
-- We fixed an issue where database synchronization failed on SQL Server when a specialization of `System.User` was removed and there was still an `owner` or `changedBy` reference from an instance of `System.User` or a different specialization of it to an instance of the specialization being removed. 
+* **10.24.7 Fix** — We fixed a critical issue in 10.24.7 (only) where application startup would fail when upgrading a database originally created with a Mendix version before 10.17 and using foreign key constraints.
+* We fixed an issue where changing a MxAdmin user's name in Studio Pro does not result in changing MxAdmin user's name in database. (Ticket 255505) 
+* We fixed an issue where SVG images would load with incorrect dimensions. (Ticket 258901)
+* When using Oracle, we no longer use `dbms.lob_substr` in the generated SQL for enumeration attributes with values shorter than 2000 characters. (Ticket 259283)
+* We fixed an issue where database synchronization failed on SQL Server when a specialization of `System.User` was removed and there was still an `owner` or `changedBy` reference from an instance of `System.User` or a different specialization of it to an instance of the specialization being removed. 
+
 * We fixed an issue affecting file saving which made named files appear untitled. Previewed file names now work as intended.
-- We fixed an issue in the Create object activity which would fail when creating an instance of a remote non-persistable entity in a microflow.
-- We fixed an issue in consumed REST services where choosing an OpenAPI contract without any operations would result in an error.
-- We fixed an issue where a warning was logged on startup about an already registered Jetty gauge when multiple listening addresses are specified. The connection metrics for Jetty are added per listening address and they now contain a tag `port` with the port number and a tag `host` if a host is specified. This is applicable to the metrics `jetty.connections.bytes.in`, `jetty.connections.bytes.out`, `jetty.connections.current`, `jetty.connections.max`, `jetty.connections.messages.in`, `jetty.connections.messages.out`, and `jetty.connections.request`. Be aware of the fact that there are usually two listening addresses when you specify **Open to current machine** for Runtime port security, for example 127.0.0.1 and ::1.
+* We fixed an issue in the Create object activity which would fail when creating an instance of a remote non-persistable entity in a microflow.
+* We fixed an issue in consumed REST services where choosing an OpenAPI contract without any operations would result in an error.
+* We fixed an issue where a warning was logged on startup about an already registered Jetty gauge when multiple listening addresses are specified. The connection metrics for Jetty are added per listening address and they now contain a tag `port` with the port number and a tag `host` if a host is specified. This is applicable to the metrics `jetty.connections.bytes.in`, `jetty.connections.bytes.out`, `jetty.connections.current`, `jetty.connections.max`, `jetty.connections.messages.in`, `jetty.connections.messages.out`, and `jetty.connections.request`. Be aware of the fact that there are usually two listening addresses when you specify **Open to current machine** for Runtime port security, for example 127.0.0.1 and ::1.
 
 ## 10.24.7 {#10247}