[Auto] Lint docs

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/element-selector-api.md

@@ -281,7 +281,6 @@ The optional query parameter allows you to filter selector results:
 | `name` | `string` | Filter by name | Documents, Entities |
 | `sdkName` | `string` | Filter by SDK name (for example, `Pages$Page`) | Documents only |
 
-
 ## Preselecting Elements
 
 You can also pass an element ID as the `selectedElementId` property of the `Selector`. This ID can be either a Document, an Entity, or a Module. If a document or entity, the corresponding node on the selector form appears selected. If the ID belongs to a module, the corresponding node appears selected and  expanded, and the `New` button is enabled so the user can immediately create a new document in that module.

content/en/docs/control-center/apps/apps-overview.md

@@ -64,9 +64,10 @@ When you select apps using the checkboxes in the table, a context menu appears a
 Clicking an app name in a tab or the search results opens its details page, which includes the following tabs:
 
 * **App Info** – Shows the **Description** and **App ID**, also found in your app's [Settings](/developerportal/general-settings/).
-* **Members** – Lists the team members in the app development team.
-    * You can directly deactivate a team member from the app by clicking their name and selecting **Deactivate Member**.
-    * For other member management options, click **Manage Members**, which will open the [Team](/developerportal/general/team/#managing) page of the app.
+* **Members** – Lists the team members in the project development team.    
+    You can directly deactivate a team member from the project by clicking their name and selecting **Deactivate Member**.    
+    For other member management options, click **Manage Members**, which will open the [Team](/developerportal/general/team/#managing) page of the project.    
+    {{% alert color="info" %}}Mendix Admins cannot add or remove themselves from a project.{{% /alert %}}
 * **Environments** – Lists all Mendix Cloud environments. For the free Mendix Cloud environment, you can delete the environment on this tab. Once the free environment is deleted, all data will be removed. However, the app team members can still access the associated app repository in the Mendix Portal.
 
 If the app is not a licensed app, you can see the action menu ({{% icon name="three-dots-menu-horizontal" %}}) on the upper-right corner of the page. If the app is active, then you have the options to deactivate the app and delete the app; and if the app is deactivated, then you have the options to activate the app and delete the app.

content/en/docs/control-center/company/mendix-admins.md

@@ -17,7 +17,7 @@ To remove an admin, hover over their name in the list, then click **Remove**.
 {{< figure src="/attachments/control-center/company/mendix-admins/mendix-admins.png" >}}
 
 {{% alert color="info" %}}
-It is not possible to remove yourself as a Mendix Admin.
+It is not possible to add or remove yourself as a Mendix Admin.
 {{% /alert %}}
 
 If the **Add Mendix Admin** button is not displayed, your company is using a user group in your IdP to assign Mendix Admins. For more information, refer to [IdP-managed Mendix Admins](/control-center/security-settings/#idp-managed-mendix-admins).

content/en/docs/control-center/maia/maia-resources.md

@@ -97,4 +97,4 @@ To deprovision, select a plan of type **Provisioned** from your resources overvi
 
 {{% alert color="info" %}}
 Your subscription plan operates on a monthly bundle cycle. When you deprovision a resource, the deprovisioning takes effect at the end of the current subscription month. Until that date, you can still use the resource and status in the overview reads **Plan Deprovision Scheduled**.
-{{% /alert %}}
+{{% /alert %}}

content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md

@@ -29,7 +29,6 @@ Previous versions of the Operator did not manage `PodDisruptionBudgets`. Instead
 If you have manually created a `PodDisruptionBudget` for an app, delete it and instead specify the `PodDisruptionBudget` parameters [in the MendixApp CR](#pod-disruption-budget).
 {{% /alert %}}
 
-
 {{% alert color="info" %}}
 Mendix Operator 2.28.0 specifies `unhealthyPodEvictionPolicy: AlwaysAllow` in the `PodDisruptionBudget`, allowing Kubernetes to evict crashlooping or unavailable pods without applying rules from the `PodDisruptionBudget`.
 

content/en/docs/marketplace/platform-supported-content/modules/advanced-audit-trail/_index.md

@@ -250,4 +250,4 @@ The search functionality supports both exact matches and flexible filtering base
 
 * [Consuming Add-on Modules and Solutions](/refguide/consume-add-on-modules-and-solutions/)
 * [Audit Trail](/appstore/modules/audit-trail/)
-* [Scheduled Events](/refguide/scheduled-events/)
+* [Scheduled Events](/refguide/scheduled-events/)

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

@@ -70,4 +70,4 @@ To set up your own implementation, perform the following steps:
 1. Create a new `CortexAgentDeployedModel` on the **CortexAgentDeployedModel_Overview** page by providing the required Agent configuration details.
 2. Wire the created `CortexAgentDeployedModel` to the Conversational UI by using `CortexAgent_ProviderConfig_GetCreate` to create or retrieve the associated `ProviderConfig`.
 
-The ProviderConfig is then used by the Conversational UI to drive the chat interface, routing messages through `ChatCompletions_CallCortexAgent` and maintaining conversation continuity through the `Conversation` entity.
+The ProviderConfig is then used by the Conversational UI to drive the chat interface, routing messages through `ChatCompletions_CallCortexAgent` and maintaining conversation continuity through the `Conversation` entity.

content/en/docs/marketplace/platform-supported-content/services/event-broker.md

@@ -159,7 +159,6 @@ Technical Contacts with a license to the Mendix Event Broker can manage this fea
     * For instructions on configuring AWS S3, see [Configuring a Bridge with AWS S3](#bridge-with-aws-s3).
     * For instructions on configuring Iceberg, see [Configuring a Bridge with Iceberg](#bridge-with-iceberg).
 
-
 4. After configuring the service and connecting events (as described in the bridge-specific sections above), click **Start** on the confirmation screen to deploy the bridge.
 
     {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/ebb_general_bridge_start.png" >}}
@@ -553,7 +552,6 @@ To edit a bridge:
         **Iceberg**
         {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/edit-bridge/ebb_iceberg_edit_mode.png" class="no-border" >}}
 
-
 4. Once you have made your changes, you can:
     * Click **Apply** to save and apply the changes. A confirmation message will indicate if the changes were successful. Changes to the event configuration take effect when applied. After applying changes, the bridge status will change to **Reconfiguring** and will return to **Running** for HTTP, Azure Blob Storage, and AWS S3 bridges, or **Delivering** for Iceberg bridges, once the reconfiguration is complete.
    * Click **Cancel** to exit editing mode without saving any changes.
@@ -683,4 +681,4 @@ The supported version of AsyncAPI is 2.0.0, in accordance with [AsyncAPI documen
 The file requirements are listed below:
 
 * Size: maximum file size is 1MB.
-* Supported files: *.yml*, *.yaml*, *.json*
+* Supported files: *.yml*, *.yaml*, *.json*

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

@@ -342,5 +342,6 @@ Rich Text version 4 still has limitations that we will continue improving in the
     * Table caption
 
 Rich Text version 5 offers "class" styling to allow Rich Text to works in a strict CSP environment. This  has limitations that we will continue to improve in the future. Current notable limitations are as follows:
+
 * Resizing image, video, and tables does not work properly
 * Switching format from inline to class causes partial data loss on styling

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

@@ -236,6 +236,7 @@ Blob storage isolation is enforced through cloud IAM. The Infra. Operator is res
 | Azure Blob | Separate container, managed identity auth |
 
 For more information, see the following topics:
+
 * [Published REST Services](/refguide/published-rest-services/)
 * [App Security](/refguide/security/)
 
@@ -253,4 +254,4 @@ Each environment accesses its database through unique credentials scoped exclusi
 
 The following screenshot shows the database and file storage instance for each deployed app:
 
-{{< figure src="/attachments/private-platform/nist-ac/nist-ac-04-3.png" class="no-border" >}}
+{{< figure src="/attachments/private-platform/nist-ac/nist-ac-04-3.png" class="no-border" >}}

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

@@ -53,4 +53,4 @@ For more information, refer to the following topics:
 
 As a Mendix application, Private Mendix Platform follows the principle of Least Privilege. In the  Private Mendix Platform project's security settings, all user roles for the *User* and *Anonymous* roles are unchecked, preventing non-privileged users from gaining escalated access.
 
-{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0610-1.png" class="no-border" >}}
+{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0610-1.png" class="no-border" >}}

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

@@ -69,7 +69,7 @@ The following is a recommended implementation pattern and flow:
 
     1. When absolute timeout is reached, block further interaction with protected pages.
     2. Redirect users to the login flow or a dedicated re-authentication page, and require valid authentication before access is restored.
-   3. Log session-expiration lock events (and optional warning acknowledgements) in application audit logs when required by policy.
+    3. Log session-expiration lock events (and optional warning acknowledgements) in application audit logs when required by policy.
 
 {{< figure src="/attachments/private-platform/nist-ac/nist-ac-11-2.png" class="no-border" >}}
 
@@ -95,4 +95,4 @@ To access the configuration page, in Private Mendix Platform, go to **Admin > Se
 
 The Private Mendix Platform session timeout configuration applies only to Private Mendix Platform sessions and does not control sessions inside customer-hosted Mendix applications. If customers require equivalent AC-11-compliant behavior in their own applications, they must implement the full session-expiration and re-authentication flow independently within the app, as discussed above.
 
-For more details on how to properly configure and implement inactive session locks for individual Mendix applications, see [Session Management](/refguide/session-management/).
+For more details on how to properly configure and implement inactive session locks for individual Mendix applications, see [Session Management](/refguide/session-management/).

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

@@ -40,7 +40,7 @@ The following controls are related to this control:
 * [AC-20](/private-mendix-platform/nist-controls/ac-20/)
 * CA-03
 * [CA-07](/private-mendix-platform/nist-controls/ca-07/)
-* * CM-08
+* CM-08
 * IA-02
 * IA-03
 * [IA-08](/private-mendix-platform/nist-controls/ia-08/)

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

@@ -35,7 +35,7 @@ The following controls are related to this control:
 * [AC-19](/private-mendix-platform/nist-controls/ac-19/)
 * CA-03
 * [CA-07](/private-mendix-platform/nist-controls/ca-07/)
-* * CM-08
+* CM-08
 * IA-02
 * IA-03
 * [IA-08](/private-mendix-platform/nist-controls/ia-08/)

content/en/docs/private-platform/nist-controls/au/pmp-nist-au02.md

@@ -110,4 +110,4 @@ Private Mendix Platform displays logs with the time unit setting (for example, *
 When building Mendix applications, the App Implementer and Operator can generate and configure audit logging through the Mendix logging functionality. For more information, see the following documents:
 
 * [Logging](/refguide/logging/)
-* [Log Message](/refguide/log-message/)
+* [Log Message](/refguide/log-message/)

content/en/docs/private-platform/nist-controls/au/pmp-nist-au12.md

@@ -222,4 +222,4 @@ Private Mendix Platform's compliance with AU-12 currently has the following gaps
 
     Audit logging for customer-developed Mendix apps is the responsibility of the customer and app Implementer using the Mendix Audit Trail module or custom instrumentation. Private Mendix Platform does not provide or aggregate application-layer events.
 
-The above evidence demonstrates that Private Mendix Platform satisfies a partial platform-scoped subset of AU-12 requirements. Full compliance requires coordinated implementation across Infra Implementer (infrastructure logs), and App Implementer along with the customer organization (application-level audit records).
+The above evidence demonstrates that Private Mendix Platform satisfies a partial platform-scoped subset of AU-12 requirements. Full compliance requires coordinated implementation across Infra Implementer (infrastructure logs), and App Implementer along with the customer organization (application-level audit records).

content/en/docs/private-platform/nist-controls/au/pmp-nist-au1201.md

@@ -164,4 +164,4 @@ Private Mendix Platform provides the platform-layer contribution to AU-12 (01) a
 * The Infra Implementer must produce and forward infrastructure logs.
 * The App Implementer and customer must generate and forward application-level audit logs.
 
-With those integrations in place, IL4 AU-12 (01) can be met end-to-end across platform, infrastructure, and application components.
+With those integrations in place, IL4 AU-12 (01) can be met end-to-end across platform, infrastructure, and application components.

content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0306.md

@@ -154,4 +154,4 @@ Private Mendix Platform currently supports using AWS Secret Manager, Azure Key V
 
 ### Building Custom Mendix Applications
 
-When the App Implementer needs to leverage custom encryption, they can do so in a compliant manner by using the [Mendix Encryption Module](/appstore/modules/encryption/). The module allows leveraging the configuration management processes, policies, and systems dictated by the customer.
+When the App Implementer needs to leverage custom encryption, they can do so in a compliant manner by using the [Mendix Encryption Module](/appstore/modules/encryption/). The module allows leveraging the configuration management processes, policies, and systems dictated by the customer.

content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0501.md

@@ -168,4 +168,4 @@ If a user tries to access pages or feature that they do no have access to, they
 
 Activities like deployments or using the admin tools are logged:
 
-{{< figure src="/attachments/private-platform/nist-cm/nist-cm-0501-5.png" class="no-border" >}}
+{{< figure src="/attachments/private-platform/nist-cm/nist-cm-0501-5.png" class="no-border" >}}

content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm0702.md

@@ -24,7 +24,7 @@ The information system prevents program execution in accordance with one or more
 
 The following controls are related to this control:
 
-* * CM-08
+* CM-08
 * PM-05
 
 ## Responsibility

content/en/docs/private-platform/nist-controls/cm/pmp-nist-cm08.md

@@ -19,6 +19,7 @@ This document describes how Private Mendix Platform fulfills the CM-08 control.
 ## Control
 
 The organization:
+
 * Develops and documents an inventory of information system components that:
 
     * Accurately reflects the current information system.
@@ -35,6 +36,7 @@ Organizations may choose to implement centralized information system component i
 Information deemed necessary for effective accountability of information system components includes, for example, hardware inventory specifications, software license information, software version numbers, component owners, and for networked components or devices, machine names and network addresses. Inventory specifications include, for example, manufacturer, device type, model, serial number, and physical location.
 
 The following controls are related to this control:
+
 * CM-02
 * [CM-06](/private-mendix-platform/nist-controls/cm-06/)
 * PM-05
@@ -156,4 +158,4 @@ For more information, refer to the following:
 * [Private Mendix Platform Release Notes](/releasenotes/private-platform/)
 * [SBOM Generation](/refguide/sbom-generation/)
 
-{{< figure src="/attachments/private-platform/nist-cm/nist-cm-08-1.png" class="no-border" >}}
+{{< figure src="/attachments/private-platform/nist-cm/nist-cm-08-1.png" class="no-border" >}}

content/en/docs/private-platform/nist-controls/ma/pmp-nist-ma06.md

@@ -26,7 +26,7 @@ Organizations specify the information system components that result in increased
 
 The following controls are related to this control:
 
-* * CM-08
+* CM-08
 * [CP-02](/private-mendix-platform/nist-controls/cp-02/)
 * CP-07
 * SA-14

content/en/docs/private-platform/nist-controls/ra/pmp-nist-ra02.md

@@ -30,7 +30,7 @@ Clearly defined authorization boundaries are a prerequisite for effective securi
 
 The following controls are related to this control:
 
-* * CM-08
+* CM-08
 * [MP-04](/private-mendix-platform/nist-controls/mp-04/)
 * [RA-03](/private-mendix-platform/nist-controls/ra-03/)
 * SC-07

content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa08.md

@@ -82,4 +82,4 @@ Mendix applies security engineering principles in the design and development of
 
     * [What is Amazon EC2 Auto Scaling? - Amazon EC2 Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html) 
     * [Use an instance refresh to update instances in an Auto Scaling group - Amazon EC2 Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-instance-refresh.html)
-    * [Terraform Registry](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group)
+    * [Terraform Registry](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group)

content/en/docs/private-platform/nist-controls/sa/pmp-nist-sa12.md

@@ -34,7 +34,7 @@ Organizations use the acquisition/procurement processes to require supply chain
 The following controls are related to this control:
 
 * AT-03
-* * CM-08
+* CM-08
 * IR-04
 * PE-16
 * [PL-08](/private-mendix-platform/nist-controls/pl-08/)

content/en/docs/private-platform/quickstart/_index.md

@@ -87,5 +87,3 @@ Before starting the installation process, make sure that you have all the necess
 * If you plan to use Azure Key Vault, see [Configuring a Secret Store with Azure Key Vault](/developerportal/deploy/secret-store-credentials/#azure-key-vault).
 
 ## Read More
-
-