Merge pull request mendix#9126 from mendix/lint-docs

MarkvanMents · web-flow · commit e2f8d22d5ff3 · 2025-03-03T16:13:19.000+01:00
[Auto] Lint docs
diff --git a/content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/external-platforms/_index.md b/content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/external-platforms/_index.md
@@ -11,4 +11,4 @@ no_list: false
 
 The Mendix platform provides seamless integration with various external platforms through specialized connectors. These connectors enable you to extend the functionality of your applications by leveraging external services and data sources. This section introduces the connectors available for [Snowflake Cortex](/appstore/modules/genai/snowflake-cortex/), [OpenAI](/appstore/modules/genai/openai/), [Amazon Bedrock](/appstore/modules/genai/bedrock/), and [PGVector Knowledge Base](/appstore/modules/genai/pgvector/), providing a high-level overview of their capabilities.
 
-## Connectors
+## Connectors
diff --git a/content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/external-platforms/snowflake-cortex.md b/content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/external-platforms/snowflake-cortex.md
@@ -56,7 +56,6 @@ The [Snowflake showcase app](https://marketplace.mendix.com/link/component/22584
     3. Cortex LLM Functions
     4. Cortex Analyst
    
-
 3. To see how a Snowflake Cortex Analyst action is called, use the **Explorer** search box to find and open the *EXAMPLE_CortexAnalyst_GenerateResponseMessage** microflow.
 
    {{< figure src="/attachments/appstore/platform-supported-content/modules/snowflake-rest-sql/CortexAnalystRequestExample.png" >}}
diff --git a/content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix.md/genai-commons.md b/content/en/docs/appstore/use-content/platform-supported-content/modules/genai/reference-guide/genai-for-mendix.md/genai-commons.md
@@ -871,4 +871,4 @@ To check your JDK version and update it if necessary, follow these steps:
     1. You might get an error saying `FAILURE: Build failed with an exception. The supplied javaHome seems to be invalid. I cannot find the java executable.` In this case, verify that you have selected the correct JDK directory containing the updated JDK version.
     2. You may also need to update Gradle. To do this, go to **Edit** > **Preferences** > **Deployment** > **Gradle directory**. Click **Browse** and select the appropriate Gradle version from the Mendix folder. For Mendix 10.10 and above, use Gradle 8.5. For Mendix 10 versions below 10.10, use Gradle 7.6.3. Then save your settings by clicking **OK**.
     3. Rerun the project.
-    
+    
diff --git a/content/en/docs/appstore/use-content/platform-supported-content/modules/snowflake/mendix-data-loader.md b/content/en/docs/appstore/use-content/platform-supported-content/modules/snowflake/mendix-data-loader.md
@@ -188,6 +188,7 @@ ALTER ALERT <ALERT name> RESUME; -- The ALERT has STATE Suspended when created a
 
 SHOW ALERTS;
 ```
+
 ## Verifying the Access Token
 
 When using OAuth authentication with the Mendix Data Loader, it is crucial to verify the access token received by your Mendix application. This verification process ensures the token's authenticity and integrity, protecting your application from unauthorized access attempts.
diff --git a/content/en/docs/appstore/use-content/platform-supported-content/widgets/popup-menu.md b/content/en/docs/appstore/use-content/platform-supported-content/widgets/popup-menu.md
@@ -45,7 +45,7 @@ Other main properties of the widget are as follows:
 * **Menu position** – determines the location of a visible menu relative to the trigger area
     * Default: **Bottom**
 * **Clipping strategy** – determines the relative positioning of floating elements on the page. 
-    *   **Absolute** - positions the floating element relative to its nearest positioned ancestor.
-    *   **Fixed** - positions the floating element relative to the viewport. It breaks the element out of any clipping ancestor.
+    * **Absolute** - positions the floating element relative to its nearest positioned ancestor.
+    * **Fixed** - positions the floating element relative to the viewport. It breaks the element out of any clipping ancestor.
 
 If you want to use dynamic content, make sure to wrap the widget in a [data view](/refguide/data-view/) and set **Enable advanced options** to **Yes**.
diff --git a/content/en/docs/deployment/mx-azure/mx-azure-getting-started.md b/content/en/docs/deployment/mx-azure/mx-azure-getting-started.md
@@ -51,10 +51,11 @@ To adopt Mendix on Azure, you need to have the following:
      }
 }
 ```
+
 {{% /alert %}}
 
 ## Licensing
 
 Mendix on Azure is available for purchase from the the [Azure Marketplace](https://azuremarketplace.microsoft.com/). Connecting to Azure services may also include additional cost. For more information, refer to Azure documentation.
 
-For production environments, you also need a runtime license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/). The Operator license is applied automatically when using Mendix on Azure.
+For production environments, you also need a runtime license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/). The Operator license is applied automatically when using Mendix on Azure.
diff --git a/content/en/docs/deployment/mx-azure/mx-azure-installation.md b/content/en/docs/deployment/mx-azure/mx-azure-installation.md
@@ -71,7 +71,7 @@ If required, you can change the following options for your cluster:
 * VM type
 * Load balancer type
 * Postgres compute SKU
