[Auto] Lint docs

content/en/docs/academy/_index.md

@@ -44,4 +44,3 @@ Refer to the following pages for details on Mendix Academy exams:
 * [Purchasing Mendix Exam Seats](/academy/purchasing-exams/)
 * [Managing Exam Seats](/academy/purchasing-exams/manage-exam-seats/)
 * [Managing Exam Admins](/academy/purchasing-exams/manage-exam-admins/)
-

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md

@@ -277,11 +277,11 @@ The user can use the optional attribute [`allowUpload`](#allow-upload) with defa
 
 #### XML Attributes
 
-| Attribute  	| Required | Attribute Type | Description                                                           |
+| Attribute      | Required | Attribute Type | Description                                                           |
 |---------------|----------|----------------|-----------------------------------------------------------------------|
-| `type`     	| Yes      | String         | Must be `image`                                                       |
-| `key`      	| Yes      | String         | See [key](#key)                                                       |
-| `required` 	| No       | Boolean        | Whether the property must be specified by the user, `true` by default |
+| `type`         | Yes      | String         | Must be `image`                                                       |
+| `key`          | Yes      | String         | See [key](#key)                                                       |
+| `required`     | No       | Boolean        | Whether the property must be specified by the user, `true` by default |
 | `allowUpload` | No       | Boolean        | See [allowUpload](#allow-upload)                                      |
 
 #### Studio Pro UI

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

@@ -58,8 +58,7 @@ To send your runtime information to Splunk Cloud Platform, you need to set it up
 {{% /alert %}}
 </div>
 
-
-5. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment.
+1. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment.
 
     {{% alert color="warning" %}}The first time you set up the Splunk Cloud Platform integration, you must redeploy your app and then restart it. Just restarting the app is not sufficient because additional dependencies need to be included.{{% /alert %}}
 

content/en/docs/marketplace/platform-supported-content/modules/global-inbox.md

@@ -140,4 +140,4 @@ Any user that can see a task in Publisher Application can see the same task in t
 
 * **Global Inbox** does not support [Workflow Groups](/refguide/workflow-groups/) at the moment. This will be introduced at a later stage.
 * The beta version of **Global Inbox** has limited support for error handling. Any exceptions that occur in a microflow after updating a user task (or other Workflow-related entity) in the same microflow (for example, updating the targeted users or due date) might result in data becoming out of sync. This is a temporary limitation that will be resolved in an upcoming version.
-* Workflows and tasks that are modeled in the same app that includes the Global Inbox module are NOT available in the Global Inbox. The Global Inbox app only consumes and displays workflow instances from other Mendix applications.
+* Workflows and tasks that are modeled in the same app that includes the Global Inbox module are NOT available in the Global Inbox. The Global Inbox app only consumes and displays workflow instances from other Mendix applications.

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

@@ -68,7 +68,7 @@ If you want to use specific resources, you should instead expose a new endpoint
 9. Click **Back** to return to the **Details** page.
 10. Click the **Ingestion Configuration** tab to set up your ingestion destination table.
 11. Click **Create** to start setting up the Ingestion Configuration.
-    * **Target Database** – Name of the database for data ingestion
+    ***Target Database** – Name of the database for data ingestion
     * **Target Schema** – Target schema where all data will be ingested
 12. Click **Save**.
 13. Click the **Data Ingestion** tab, where you can start your data ingestion or set up a schedule.

content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-ai-data-connector.md

@@ -315,7 +315,7 @@ To configure your Mendix app for Snowflake Cortex Analyst, perform the following
 
  {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-ai-data-connector/CortexAnalystRequestExample.png" >}}
 
- ## Configuring Snowflake Cortex Search {#cortex-search}
+## Configuring Snowflake Cortex Search {#cortex-search}
 
 Snowflake Cortex Search is a fully-managed, ML-powered Snowflake Cortex feature that helps you retrieve data relevant to a prompt to help an LLM generate informed answers (Retrieval Augmented Generation).
 

content/en/docs/refguide/modeling/integration/odata-services/build-odata-apis.md

@@ -505,7 +505,6 @@ You can generate and reuse generated validation microflows. The following exampl
     }
      ```
 
-
 ### Deleting Data
 
 Deleting is provided using the `DELETE` operation. See the following `DELETE` request:

content/en/docs/refguide/modeling/menus/version-control-menu/_index.md

@@ -76,4 +76,4 @@ The **Add Snapshot of Data** option creates a snapshot of the built-in database
 
 * [Studio Pro Overview](/refguide/studio-pro-overview/)
 * [Version Control](/refguide/version-control/)
-* [Pulling, Committing, and Pushing](/refguide/pushing-pulling/)
+* [Pulling, Committing, and Pushing](/refguide/pushing-pulling/)

content/en/docs/refguide/modeling/menus/version-control-menu/commit-dialog.md

@@ -79,4 +79,4 @@ If any synchronization fails during this step, you are asked if the commit shoul
 
 ## Read More
 
-* [Pulling, Committing, and Pushing](/refguide/pushing-pulling/)
+* [Pulling, Committing, and Pushing](/refguide/pushing-pulling/)

content/en/docs/refguide/modeling/menus/version-control-menu/download-from-version-control-dialog.md

@@ -53,4 +53,4 @@ Choose the **App directory** to which want to download the app. The suggested na
 ## Read More
 
 * [Enabling Version Control for Your App](/refguide/version-control/enable/)
-* [Optional: Working with Private Git](/refguide/on-premises-git/)
+* [Optional: Working with Private Git](/refguide/on-premises-git/)

content/en/docs/refguide/modeling/menus/version-control-menu/history-dialog.md

@@ -95,4 +95,4 @@ This tab shows a list of stories that are related to the changes.
 
 * [Version Control](/refguide/version-control/)
 * [Stories Pane](/refguide/stories-pane/)
-* [Using Version Control History](/refguide/version-control-using-history/)
+* [Using Version Control History](/refguide/version-control-using-history/)

content/en/docs/refguide/modeling/menus/version-control-menu/merge-dialog.md

@@ -64,4 +64,4 @@ Choose the branch line that you want to merge. It is not necessary to select ind
 ## Read More
 
 * [Pulling, Committing, and Pushing](/refguide/pushing-pulling/)
-* [Combining Changes and Resolving Conflicts](/refguide/resolving-conflicts/)
+* [Combining Changes and Resolving Conflicts](/refguide/resolving-conflicts/)

content/en/docs/refguide/modeling/xpath/xpath-constraints/xpath-constraint-functions/_index.md

@@ -26,4 +26,4 @@ The following pages describe the functions that can be executed within constrain
 
 {{% alert color="info" %}}
 In all these functions, the attribute in the example is just the name of the attribute, for example `Name`. This is for clarity. However, the attribute can also contain the path to the attribute, for example `Sales.Order_Customer/Sales.Customer/Name`.
-{{% /alert %}}
+{{% /alert %}}

content/en/docs/refguide/runtime/custom-settings/_index.md

@@ -289,7 +289,7 @@ The settings below influence the behavior of the Mendix web client.
 | <a id="commendixwebuiFeedbackSizeWarningThreshold" href="#commendixwebuiFeedbackSizeWarningThreshold">com.<wbr>mendix.<wbr>webui.<wbr>FeedbackSizeWarningThreshold</a> | A warning is logged when the feedback size exceeds the threshold. Feedback is sent from server to client to instruct (for example, to refresh objects or to open a page). They are serialized as "instructions" in the server response. If there are too many instructions, this can have performance implications, as they all have to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 5000 |
 | <a id="commendixwebuiStateSizeWarningThreshold" href="#commendixwebuiStateSizeWarningThreshold">com.<wbr>mendix.<wbr>webui.<wbr>StateSizeWarningThreshold</a> | A warning is logged when the state size exceeds the threshold. The state consists of changes in objects and of objects not committed to the database (yet). If there is too much state, this will have performance implications, as the whole state has to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 100 |
 | <a id="commendixwebuiCommittedObjectsThreshold" href="#commendixwebuiCommittedObjectsThreshold">com.<wbr>mendix.<wbr>webui.<wbr>CommittedObjectsThreshold</a> | The threshold controls how much data is sent back to the client after executing a microflow. By default, we send back full objects when they are changed or committed. When this threshold is reached, only object GUIDs are sent back instead so that the client knows about the changes while the amount of data sent over the network is reduced. The client will then retrieve the objects later on, if needed. | 100 |
-| <a id="MaxRetrieveAmount" href="#MaxRetrieveAmount">MaxRetrieveAmount</a> | The maximum number of objects the client is allowed to retrieve by list widgets using database datasource runtime operation.<br/>When requesting more objects than allowed, the runtime will enforce the `MaxRetrieveAmount` by setting a limit on the query and will log the following warning: `A retrieve action requested more objects than allowed by the `MaxRetrieveAmount` runtime setting. Amount requested: (...), MaxRetrieveAmount: (...).`<br />*This setting was introduced in Mendix version 11.8.0 and 11.6.5 MTS* |  |
+| <a id="MaxRetrieveAmount" href="#MaxRetrieveAmount">MaxRetrieveAmount</a> | The maximum number of objects the client is allowed to retrieve by list widgets using database datasource runtime operation.<br/>When requesting more objects than allowed, the runtime will enforce the `MaxRetrieveAmount` by setting a limit on the query and will log the following warning: `A retrieve action requested more objects than allowed by the`MaxRetrieveAmount`runtime setting. Amount requested: (...), MaxRetrieveAmount: (...).`<br />*This setting was introduced in Mendix version 11.8.0 and 11.6.5 MTS* |  |
 
 ## Metrics Settings{#metrics-settings}
 

content/en/docs/refguide/testing/_index.md

@@ -80,4 +80,4 @@ Performance testing involves unit-level performance checks for critical microflo
 
 You can use the following offerings to help with this test type:
 
-* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).
+* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).

content/en/docs/refguide/version-control/configure/version-control-enable.md

@@ -44,4 +44,4 @@ If version control was disabled during the app creation, you can enable it by pe
 
 1. In Studio Pro, open the [Version Control menu](/refguide/upload-to-version-control-dialog/).
 2. Click **Upload to Version Control Server**.
-3. Select the server where you want to store the app. You can also create a new server.
+3. Select the server where you want to store the app. You can also create a new server.

content/en/docs/refguide/version-control/using-version-control-in-studio-pro/deploy-external.md

@@ -76,5 +76,3 @@ git fetch --depth 1 origin <sha1-of-commit-of-interest>
 # reset this repository's master branch to the commit of interest
 git reset --hard FETCH_HEAD
 ```
-
-

content/en/docs/refguide/version-control/using-version-control-in-studio-pro/peer-review.md

@@ -25,4 +25,4 @@ The [Name and Email settings](/refguide/preferences-dialog/#name) can be adjuste
 
 Select a revision to see additional details, such as related stories, changed documents, Studio Pro version, and changes on disk. Icons summarize the kinds of changes that happened in the app.
 
-{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/history-dialog/revisions.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/history-dialog/revisions.png" class="no-border" >}}

content/en/docs/refguide/version-control/using-version-control-in-studio-pro/push-pull.md

@@ -154,4 +154,4 @@ If your team is committing often, you then should pull often. Frequent pulling h
 
 ## Read More
 
-* [Mx Command-Line Tool: Merging and Diffing Commands](/refguide/mx-command-line-tool/#merging-and-diffing-commands)
+* [Mx Command-Line Tool: Merging and Diffing Commands](/refguide/mx-command-line-tool/#merging-and-diffing-commands)

content/en/docs/refguide/version-control/using-version-control-in-studio-pro/reverting-changes.md

@@ -45,4 +45,4 @@ Reverting changes is done with one commit at a time. If you want to revert multi
 
 You can also revert a commit where another branch was merged into the current branch. Reverting a merge removes the changes introduced by that merge, making it appear as if they never happened. For example, if the merge added a new page, reverting it will remove the page locally. 
 
-Just like with a normal merge, conflicts can occur when reverting a merge. For example, if later commits change the new page, the reverse merge will result in a conflict. Once you resolved the conflict, you can commit the changes and push them to the remote repository.
+Just like with a normal merge, conflicts can occur when reverting a merge. For example, if later commits change the new page, the reverse merge will result in a conflict. Once you resolved the conflict, you can commit the changes and push them to the remote repository.

content/en/docs/refguide/version-control/version-control-troubleshooting/_index.md

@@ -208,4 +208,4 @@ To solve this issue, perform the following steps:
 2. Abort the current operation in Studio Pro.
 3. Retry the operation. 
 
-## Read More
+## Read More

content/en/docs/refguide10/runtime/custom-settings/_index.md

@@ -282,7 +282,7 @@ The settings below influence the behavior of the Mendix web client.
 | <a id="commendixwebuiFeedbackSizeWarningThreshold" href="#commendixwebuiFeedbackSizeWarningThreshold">com.<wbr>mendix.<wbr>webui.<wbr>FeedbackSizeWarningThreshold</a> | A warning is logged when the feedback size exceeds the threshold. Feedback is sent from server to client to instruct (for example, to refresh objects or to open a page). They are serialized as "instructions" in the server response. If there are too many instructions, this can have performance implications, as they all have to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 5000 |
 | <a id="commendixwebuiStateSizeWarningThreshold" href="#commendixwebuiStateSizeWarningThreshold">com.<wbr>mendix.<wbr>webui.<wbr>StateSizeWarningThreshold</a> | A warning is logged when the state size exceeds the threshold. The state consists of changes in objects and of objects not committed to the database (yet). If there is too much state, this will have performance implications, as the whole state has to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 100 |
 | <a id="commendixwebuiCommittedObjectsThreshold" href="#commendixwebuiCommittedObjectsThreshold">com.<wbr>mendix.<wbr>webui.<wbr>CommittedObjectsThreshold</a> | The threshold controls how much data is sent back to the client after executing a microflow. By default, we send back full objects when they are changed or committed. When this threshold is reached, only object GUIDs are sent back instead so that the client knows about the changes while the amount of data sent over the network is reduced. The client will then retrieve the objects later on, if needed. | 100 |
-| <a id="MaxRetrieveAmount" href="#MaxRetrieveAmount">MaxRetrieveAmount</a> | The maximum number of objects the client is allowed to retrieve by list widgets using database datasource runtime operation.<br/>When requesting more objects than allowed, the runtime will enforce the `MaxRetrieveAmount` by setting a limit on the query and will log the following warning: `A retrieve action requested more objects than allowed by the `MaxRetrieveAmount` runtime setting. Amount requested: (...), MaxRetrieveAmount: (...).`<br />*This setting was introduced in Mendix version 10.24.16* |  |
+| <a id="MaxRetrieveAmount" href="#MaxRetrieveAmount">MaxRetrieveAmount</a> | The maximum number of objects the client is allowed to retrieve by list widgets using database datasource runtime operation.<br/>When requesting more objects than allowed, the runtime will enforce the `MaxRetrieveAmount` by setting a limit on the query and will log the following warning: `A retrieve action requested more objects than allowed by the`MaxRetrieveAmount`runtime setting. Amount requested: (...), MaxRetrieveAmount: (...).`<br />*This setting was introduced in Mendix version 10.24.16* |  |
 
 ## Metrics Settings{#metrics-settings}
 

content/en/docs/refguide10/testing/_index.md

@@ -80,4 +80,4 @@ Performance testing involves unit-level performance checks for critical microflo
 
 You can use the following offerings to help with this test type:
 
-* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).
+* [Tracing](/refguide/tracing-in-runtime/) - Generates traces that help you analyze errors and performance, which can be sent to observability tools like [Jaeger](https://www.jaegertracing.io/) or [Datadog](https://www.datadoghq.com/).

content/en/docs/refguide9/general/install.md

@@ -62,6 +62,7 @@ Sometimes you can run into problems when installing Studio Pro. One work-around
 The prerequisites are the following:
 
 * Microsoft .NET Desktop Runtime
+
     | Studio Pro 9.0.0 - 9.24.33 | Studio Pro 9.24.34 - 9.24.41 | Studio Pro 9.24.42 and above |
     | --- | --- | --- |
     |  [Microsoft .NET Desktop Runtime 6.0.x](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) – Mendix recommends using version 6.0.6 or above | [Microsoft .NET Desktop Runtime 8.0.x](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) – Mendix recommends using version 8.0.14 or above | [.NET Desktop Runtime 10.0.x (x64 or ARM64)](https://dotnet.microsoft.com/en-us/download/dotnet/10.0) <br/> Mendix recommends using version 10.0.3 or above |

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

@@ -9,7 +9,7 @@ description: "Native Template 14"
 
 **Release date: Feb 25, 2026**
 
-- We updated `.gitignore` to more precisely exclude `node_modules` directories in specific locations.
+* We updated `.gitignore` to more precisely exclude `node_modules` directories in specific locations.
 
 ## 14.1.13 {#1423}