Run markdownlint-cli2 on docs to find (and correct) linting errors.

NatasaKralj · MarkvanMents · commit 69850fac0999 · 2025-01-01T20:13:10.000Z
diff --git a/content/en/docs/apidocs-mxsdk/apidocs/catalog/registration-api.md b/content/en/docs/apidocs-mxsdk/apidocs/catalog/registration-api.md
@@ -239,7 +239,6 @@ Completing the `PUT` operation call more than once overwrites the details for al
 
 It is possible (although uncommon) to update the URL of a hosted environment. The root URLs update upon redeployment, and endpoints that are registered under that environment get updated endpoint locations.
 
-
 ### Preparing Your Service Details Using the Transform API {#transform-api}
 
 The Transform API is an endpoint in the Registration API. It converts the *dependencies.json* file that your Mendix app generates into the structure the Registration API requires to register services.
@@ -348,4 +347,4 @@ A successful `PUT` call results in a `200` status code and a JSON response body.
 
 ## API Reference {#api-reference}
 
-{{< swaggerui src="/openapi-spec/catalog-registration_v5.yaml" >}}
+{{< swaggerui src="/openapi-spec/catalog-registration_v5.yaml" >}}
diff --git a/content/en/docs/apidocs-mxsdk/apidocs/catalog/search-api.md b/content/en/docs/apidocs-mxsdk/apidocs/catalog/search-api.md
@@ -13,7 +13,6 @@ The Search API enables users to search and retrieve assets that are registered i
 
 You can paginate through search results with an offset, which allows you to limit the number of results and specify how many to skip.
 
-
 ## Authentication and Access Rights
 
 To use the Catalog Search API, you need the following:
diff --git a/content/en/docs/appstore/use-content/platform-supported-content/modules/aws/amazon-bedrock.md b/content/en/docs/appstore/use-content/platform-supported-content/modules/aws/amazon-bedrock.md
@@ -185,7 +185,6 @@ To invoke a Bedrock agent for your Mendix app, do the following steps:
 7. Select a microflow that takes an **AmazonBedrockConnector.InvokeAgentResponse** object as an input and handles that response.
     This is necessary because InvokeAgent is an asynchronous operation which means that it will not necessarily finish when the process that it was invoked from finishes. By giving the operation a handler microflow, the response can be handled as soon as it arrives. For an example handler microflow, see **AmazonBedrockConnector.InvokeAgentResponse_Handle** in the connector module. This microflow logs the response, so you can also use it just to investigate the response.
 
-
 ### Token Usage {#tokenusage}
  
 [Token usage](/appstore/modules/genai/commons/#token-usage) monitoring is now possible for the following operations: 
diff --git a/content/en/docs/appstore/use-content/platform-supported-content/modules/file-uploader.md b/content/en/docs/appstore/use-content/platform-supported-content/modules/file-uploader.md
@@ -96,5 +96,3 @@ This nanoflow will attach an uploaded file to the context object.
 #### ACT_CreateUploadedImageDocument
 
 This nanoflow will attach an uploaded image to the context object.
-
-
diff --git a/content/en/docs/appstore/use-content/platform-supported-content/modules/snowflake/snowflake-rest-sql.md b/content/en/docs/appstore/use-content/platform-supported-content/modules/snowflake/snowflake-rest-sql.md
@@ -111,6 +111,7 @@ To set this up:
 3. Duplicate the **Call REST (POST)** action, modify the **async** query parameter to **true**, and use this as a basis to build your custom asynchronous microflows.
 
 Your custom microflows should consist of the following:
+
 * **A request call microflow** - Sends the request and returns the request ID.
 * **A polling microflow** - Uses the request ID to check if the response is available, and then returns the response once it is ready.
 
@@ -268,6 +269,6 @@ To configure your Mendix app for Snowflake Cortex Analyst, perform the following
    
  {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-rest-sql/CortexAnalystRequestExample.png" >}}
 
- ### Example Implementation
+### Example Implementation
 
  The [Snowflake showcase app](https://marketplace.mendix.com/link/component/225845) contains example implementations of the Analyst, ANOMALY DETECTION, COMPLETE and TRANSLATE functionalities. For more information, see [Snowflake Cortex Analyst](/appstore/modules/genai/snowflake-cortex/#functionalities).
diff --git a/content/en/docs/catalog/manage/search.md b/content/en/docs/catalog/manage/search.md
@@ -247,4 +247,4 @@ When an item is selected in the search results pane, you can click the [Landscap
 
 ## Search using the API
 
-To use the Catalog Search API, see [Search API](/apidocs-mxsdk/apidocs/search-api/).
+To use the Catalog Search API, see [Search API](/apidocs-mxsdk/apidocs/search-api/).
diff --git a/content/en/docs/catalog/register/register-data.md b/content/en/docs/catalog/register/register-data.md
@@ -84,7 +84,7 @@ Follow the steps below:
     * **Non-production** – hosting is paid for, but data is not of production quality
 
 8. Select your **Authentication** method. For details on supported authentication types, see the [Authentication](#authentication) section below. Curators can also [add or change authentication methods](/catalog/manage/curate/#authentication) later.
-9.  Select **Done!** to complete the registration.
+9. Select **Done!** to complete the registration.
 
 Congratulations! Your service is registered in the Catalog. 
 
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/monitoring-application-health/_index.md b/content/en/docs/deployment/mendix-cloud-deploy/monitoring-application-health/_index.md
@@ -206,8 +206,6 @@ The reason you receive a message is that when you are using a [basic license](/d
 
 The autoscaling might occur when your app does not have high resource usage because of the way shared databases are managed. More resources may be required by an app using another schema on the shared database. This is a known phenomenon, which AWS terms a [noisy neighbor](https://docs.aws.amazon.com/wellarchitected/latest/saas-lens/noisy-neighbor.html).
 
-
-
 ## Read More
 
 * [Metrics](/developerportal/operate/metrics/)
diff --git a/content/en/docs/developerportal/security-summary.md b/content/en/docs/developerportal/security-summary.md
@@ -66,4 +66,4 @@ For information about security practices for app governance, refer to the follow
 
 ## Getting Support
 
-For additional information, frequently asked questions, and troubleshooting tis, refer to [Frequently Asked Questions – Security](/support/security-findings-faq/). If you have more questions, contact your Customer Success Manager (CSM), or join the [Mendix Community forum](https://community.mendix.com/p/community).
+For additional information, frequently asked questions, and troubleshooting tis, refer to [Frequently Asked Questions – Security](/support/security-findings-faq/). If you have more questions, contact your Customer Success Manager (CSM), or join the [Mendix Community forum](https://community.mendix.com/p/community).
diff --git a/content/en/docs/refguide/mobile/distributing-mobile-apps/building-native-apps/bitrise.md b/content/en/docs/refguide/mobile/distributing-mobile-apps/building-native-apps/bitrise.md
@@ -17,7 +17,7 @@ Before starting this guide, make sure you have completed the following prerequis
 * Signed up for a [Bitrise account](https://app.bitrise.io/users/sign_up)
 * Read the [Getting Starting guide from Bitrise](https://devcenter.bitrise.io/en/getting-started.html) and understand the key concepts of Bitrise
 * Have access to a Mendix application project with a native mobile profile as a developer
-   * The Mendix application is deployed
+    * The Mendix application is deployed
 * Have created the native template project for your app by following [Using Mendix Native Mobile Builder to Set Up Your Local App](/refguide/mobile/distributing-mobile-apps/building-native-apps/native-build-locally/#using-mendix-native-mobile-builder-to-set-up-your-local-app). Make sure to set the GitHub token to also create a GitHub repository.
 * Fulfilled the prerequisites below for all operating systems you want to target:
 
@@ -41,7 +41,7 @@ To set up your build project, do the following:
 1. Create a new project in the workspace.
 1. Select the GitHub project generated by **Build Native App** as the repository. It is recommended to use the **GitHub App Integration**:
 
-	{{< figure src="/attachments/refguide/mobile/distributing-mobile-apps/building-native-apps/bitrise/select-repository.png" alt="Select repository" width="350" class="no-border" >}}
+    {{< figure src="/attachments/refguide/mobile/distributing-mobile-apps/building-native-apps/bitrise/select-repository.png" alt="Select repository" width="350" class="no-border" >}}
 
 1. Select the `master` branch and let Bitrise auto-detect the configuration.
 1. Confirm that the correct configuration has been detected:
@@ -125,7 +125,6 @@ After these changes, your workflow should look like this (if you target both ope
 
 {{< figure src="/attachments/refguide/mobile/distributing-mobile-apps/building-native-apps/bitrise/select-repository.png" alt="Completed workflow" width="350" class="no-border" >}}
 
-
 ## Build Your App
 
 Builds can be started manually or automatically. To start a build manually, open the build project and click **Start build** and confirm the dialog. A typical build will take approximately 20 minutes, but can take longer for complex applications with many dependencies.
@@ -140,4 +139,4 @@ To set up automatic builds after running **Build Native App**, follow these step
 1. Select **Push branch** for **Condition 1** and change the **Push** branch to `master`.
 1. Select the **deploy** workflow and confirm.
 
-Now, every time some runs **Build Native App** to update the application bundle, a new build will be triggered in Bitrise.
+Now, every time some runs **Build Native App** to update the application bundle, a new build will be triggered in Bitrise.
diff --git a/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md b/content/en/docs/refguide/modeling/mendix-ai-assistance/maia-chat.md
@@ -76,4 +76,4 @@ For information on the supported shortcut keys in Maia Chat, see the [Maia Chat
 
 ## Read More
 
-* [Maia Learn](/refguide/maia-learn/)
+* [Maia Learn](/refguide/maia-learn/)
diff --git a/content/en/docs/refguide/runtime/monitoring-mendix-runtime.md b/content/en/docs/refguide/runtime/monitoring-mendix-runtime.md
@@ -538,6 +538,7 @@ Returns feedback about the Mendix Runtime.
 
 Log subscriber is what renders logs. By changing log subscribers it is possible to configure the logs format. 
 For that you need to make three steps:
+
 1. Get the name of your current log subscriber
 2. Delete your current log subscriber
 3. Create new log subscriber
diff --git a/content/en/docs/refguide/version-control/version-control-troubleshooting/repository-size.md b/content/en/docs/refguide/version-control/version-control-troubleshooting/repository-size.md
@@ -69,6 +69,7 @@ Before converting the MPR format it is recommended to commit your local work to
 When a file exceeds the Git compression threshold, 512 MB by default, Git will store a full copy of the file with each new revision instead of only storing the delta. This results in extremely rapid repository growth with both client and server-side consequences.
 
 As the Mendix model is stored in a single file, this threshold can be exceeded by the *.mpr* file. To decrease the MPR file size, consider doing the following:
+
 * [Convert to MPRv2](#convert) – By splitting the single binary file into multiple files, your file size will drop below the compression threshold.
 * Remove [excluded and unused documents](/refguide/dev-best-practices/#excluded-and-unused-documents) – If you have a large number of unnecessary documents in your app model, this can significantly increase the size of the MPR file.
 * Decrease duplication in pages – If you have a number of pages featuring the same content, such as an advanced datagrid, consider extracting this piece of logic to a widget. Reusing a widget on multiple pages prevents the data from being saved several times and can have a large impact on the size of the MPR file.
@@ -119,7 +120,6 @@ To conclude whether the situation is acceptable for you, follow these steps:
 * Ensure the Git app you are downloading is not yet on your machine
 * Download the branch through Studio Pro, while manually measuring how long the download takes
   
-
 The first download of a branch on a device is a good indication of the maximum waiting time you or your team member can experience. Subsequent branch downloads use data that is already available locally and will, therefore, be a lot faster.
 
 If the download time was acceptable, or if you have a process where team members do not change often and they do not have to download an app for the first time, you can skip the cleanup.
@@ -215,7 +215,6 @@ We recommend doing the following:
 * Check your git config settings, especially any setting that involves encoding or text conversions: run `git config --list --show-origin`.
 * Consider moving your local repo, so that its folder has a shorter name
   
-
 When reaching out to Mendix Support, please include:
 
 * App/Projects ID for your app
diff --git a/content/en/docs/releasenotes/catalog/_index.md b/content/en/docs/releasenotes/catalog/_index.md
@@ -16,7 +16,6 @@ These release notes cover changes made to the [Catalog](/catalog/).
 
 ### December 12, 2024
 
-
 #### Features
 
 * You can now register new, and update existing, REST and Web Services through the Catalog UI. 
diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-9-parent/nt-10-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-9-parent/nt-10-rn.md
@@ -20,19 +20,19 @@ description: "Native Template 10 release notes."
 
 #### Library Updates and Improvements
 
-- **@react-native-async-storage/async-storage:** 2.0.0  
-- **@react-native-community/datetimepicker:** 8.2.0  
-- **@react-native-masked-view/masked-view:** 0.3.1  
-- **@react-native-picker/picker:** 2.8.1  
-- **@react-navigation/native:** 6.1.18  
-- **react-native-device-info:** 13.0.0  
-- **react-native-gesture-handler:** 2.20.2  
-- **react-native-localize:** 3.2.1  
-- **react-native-pager-view:** 6.4.1  
-- **react-native-safe-area-context:** 4.11.0  
-- **react-native-svg:** 15.7.1  
-- **react-native-tab-view:** 3.5.2  
-- **react-native-vector-icons:** 10.2.0  
+* **@react-native-async-storage/async-storage:** 2.0.0  
+* **@react-native-community/datetimepicker:** 8.2.0  
+* **@react-native-masked-view/masked-view:** 0.3.1  
+* **@react-native-picker/picker:** 2.8.1  
+* **@react-navigation/native:** 6.1.18  
+* **react-native-device-info:** 13.0.0  
+* **react-native-gesture-handler:** 2.20.2  
+* **react-native-localize:** 3.2.1  
+* **react-native-pager-view:** 6.4.1  
+* **react-native-safe-area-context:** 4.11.0  
+* **react-native-svg:** 15.7.1  
+* **react-native-tab-view:** 3.5.2  
+* **react-native-vector-icons:** 10.2.0  
 
 ### Breaking Changes
 
diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-9-parent/nt-11-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-9-parent/nt-11-rn.md
@@ -33,4 +33,4 @@ If you are upgrading from Mendix versions below 10.17, please follow these steps
 1. Test your application:
     1. Thoroughly test your application to ensure that all features work as expected after the updates.
 
-For the most direct information on the Native Template, visit our [GitHub Releases page](https://github.com/mendix/native-template/releases/tag/v11.0.0).
+For the most direct information on the Native Template, visit our [GitHub Releases page](https://github.com/mendix/native-template/releases/tag/v11.0.0).
diff --git a/content/en/docs/releasenotes/private-platform/1.17.md b/content/en/docs/releasenotes/private-platform/1.17.md
@@ -47,4 +47,4 @@ We have provided the following fixes:
 * (Platform) We have fixed an issue where the **Build & Deploy** capability could not be enabled in the **Capabilities** menu.
 * (Platform) We have fixed an issue where SSO login using SAML would fail if the user account already existed in Private Mendix Platform.
 * (UI) We have resolved an issue with GitLab pagination in GitLab 17.5.2-ee.
-* (UI) We have resolved some pagination issues in the Chinese translation of Private Mendix Platform.
+* (UI) We have resolved some pagination issues in the Chinese translation of Private Mendix Platform.
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.12.md b/content/en/docs/releasenotes/studio-pro/10/10.12.md
@@ -55,7 +55,7 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 ### Known Issues
 
 * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
-  * Fixed in [10.18.0](/releasenotes/studio-pro/10.18/#fix-line-endings).
+    * Fixed in [10.18.0](/releasenotes/studio-pro/10.18/#fix-line-endings).
 * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.
 * There is a positioning error in the logic editors when you are dragging a large element, such as a loop, into a sequence flow, it overlaps with the existing elements.
 * Studio Pro on Mac loads user settings from the previous version of the application.
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.16.md b/content/en/docs/releasenotes/studio-pro/10/10.16.md
@@ -27,7 +27,7 @@ weight: 84
 * There is a positioning error in the logic editors when you are dragging a large element, such as a loop, into a sequence flow, it overlaps with the existing elements.
     * Fixed in [10.17.0](/releasenotes/studio-pro/10.17/#fix-positioning-error).
 * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
-  * Fixed in [10.18.0](/releasenotes/studio-pro/10.18/#fix-line-endings).
+    * Fixed in [10.18.0](/releasenotes/studio-pro/10.18/#fix-line-endings).
 
 ## 10.16.0 {#10160}
 
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.17.md b/content/en/docs/releasenotes/studio-pro/10/10.17.md
@@ -101,4 +101,4 @@ We added Japanese, Chinese, Korean, and German translations of the Studio Pro in
 ### Known Issues
 
 * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
-  * Fixed in [10.18.0](/releasenotes/studio-pro/10.18/#fix-line-endings).
+    * Fixed in [10.18.0](/releasenotes/studio-pro/10.18/#fix-line-endings).
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.18.md b/content/en/docs/releasenotes/studio-pro/10/10.18.md
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.6.md b/content/en/docs/releasenotes/studio-pro/10/10.6.md
diff --git a/content/en/docs/releasenotes/studio-pro/9/9.24.md b/content/en/docs/releasenotes/studio-pro/9/9.24.md

Original file line number	Diff line number	Diff line change
`@@ -247,4 +247,4 @@ When an item is selected in the search results pane, you can click the [Landscap`
`247`	`247`
`248`	`248`	`## Search using the API`
`249`	`249`
`250`		`-To use the Catalog Search API, see [Search API](/apidocs-mxsdk/apidocs/search-api/).`
	`250`	`+To use the Catalog Search API, see [Search API](/apidocs-mxsdk/apidocs/search-api/).`
Original file line number	Diff line number	Diff line change
`@@ -66,4 +66,4 @@ For information about security practices for app governance, refer to the follow`
`66`	`66`
`67`	`67`	`## Getting Support`
`68`	`68`
`69`		`-For additional information, frequently asked questions, and troubleshooting tis, refer to [Frequently Asked Questions – Security](/support/security-findings-faq/). If you have more questions, contact your Customer Success Manager (CSM), or join the [Mendix Community forum](https://community.mendix.com/p/community).`
	`69`	`+For additional information, frequently asked questions, and troubleshooting tis, refer to [Frequently Asked Questions – Security](/support/security-findings-faq/). If you have more questions, contact your Customer Success Manager (CSM), or join the [Mendix Community forum](https://community.mendix.com/p/community).`