-*  Postgres performance tier for storage IOPS
+* Postgres performance tier for storage IOPS
 * Custom tags
 
 ## Enabling Connections Between Different Azure Resource Groups
diff --git a/content/en/docs/deployment/mx-azure/mx-azure-support.md b/content/en/docs/deployment/mx-azure/mx-azure-support.md
@@ -148,4 +148,4 @@ The solution is being benchmarked against SOC2 Azure Policy Compliance controls.
 ## Known Limitations
 
 * Mendix on Azure only supports hosting apps on Mendix versions 10.10 or later. Any app on an earlier version will fail to deploy successfully.
-* Due to the managed nature of this product, not all Private Cloud APIs are available to the customer. Refer to the Build and Deploy API documentation to find out which API calls are out of scope for Mendix on Azure.
+* Due to the managed nature of this product, not all Private Cloud APIs are available to the customer. Refer to the Build and Deploy API documentation to find out which API calls are out of scope for Mendix on Azure.
diff --git a/content/en/docs/deployment/private-cloud/secret-store-credentials.md b/content/en/docs/deployment/private-cloud/secret-store-credentials.md
@@ -801,7 +801,6 @@ After completing the prerequisites, follow these steps to switch from password-b
 3. Open the environment's Blob Storage Account Container in the Azure portal, and [assign a Storage Blob Data Contributor role](https://learn.microsoft.com/en-us/azure/storage/blobs/assign-azure-role-data-access) to the environment's managed identity.
 4. Restart the Mendix app environment.
 
-
 ### Configuring a Secret Store with Google Secret Manager {#google-secret-manager}
 
 To follow these instructions you will need:
@@ -969,7 +968,6 @@ To enable your environment to use [Google Secret Manager Provider](https://githu
 
 For more information, refer to the the official [Google Secret Manager Provider for Secret Store CSI Driver](https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp) repository and [Google Secret Manager documentation](https://cloud.google.com/secret-manager/docs/overview).
 
-
 ## Additional Considerations {#additional-considerations}
 
 When implementing a secret store, keep in mind the following considerations:
diff --git a/content/en/docs/developerportal/digital-execution/_index.md b/content/en/docs/developerportal/digital-execution/_index.md
@@ -12,4 +12,4 @@ The Mendix Digital Execution Practice is a method for executing on your digital
 
 ## Documents in This Category
  
-To help you implement your Mendix Digital Execution strategy, you can use the following tools:
+To help you implement your Mendix Digital Execution strategy, you can use the following tools:
diff --git a/content/en/docs/developerportal/digital-execution/portfolio-management/_index.md b/content/en/docs/developerportal/digital-execution/portfolio-management/_index.md
@@ -94,4 +94,4 @@ Clicking a menu item opens the corresponding page:
 * [Application Portfolio Management with Low-Code](https://www.mendix.com/application-portfolio-management/)
 * [Make Strategic Decisions with Portfolio Management](https://academy.mendix.com/link/paths/145/Make-Strategic-Decisions-With-Portfolio-Management)
 * [Why Portfolio Management is Crucial to App Development at Scale](https://www.mendix.com/blog/)
-* [Preparing to Launch your First Mendix App with Compass](/developerportal/compass/) - Another Digital Execution tool, geared towards planning and streamlining the implementation of your first Mendix app
+* [Preparing to Launch your First Mendix App with Compass](/developerportal/compass/) - Another Digital Execution tool, geared towards planning and streamlining the implementation of your first Mendix app
diff --git a/content/en/docs/howto/monitoring-troubleshooting/debug-java-actions/_index.md b/content/en/docs/howto/monitoring-troubleshooting/debug-java-actions/_index.md
@@ -61,9 +61,9 @@ Before starting this how-to, make sure you have completed the following prerequi
 ## Limitations
 
 There is the following limitation:
+
 * If there are add-on modules imported into Studio Pro and the application is deployed for Eclipse using menu option **App > Deploy for Eclipse**, there are known build failures in Java source code.
 
-  
 ## Read More
 
 * [Find the Root Cause of Runtime Errors](/howto/monitoring-troubleshooting/finding-the-root-cause-of-runtime-errors/)
diff --git a/content/en/docs/refguide/mobile/introduction-to-mobile-technologies/native-mobile.md b/content/en/docs/refguide/mobile/introduction-to-mobile-technologies/native-mobile.md
@@ -66,4 +66,3 @@ bitcode_strip_path = `xcrun --find bitcode_strip`.chop!
      strip_bitcode_from_framework(bitcode_strip_path, framework_relative_path)
    end
 ```
-
diff --git a/content/en/docs/refguide/modeling/domain-model/oql/oql-clauses.md b/content/en/docs/refguide/modeling/domain-model/oql/oql-clauses.md
@@ -1078,6 +1078,7 @@ The syntax is as follows:
 ### Result data type {#oql-union-type}
 
 The data types used in `select_query` statements are considered when determining the final return type of the `UNION` clause. All data types used in `select_query` statements must be compatible. All data types are compatible with themselves. Differing types are only compatible in these cases:
+
 * `UNION` of numeric types `INTEGER`, `LONG` and `DECIMAL`. The return type is the numeric type found in the `select_query` statements with the highest precedence (see [Type Precedence](/refguide/oql-expression-syntax/#type-coercion) for more information). 
 * `UNION` of limited and unlimited `STRING`. The return type is determined by the largest length of `STRING` attributes in the `select_query` statements.
 * `UNION` of any known type and a `NULL` literal. The result type is the known type.
diff --git a/content/en/docs/refguide/modeling/security/security-overview.md b/content/en/docs/refguide/modeling/security/security-overview.md
@@ -62,26 +62,28 @@ The **Nanoflow Access** tab lists the names of nanoflows within the selected mod
 To export the **Security Overview**, click the **Export to Excel** button. This generates an Excel file in the selected directory, which contains the following three sheets:
 
 1. Entity Access -- This sheet contains the entity access rules data, including the following:
-    a. User Role
-    b. Module: The module containing the entity.
-    c. Entity: The name of the entity.
-    d. Member: The attribute or association name.
-    e. Kind: Specifies whether the member is an association or an attribute.
-    f. Type: The type of the member.
-    g. XPath: The XPath constraint.
-    h. XPath Caption:  The XPath constraint caption, when set.
-    i. Access: The access level (None, Read or ReadWrite).
+
+    1. User Role.
+    2. Module: The module containing the entity.
+    3. Entity: The name of the entity.
+    4. Member: The attribute or association name.
+    5. Kind: Specifies whether the member is an association or an attribute.
+    6. Type: The type of the member.
+    7. XPath: The XPath constraint.
+    8. XPath Caption:  The XPath constraint caption, when set.
+    9. Access: The access level (None, Read or ReadWrite).
 
 2. Document Access -- This sheet includes the accessible pages, microflows and nanoflows, including the following:
-	a. Document type -- The type of the accessible document (page, microflow, nanoflow).
-	b. User Role
-	c. Module: The module containing the the page, nanoflow, or microflow.
-	d. Document: The name of the page, nanoflow, or microflow.
-
-3. Module Roles -- this sheet provides the mappings between user roles and module roles, including the following:
-	a. User Role
-	b. Module
-	c. Module Role.
+
+    1. Document type -- The type of the accessible document (page, microflow, nanoflow).
+    2. User Role.
+    3. Module: The module containing the the page, nanoflow, or microflow.
+    4. Document: The name of the page, nanoflow, or microflow.
+
+4. Module Roles -- this sheet provides the mappings between user roles and module roles, including the following:
+    1. User Role.
+    2. Module.
+    3. Module Role.
 
 ## Read More
 
diff --git a/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/_index.md b/content/en/docs/refguide/version-control/using-version-control-in-studio-pro/_index.md
@@ -225,6 +225,7 @@ Select the **Version Control** menu > **Revert a Commit...** to revert a commit.
 
 {{% alert color="warning" %}}
 Reverting a commit creates a new commit that undoes the changes introduced by the original commit. This may lead to unexpected results depending on the context of the original commit.
+
 * **Port fix and reverting** – If you used [Port Fix](/refguide/merge-dialog/#port-fix) to apply a commit from another branch to the current branch, and then you revert that commit, the changes from the cherry-pick will not be reapplied when merging the full branch. This happens because the revert commit explicitly negates the cherry-picked changes, and Git recognizes them as already addressed.
 * **Merging and reverting** – If you [merged another branch](/refguide/version-control/#merging-branches) into the current branch and then reverted the merge commit, merging the same branch again will not reapply its changes. Git identifies that the merge was undone and prevents those changes from being reapplied.
 {{% /alert %}}
diff --git a/content/en/docs/releasenotes/digital-execution/_index.md b/content/en/docs/releasenotes/digital-execution/_index.md
@@ -200,4 +200,4 @@ In Portfolio Management, you can do the following:
 * Archive and restore project initiatives
 * Invite users to dedicated portfolio boards (both internal to your organization and external)
 * Easily manage portfolio users via **Access Management**
-* Get notified when you get assigned to a project initiative or someone commented on a project initiative you own
+* Get notified when you get assigned to a project initiative or someone commented on a project initiative you own
diff --git a/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md b/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md
@@ -33,6 +33,7 @@ We are in the process of fixing the signing certificate. Until this is resolved,
 
 {{% alert color="info" %}}
 **Windows Security Note**: If Windows security policies prevent you from accomplishing the above, do the following:
+
 1. Right-click the installer.
 1. Click **Properties**.
 1. Select **Unblock**.
diff --git a/content/en/docs/releasenotes/sdk/metamodel/metamodel-10/metamodel-10.20.md b/content/en/docs/releasenotes/sdk/metamodel/metamodel-10/metamodel-10.20.md
@@ -43,4 +43,3 @@ weight: 80
 #### LinearRecurrence (Element)
 
 * We introduced this element. 
-
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.12.md b/content/en/docs/releasenotes/studio-pro/10/10.12.md
@@ -18,10 +18,10 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 
 ### Fixes
 
-- We decreased the chance for database transaction deadlocks when updating the **LastActive** attribute for System.Session instances. (Ticket 240094)
+* We decreased the chance for database transaction deadlocks when updating the **LastActive** attribute for System.Session instances. (Ticket 240094)
 
-- We fixed an issue where attempting to convert nanoflow or microflow in the System module resulted in an error. This option is now disabled for the System module.
-- We fixed an issue with updating module roles in the **Module Security** dialog box that occurred after moving a document between modules.
+* We fixed an issue where attempting to convert nanoflow or microflow in the System module resulted in an error. This option is now disabled for the System module.
+* We fixed an issue with updating module roles in the **Module Security** dialog box that occurred after moving a document between modules.
 
 ## 10.12.14 {#101214}
 
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.20.md b/content/en/docs/releasenotes/studio-pro/10/10.20.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
`@@ -11,4 +11,4 @@ no_list: false`
`11`	`11`
`12`	`12`	The Mendix platform provides seamless integration with various external platforms through specialized connectors. These connectors enable you to extend the functionality of your applications by leveraging external services and data sources. This section introduces the connectors available for [Snowflake Cortex](/appstore/modules/genai/snowflake-cortex/), [OpenAI](/appstore/modules/genai/openai/), [Amazon Bedrock](/appstore/modules/genai/bedrock/), and [PGVector Knowledge Base](/appstore/modules/genai/pgvector/), providing a high-level overview of their capabilities.
`13`	`13`
`14`		`-## Connectors`
	`14`	`+## Connectors`
Original file line number	Diff line number	Diff line change
`@@ -51,10 +51,11 @@ To adopt Mendix on Azure, you need to have the following:`
`51`	`51`	`}`
`52`	`52`	`}`
`53`	`53`	```
	`54`	`+`
`54`	`55`	`{{% /alert %}}`
`55`	`56`
`56`	`57`	`## Licensing`
`57`	`58`
`58`	`59`	`Mendix on Azure is available for purchase from the the [Azure Marketplace](https://azuremarketplace.microsoft.com/). Connecting to Azure services may also include additional cost. For more information, refer to Azure documentation.`
`59`	`60`
`60`		`-For production environments, you also need a runtime license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/). The Operator license is applied automatically when using Mendix on Azure.`
	`61`	`+For production environments, you also need a runtime license for your Mendix app. For more information, refer to [Licensing Apps](/developerportal/deploy/licensing-apps-outside-mxcloud/). The Operator license is applied automatically when using Mendix on Azure.`
Original file line number	Diff line number	Diff line change
`@@ -12,4 +12,4 @@ The Mendix Digital Execution Practice is a method for executing on your digital`
`12`	`12`
`13`	`13`	`## Documents in This Category`
`14`	`14`
`15`		`-To help you implement your Mendix Digital Execution strategy, you can use the following tools:`
	`15`	`+To help you implement your Mendix Digital Execution strategy, you can use the following tools:`