[Auto] Lint docs (#11282)

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

* lint fixing after github action run

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Olufunke Moronfolu <olufunke.moronfolu@mendix.com>

Author: github-actions[bot]

content/en/docs/apidocs-mxsdk/apidocs/audit-logs-api.md

@@ -34,4 +34,4 @@ Two types of Authorization headers are supported: `Bearer` (Client credentials o
 
 The following API reference includes information on which scope and token type is required for each endpoint.
 
-{{< swaggerui src="/openapi-spec/audit-logging-v1.yaml"  >}}
+{{< swaggerui src="/openapi-spec/audit-logging-v1.yaml"  >}}

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

@@ -482,7 +482,6 @@ Then the Studio Pro UI for the property appears like this:
 
 ### Action {#action}
 
-
 The action property type allows a user to configure an action which can do things like call nanoflows, save changes, and open pages.
 
 If a `dataSource` attribute is not specified, the client will receive an `ActionValue` representing the action or `undefined` if the **Do nothing** action was selected.
@@ -838,7 +837,6 @@ The [`action`](#action), [`attribute`](#attribute), [`association`](#association
 
 ### Selection {#selection}
 
-
 The selection property allows a widget to read and set a selection that can be used in actions, expressions, or a `Listen to` data source of a data view.
 
 #### XML Attributes
@@ -909,7 +907,6 @@ Label property allows a pluggable widget to have labeling functionality similar
 
 #### setLabel {#setLabel}
 
-
 You can use `setLabel` to specify which properties can be used to set the `Label` property value. 
 
 Configuring the value of a property with the `setLabel` attribute will automatically update the value of `Label`.

content/en/docs/deployment/mx-azure/mx-azure-cluster-visibility.md

@@ -16,8 +16,8 @@ Below is a short summary of the key aspects of cluster visibility. For more info
 * Visibility - All cluster namespace members can view initialized clusters to facilitate support and monitoring.
 * Security - Only Cluster Managers with appropriate Azure RBAC roles (Owner or Contributor) can modify cluster settings.
 * Separation of Concerns: 
-  * Initialized clusters are visible to all namespace members regardless of Azure RBAC.
-  * Editing capabilities require both Cluster Manager role or Azure Owner or Contributor permissions.
+    * Initialized clusters are visible to all namespace members regardless of Azure RBAC.
+    * Editing capabilities require both Cluster Manager role or Azure Owner or Contributor permissions.
 
 ## Cluster Visibility
 

content/en/docs/deployment/on-premises-design/cloud-foundry/cloud-foundry-deploy-pad.md

@@ -71,4 +71,5 @@ To deploy your app to Cloud Foundry, perform the following steps:
        ``` 
 
 5. Run the `cf push` command.
+
 6. Verify that the Mendix app has started successfully.

content/en/docs/marketplace/genai/reference-guide/agent-editor.md

@@ -225,6 +225,7 @@ If a call fails during testing, a generic error message is shown in the Agent Ed
 ### Including the Agent in the App Logic {#call-agent}
 
 Include an agent in the app logic by calling it from a microflow. Agent Editor provides **Call Agent** toolbox actions in the **Agent Editor** category:
+
 * **Call Agent without History** focuses on single-call, task-style execution
 * **Call Agent with History** supports conversational scenarios with multiple messages
 

content/en/docs/marketplace/platform-supported-content/modules/excel-exporter.md

@@ -57,10 +57,10 @@ On the template details page, you can define the template with the following ite
     {{% alert color="info" %}}If you use an uploaded Excel file as a template, the names of the sheets and columns in your template will be used. However, the background color in your template will be overruled by the **Background color** (including **none**) specified in the applicable style. {{% /alert %}}
 
 * **Sanitize formulas to text**: When enabled, the module automatically sanitizes any string values that begin with potentially dangerous characters:
-  - `=` (equals)
-  - `+` (plus)
-  - `-` (minus/hyphen)
-  - `@` (at)
+    * `=` (equals)
+    * `+` (plus)
+    * `-` (minus/hyphen)
+    * `@` (at)
 
     {{% alert color="info" %}} When sanitization is enabled, the exporter prepends a apostrophe (`'`) to any string value starting with these
   characters. This forces Excel and CSV applications to treat the value as literal text rather than a formula.

content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp-byo.md

@@ -38,27 +38,25 @@ Because Snowflake conforms to the API specification of OpenAI, you can use the O
     1. Click **New**.
     2. Enter an identifying name.
     3. For API type, select **OpenAI**.
-    4. For **Endpoint**, enter your Snowflake account URL with the `/api/v2/cortex/v1/` suffix. 
-    
-    For example, the URL may look like the following: `https:/<snowflake_accountname>.snowflakecomputing.com/api/v2/cortex/v1/`.
+    4. For **Endpoint**, enter your Snowflake account URL with the `/api/v2/cortex/v1/` suffix. For example, the URL may look like the following: `https:/<snowflake_accountname>.snowflakecomputing.com/api/v2/cortex/v1/`.
 
     5. Save your changes.
 
-    {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/save-changes.png" >}}
+        {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/save-changes.png" >}}
 
 2. Add a Large Language Model by performing the following steps:
 
     1. Hover over the **three dots** icon and select **Manage deployed models** from the pop-up menu.
 
-    {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/manage-deployed-models.png" >}}
+        {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/manage-deployed-models.png" >}}
 
     2. Click **Add new model** to add an LLM from the [list of available LLMs](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api#model-availability) in your Snowflake account.
 
-    {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/new-deployed-model.png" >}}
+        {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/new-deployed-model.png" >}}
 
-    Alternatively, you can log into your Snowflake account with Snowsight and select **AI & ML > AI Studio > Cortex Playground**. The list in the top middle of the screen lists all available models.
-    
-    The **Model name** field in the Deployed Model configuration in Mendix must match exactly with the model name in Snowflake.
+        Alternatively, you can log into your Snowflake account with Snowsight and select **AI & ML > AI Studio > Cortex Playground**. The list in the top middle of the screen lists all available models.
+        
+        The **Model name** field in the Deployed Model configuration in Mendix must match exactly with the model name in Snowflake.
 
     3. Complete the configuration for your model.
     4. Save your changes.
@@ -67,9 +65,9 @@ Because Snowflake conforms to the API specification of OpenAI, you can use the O
 
     1. Hover over the **three dots** icon and select **Test** from the pop-up menu.
 
-    {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/test-option.png" >}}
+        {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/test-option.png" >}}
 
     2. Select your deployed model from the drop-down list.
     3. Click **Test**.
 
-    {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/test.png" >}}
+        {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-byok/test.png" >}}

content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp.md

@@ -410,10 +410,9 @@ After setting up the MCP server, you can now create a Mendix AI agent and connec
 8. On the **Consumed MCP Services** page, click **MCP Client** and configure the following properties of your Snowflake MCP server:
     
     1. Enter a name.
-    2. Specify the MCP endpoint in the following format: `https://<snoflake-account-id>.snowflakecomputing.com/api/v2/databases/<database name>/schemas/<schema name>/mcp-servers/<mcpserver name> `
+    2. Specify the MCP endpoint in the following format: `https://<snoflake-account-id>.snowflakecomputing.com/api/v2/databases/<database name>/schemas/<schema name>/mcp-servers/<mcpserver name>`.
         
-        {{% alert color="info" %}}
-        If your Snowflake account ID contains underscores (`_`), replace them with `-` in the endpoint. This is only required for the account ID, not for the database name, schema name, or MCP server name.
+        {{% alert color="info" %}} If your Snowflake account ID contains underscores (`_`), replace them with `-` in the endpoint. This is only required for the account ID, not for the database name, schema name, or MCP server name.
         {{% /alert %}}
         
     3. For the protocol value, enter *v2025_03_26*.
@@ -472,4 +471,4 @@ The primary table is SNOWFLAKE_MCP_DEMO.TESTDATA.TICKETS:
 - Always confirm successful operations by showing the user what was created or retrieved.
 - Use fully qualified table names (DATABASE.SCHEMA.TABLE) in all tool calls.
 - If a tool call returns an error, explain the issue clearly and suggest a correction.
-```
+```

content/en/docs/private-platform/nist-controls/_index.md

@@ -15,4 +15,3 @@ Documents in this section provide more information about Private Mendix Platform
 In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below.
 
 ## Control Categories
-

content/en/docs/private-platform/nist-controls/ac/_index.md

@@ -12,4 +12,4 @@ simple_list: true
 
 Documents in this section provide more information about Private Mendix Platform's compliance with the Access Control (AC) category of the [NIST 800-53](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) security framework. For each applicable control, we have listed which party (Mendix or the customer) is responsible for which component or aspect.
 
-In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below.
+In general, Mendix is responsible for the Private Mendix Platform, Mendix Operator, Mendix Studio Pro, Mendix Runtime, and so on. Customer responsibilities are related to infra and organization processes. For more information, refer to detailed documentation below.