[Auto] Lint docs

content/en/docs/control-center/security/software-composition/components.md

@@ -109,4 +109,4 @@ The component usage list contains the following information:
 * **Runtime** — The runtime version to which the component is compatible.
 * **Target Cloud** — The type of cloud where the deployment package is deployed.
 * **Technical Contact** — The Technical Contact of the app.
-* Column customization ({{% icon name="view" %}}) — You can customize the columns in the list by clicking the {{% icon name="view" %}} icon and selecting or deselecting options.
+* Column customization ({{% icon name="view" %}}) — You can customize the columns in the list by clicking the {{% icon name="view" %}} icon and selecting or deselecting options.

content/en/docs/deployment/mendix-cloud-deploy/deploying-to-mendix-cloud.md

@@ -116,7 +116,6 @@ With a Free App, you can deploy your app to Mendix Cloud from Studio Pro by usin
 
 * Alternatively, in the top bar of Studio Pro, click **Publish**.
 
-
 ## Deployment Status and Troubleshooting
 
 The [Mendix Platform Status page](https://status.mendix.com/) shows the current status of Mendix services. If you have issues with deployment, you can check the status page to see if deployment is operational (under **Mendix Services**) or if there are other Mendix issues that may be affecting your deployment. For more information, see [Mendix Cloud Status](/developerportal/deploy/mendix-cloud-status/).

content/en/docs/deployment/mx-azure/mx-azure-installation.md

@@ -254,4 +254,3 @@ Once the cluster is successfully created and initialized in the Mendix on the Az
 After being added, the new cluster manager has the ability to view and manage the cluster within the Mendix on the Azure portal. They can also access and update the support ticket associated with the cluster in the Mendix on Azure portal. However, the newly added cluster manager does not have access to the Zendesk ticket linked to the cluster's support ticket.  
 
 If a cluster manager is deleted, they can no longer view the associated cluster or its support ticket in the Mendix on Azure portal.
-

content/en/docs/developerportal/digital-execution/implement-mendix/_index.md

@@ -26,4 +26,4 @@ After completing the steps outlined in this guide, you will be able to:
 * Prepare your first project, and onboard your first project team. 
 * Launch your first app.
 
-## Documents in This Category
+## Documents in This Category

content/en/docs/developerportal/digital-execution/implement-mendix/mendix-ecosystem.md

@@ -166,4 +166,4 @@ It is important to know what’s happening with the Mendix Platform to be sure t
 
 * [Join the Mendix Community](https://community.mendix.com/p/questions) to connect with over 290,000 community members. The Mendix Community is a great place for developers to ask questions and post ideas for our product managers. 
 
-* [Subscribe to our blog](https://www.mendix.com/blog/#blog__subscribe) and deep dive into our diverse library of articles and blog posts, where we discuss everything from Mendix best practices to industry trends.
+* [Subscribe to our blog](https://www.mendix.com/blog/#blog__subscribe) and deep dive into our diverse library of articles and blog posts, where we discuss everything from Mendix best practices to industry trends.

content/en/docs/developerportal/digital-execution/implement-mendix/questions-feedback.md

@@ -23,4 +23,4 @@ If you need help with technical matters:
   Be sure to first check whether someone has already asked the question you're wondering about. If not, feel free to post it, and our community will help you out. Doing so will gain you points.
 * Submit a support ticket. If something really appears to be broken from a technical point of view, such as not being able to visit or edit your app anymore, contact our [Support Team](https://support.mendix.com/hc/en-us).
 
-If you have feedback or any improvement suggestions, use the **Feedback** option at the bottom of this page.
+If you have feedback or any improvement suggestions, use the **Feedback** option at the bottom of this page.

content/en/docs/marketplace/genai/concepts/_index.md

@@ -102,13 +102,10 @@ See [Function Calling](/appstore/modules/genai/function-calling/) for more infor
 
 This pattern is supported both by [OpenAI](https://platform.openai.com/docs/guides/function-calling) and [various models available on Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/conversation-inference.html#conversation-inference-supported-models-features).
 
-
 ## Agents and Assistants {#agents}
 
 The agent concept combines prompts, RAG (Retrieval Augmented Generation), and ReAct patterns in a single call. These components of agent-based logic are all supported by our Agents Kit. Using LLMs, business logic can be enriched by enabling AI agents to reason and autonomously execute actions while being grounded in domain-specific knowledge. With Mendix's Agents Kit, agents become a seamless part of your application's logic.
 
 For an overview of the components that help you get started, refer to [the Agents Kit overview](/appstore/modules/genai/#architecture). 
 
 In addition, you can integrate agentic behavior in a Mendix app by leveraging external agents through cloud infrastructure providers. In this case, the Mendix app does not store the agent definition. Instead, it only calls the external agent. For example, [Agents for Amazon Bedrock](https://aws.amazon.com/bedrock/agents/) provides this functionality for Amazon Bedrock. You can find out how to use this in your Mendix application in [Invoking an Agent with the InvokeAgent Operation](/appstore/modules/aws/amazon-bedrock/#invokeagent) section of the *Amazon Bedrock* module documentation.
-
-

content/en/docs/marketplace/platform-supported-content/modules/oidc.md

@@ -1146,4 +1146,4 @@ If a user logs in on one tab and then attempts to log in on another tab, a `401`
 
 ### Endpoints cannot be reached
 
-This issue can be caused by wrong configuration of your firewall. If you have a firewall between your application and your IdP, make sure it is properly configured for the consumption of the endpoints.
+This issue can be caused by wrong configuration of your firewall. If you have a firewall between your application and your IdP, make sure it is properly configured for the consumption of the endpoints.

content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md

@@ -42,15 +42,12 @@ Once the Mendix Data Loader is deployed, follow these steps to configure and use
 4. Click **Create** to create a new data source.
     1. Enter a **Name** for your data source within the Data Loader.
     2. Enter an **API endpoint** – that is, the base endpoint for the OData resource in your Mendix application, for example, `https://yourmendixapp.mendixcloud.com/odata/snowflakedata/v1/`.
-
 {{% alert color="warning" %}}This must be the root URL, that is, it must end in `/v1/` or `/v2/` Adding anything to the root URL (such as a resource path) will prevent the Mendix Data Loader from working.
 
 If you want to use specific resources, you should instead expose a new endpoint that only contains the resources that you require. This is because it is only possible to use every resource that is exposed in the OData endpoint, and impossible to exclude certain resources.{{% /alert %}}
-
     3. Use the **Use Delta Ingestion** check box to specify if you want to ingest all exposed data with every ingestion, or if you want to ingest only data that was newly created or changed since the last ingestion for this data source.
     4. Click **Save**.
     5. Grant the application **CREATE DATABASE** and **EXECUTE TASK** privileges. This step is necessary for the application to create the staging database for data ingestion and to execute tasks.
-
 5. To view the status of your data source, check the **Details**.
 6. To view the configuration status, click the **Authentication Configuration** tab.
 7. To set up authentication, click **Edit**, and then provide the required information based on the selected authentication type:
@@ -75,6 +72,7 @@ If you want to use specific resources, you should instead expose a new endpoint
 13. Click the **Data Ingestion** tab, where you can start your data ingestion or set up a schedule.
 14. Click **Ingest Now** to start a data ingestion.
 15. Click **New Task** to create a CRON job for scheduled data ingestions.
+
     * To schedule the data ingestion, specify the following parameters:
         * **Ingestion Task Schedule** – Choose from custom CRON expression, every day at 00:00 AM UTC, every Monday at 00:00 AM UTC, or every first day of the month at 00:00 AM UTC.
         * **Custom CRON Expression** – Use this field only when specifying a custom CRON expression.

content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md

@@ -147,14 +147,14 @@ Before use, please ensure you meet the following prerequisites:
 * Prior to adding a new font, the font files and font family have to already be included in your project. To add font files into the project, you can put the font files inside your styles/web directory.
 * Define font family in styling. You will need to define the new font by adding the font face custom styling.
 
-	```css
+    ```css
 	@font-face {
 	  font-family: 'Your-font-family-name';
 	  src: url('YourFontFile.ttf') format('truetype');
 	  font-weight: 100;
 	  font-style: normal;
 	}
-	```
+    ```
 
 #### Adding a Custom Font 
 

content/en/docs/mendix-portal/_index.md

@@ -24,4 +24,4 @@ Mendix Portal is the online platform from Mendix. It allows you to create, share
 * Academy — Explore learning paths.
 * [Community](/community-tools/) — Connect with Community members, and ask and answer questions.
 
-## Documents in This Category
+## Documents in This Category

content/en/docs/mendix-portal/maia-portal.md

@@ -59,4 +59,4 @@ Maia Chat supports asking follow-up questions based on your previous question an
 
 Maia Chat only keeps track of a conversation history within a session on a page in Mendix Portal.
 
-{{% /alert %}}
+{{% /alert %}}

content/en/docs/private-platform/configuration/pmp-configure-aws-secret.md

@@ -78,13 +78,13 @@ When creating a property to use as a key for external secret storage, use the fo
 
         * BuildPackage
 
-             * fileServerBasic
+            * fileServerBasic
 
                 * **BuildPackage.FileBasicAuthPassword** - Password for the file server
 
-             * AwsAKSK
+            * AwsAKSK
 
-                 * **BuildPackage.AwsSecretAccessKey** - AWS secret access key for the file server
+                * **BuildPackage.AwsSecretAccessKey** - AWS secret access key for the file server
 
         * RuntimeBaseImage
 
@@ -292,7 +292,7 @@ The following example shows how you can configure Private Mendix Platform to wor
 
     The secret template contains a sample key structure which you can use:
 
-        ```text
+    ```text
         {  //...other keys
             "VCS": {
                 // ...other keys
@@ -301,7 +301,7 @@ The following example shows how you can configure Private Mendix Platform to wor
                 },
             // ...other keys
         }
-        ```
+    ```
 
 8. Repeat the process for other credentials as needed, ensuring you follow the naming conventions for each service.
 

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

@@ -42,7 +42,6 @@ For MxBuild and macOS users:
 If you are using the macOS version of Studio Pro and you store your project files on an external drive not formatted using the Apple File System, macOS can generate hidden files and folders that can make Windows versions of Studio Pro or MxBuild not work as expected.
 {{% /alert %}}
 
-
 ## Command Line
 
 To build your package, specify the Mendix app file (*.mpr*) for which you want to build the deployment package (*.mda*) on the command-line. The file name may be preceded by a relative or absolute path. The app file should be located inside a Mendix app directory.

content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/best-practices.md

@@ -143,11 +143,13 @@ Attribute paths can not be used in sort orderings in offline apps.
 ## Enhancing Persistent Mode in File Storage {#persistent-mode}
 
 When using offline profiles, files are stored locally on a user's device in the browser Origin Private File System (OPFS). The OPFS can operate in two modes: **persistent** and **best-effort**. The **persistent** mode is preferable because it offers greater storage capacity and better data durability. While **persistent** mode is used by default, a browser may opt for **best-effort** mode if it assesses the site's importance as low. This assessment is made based on internal browser heuristics, which include the following:
+
 * The level of site engagement
 * Whether the site has been bookmarked
 * Whether permission for site notifications has been granted
 
 To enhance the likelihood of operating the OPFS in 'persistent' mode, consider taking the following actions:
+
 * Bookmark the site
 * Enable notifications for the site
 

content/en/docs/refguide/mobile/distributing-mobile-apps/testing-mobile-apps.md

@@ -99,10 +99,10 @@ While using Espresso in combination with Mendix apps, there have been occasional
 
 ```json
 {
-"toolsVersions": {
-    "compileSdk": "30"
-    ...
-}
+    "toolsVersions": {
+        "compileSdk": "30"
+        ...
+    }
 }
 ```
 

content/en/docs/refguide/modeling/menus/translatable-texts/advanced-translations-export.md

@@ -53,4 +53,4 @@ After completion, a confirmation pop-up appears. If the operation fails, a failu
 
 {{% alert color="warning" %}}
 Do not close the app while the export is running.
-{{% /alert %}}
+{{% /alert %}}

content/en/docs/refguide10/mobile/distributing-mobile-apps/testing-mobile-apps.md

@@ -99,10 +99,10 @@ While using Espresso in combination with Mendix apps, there have been occasional
 
 ```json
 {
-"toolsVersions": {
-    "compileSdk": "30"
-    ...
-}
+    "toolsVersions": {
+        "compileSdk": "30"
+        ...
+    }
 }
 ```
 

content/en/docs/refguide9/mobile/distributing-mobile-apps/testing-mobile-apps.md

@@ -85,10 +85,8 @@ To set up Appium Desktop for native Android testing, do the following:
 
 1. Click on the blue **Select Elements** button, and then click on an element in the app preview to spy on that element.
 
-
 ### Troubleshooting Espresso
 
-
 While using Espresso in combination with Mendix apps, we observed a `No static method lifecycleEventObserver` error. More information about this can be found [here](https://github.com/appium/appium-espresso-driver/issues/639). You can fix this by adding the `espressoBuildConfig` property to the capabilities. It should point to a JSON file containing:
 
 ```json
@@ -101,10 +99,10 @@ While using Espresso in combination with Mendix apps, there have been occasional
 
 ```json
 {
-"toolsVersions": {
-    "compileSdk": "30"
-    ...
-}
+    "toolsVersions": {
+        "compileSdk": "30"
+        ...
+    }
 }
 ```
 

content/en/docs/releasenotes/marketplace/marketplace-services/_index.md

@@ -9,4 +9,4 @@ numberless_headings: true
 
 The Marketplace Services Release Notes include updates to services delivered through the Mendix Marketplace:
 
-* [Private PDF Document Generation Service](/releasenotes/marketplace/private-service/)
+* [Private PDF Document Generation Service](/releasenotes/marketplace/private-service/)

content/en/docs/releasenotes/marketplace/marketplace-services/private-service.md

@@ -22,4 +22,4 @@ With this version of the private PDF Document Generation service, we have improv
 
 ### Private PDF Document Generation Service
 
-The [PDF Document Generation](/appstore/modules/document-generation/) module now supports the use of [private PDF document generation service instances](/appstore/services/private-document-generation-service/). This flexible solution is based on Docker, and is hosted and managed by you. It allows you to run your own version of the PDF Document Generation service with additional control and configuration options, and it specifically targets air-gapped apps, or tailored performance and data sharing requirements.
+The [PDF Document Generation](/appstore/modules/document-generation/) module now supports the use of [private PDF document generation service instances](/appstore/services/private-document-generation-service/). This flexible solution is based on Docker, and is hosted and managed by you. It allows you to run your own version of the PDF Document Generation service with additional control and configuration options, and it specifically targets air-gapped apps, or tailored performance and data sharing requirements.

content/en/docs/releasenotes/mobile/native-template/_index.md

@@ -9,6 +9,7 @@ description: "Native Template release notes."
 For more information on native mobile app development, see the [native-template](https://github.com/mendix/native-template/) repository and the [Building, Testing, and Distributing Apps](/refguide/mobile/distributing-mobile-apps/) guide. Below you can see the current versions in active development and which Mendix Studio Pro versions they correspond with.
 
 Compatible with Studio Pro 11:
+
 * Native Template versions of [15](/releasenotes/mobile/nt-15-rn/) are compatible with apps built using Studio Pro [11.0](/releasenotes/studio-pro/11.0/) and above.
 
 Compatible with Studio Pro 10:

content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/_index.md

@@ -8,4 +8,4 @@ description: "Studio Pro 11 compatible Native Template release notes."
 These are the current Native Template versions for Studio Pro 11 in active development:
 
 * Native Template versions of [15](/releasenotes/mobile/nt-15-rn/) are compatible with apps built using the following versions of Studio Pro:
-    * Studio Pro 11.0 and above.
+    * Studio Pro 11.0 and above.

content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-15-rn.md

@@ -11,8 +11,8 @@ description: "Native Template 15"
 
 ### Improvements
 
-- We migrated several libraries that had not been maintained to modern, actively-supported alternatives.
-- We improved the update process from an older version of Studio Pro to the latest version.
+* We migrated several libraries that had not been maintained to modern, actively-supported alternatives.
+* We improved the update process from an older version of Studio Pro to the latest version.
 
 ### Removed
 
@@ -34,11 +34,11 @@ description: "Native Template 15"
 
 ### Improvements
 
-- We updated one library.
+* We updated one library.
 
 ### Library Updates and Improvements
 
-- **@mendix/native**: 10.1.4
+* **@mendix/native**: 10.1.4
 
 ## 15.1.1 {#1511}
 
@@ -66,8 +66,8 @@ description: "Native Template 15"
 
 ### Improvements
 
-- We upgraded our Database Backend Library to the most recent version. This update brings better performance on database operations and performance improvements. 
+* We upgraded our Database Backend Library to the most recent version. This update brings better performance on database operations and performance improvements. 
 
 ### Library Updates and Improvements
 
-- **@op-engineering/op-sqlite**: 12.0.2
+* **@op-engineering/op-sqlite**: 12.0.2

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

@@ -77,7 +77,7 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 ### Known Issues
 
 * Importing a module containing workflows makes all running workflow instances incompatible. (Ticket 234084)
-  * Fixed in [10.21.0](/releasenotes/studio-pro/10.21/#fix-workflow-instances).
+    * Fixed in [10.21.0](/releasenotes/studio-pro/10.21/#fix-workflow-instances).
 * In the React client, re-running an app locally with runtime-only changes does not properly apply those changes. (Tickets 253176, 253539, 253842, 253932, 254100)
 * In the React client, the debugger does not reconnect when restarting an app.
 

content/en/docs/releasenotes/studio-pro/11/11.0.md

@@ -359,4 +359,4 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro
 * In the React client, re-running an app locally with runtime-only changes does not properly apply those changes. (Tickets 253176, 253539, 253842, 253932, 254100)
     * Fixed in [11.1.0](/releasenotes/studio-pro/11.1/#fix-runtime-only-changes)
 * In the React client, the debugger does not reconnect when restarting an app.
-    * Fixed in [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect)
+    * Fixed in [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect)