[Auto] Lint docs #11586

[Auto] Lint docs

Author: OlufunkeMoronfolu

content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/pipeline-api-v2.md

@@ -26,4 +26,4 @@ For information about Pipeline API version 1, see [Pipeline API - Version 1](/ap
 
 ## API Reference
 
-{{< swaggerui src="/openapi-spec/openapi-pipeline-v2.yaml"  >}}
+{{< swaggerui src="/openapi-spec/openapi-pipeline-v2.yaml"  >}}

content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api-v2.md

@@ -32,4 +32,4 @@ For information about Project API version 1, see [Project API - Version 1](/apid
 
 ## API Reference
 
-{{< swaggerui src="/openapi-spec/openapi-project-v2.yaml"  >}}
+{{< swaggerui src="/openapi-spec/openapi-project-v2.yaml"  >}}

content/en/docs/apidocs-mxsdk/apidocs/private-mendix-platform/project-api.md

@@ -31,4 +31,4 @@ For information about Project API version 2, see [Project API - Version 2](/apid
 
 ## API Reference
 
-{{< swaggerui src="/openapi-spec/openapi-project-v1.yaml"  >}}
+{{< swaggerui src="/openapi-spec/openapi-project-v1.yaml"  >}}

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

@@ -279,7 +279,6 @@ export const component: IComponent = {
 };
 ```
 
-
 Replace your `src/model/PersonInfo.ts` file with the following:
 
 ```typescript {hl_lines=["6-10"]}
@@ -416,7 +415,6 @@ export const component: IComponent = {
 };
 ```
 
-
 Return `dependentElementIds` to tell Studio Pro which elements your document depends on. When those elements change, your checks rerun automatically.
 
 {{% alert color="info" %}}
@@ -487,7 +485,6 @@ async function checkDependencyWasChanged(dependencies: Dependency[], documents:
 
 By checking whether any of the changed documents from the event payload are included in your dependencies, you can trigger the consistency checks to run again by updating the content of your blob document using `studioPro.app.model.customBlobDocuments.updateDocumentContent`. This ensures your checks run again whenever one of your dependencies is modified in Studio Pro.
 
-
 ### Renamed Elements
 
 If one of your dependencies gets renamed, you may need to update the dependency names in your document. Studio Pro cannot automatically rename your dependencies; it can only notify you that the document matching the ID now has a new name. It is up to you to update your dependency's name.

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

@@ -90,6 +90,7 @@ export const component: IComponent = {
     }
 };
 ```
+
 The `permissionsChanged` event fires for all extensions whenever any permission is granted or revoked anywhere in the system, not just for your extension. This means multiple extensions may respond to the same event simultaneously.
 
 To check if a change affects your extension, compare the old granted state against the new one for each permission name your extension declared. Without this check, your extension fires a notification every time any permission changes, including changes unrelated to your extension.

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md

@@ -485,7 +485,7 @@ if (selection.type === "Single") {
 
 ## Exposed Modules
 
- ### Session {#session}
+### Session {#session}
 
 The Mendix Platform exposes a `mendix/session` module for inspecting the current user session. It is available in both web and native.
 

content/en/docs/catalog/_index.md

@@ -54,7 +54,6 @@ From the **Home** screen, you can do the following:
 
 The Catalog is also integrated in Mendix Studio Pro to find and connect to shared services in your apps. For further details on using Catalog in Studio Pro, see [Integration Pane](/refguide/integration-pane/) in the *Studio Pro Guide*.
 
-
 ## Information Available in the Catalog {#available-info}
 
 In the Catalog, all the information for registered assets is displayed in the [Catalog search details](/catalog/manage/search/#search-details) screen. This information comes from the metadata in the OData service contract, and also from additional metadata that is added when registered assets are curated. Registered assets can be curated by owners, [Curators](/catalog/manage/user-roles/#curator), and [Mendix Admins](/catalog/manage/user-roles/#admin).

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

@@ -10,4 +10,4 @@ no_list: false
 
 The **Maia** section allows you to manage, control, and monitor Maia resources and behavior on Mendix Portal.
 
-## Documents in This Category
+## Documents in This Category

content/en/docs/control-center/security/policies.md

@@ -43,41 +43,41 @@ You can create a policy by defining your own details.
 
 2. On the **Policy Definition** tab, fill in the following details:
 
-* **Policy Name** – A relevant name for your policy, such as one indicating what the policy checks.
-* **Description** – A description of the goal of the policy, which covers why it needs to be adhered to, and how to fix its violations.
-* **Policy Conditions** – Define the conditions under which the policy is considered violated. These are the available conditions and their values:
+    * **Policy Name** – A relevant name for your policy, such as one indicating what the policy checks.
+    * **Description** – A description of the goal of the policy, which covers why it needs to be adhered to, and how to fix its violations.
+    * **Policy Conditions** – Define the conditions under which the policy is considered violated. These are the available conditions and their values:
 
-    * **Any finding severity is** – Choose which severity level violates the policy. You can select one or more of the following values:
+        * **Any finding severity is** – Choose which severity level violates the policy. You can select one or more of the following values:
 
-        * **LOW**
-        * **MEDIUM**
-        * **HIGH**
-        * **CRITICAL**
+            * **LOW**
+            * **MEDIUM**
+            * **HIGH**
+            * **CRITICAL**
 
-        For example, if you select **CRITICAL**, apps with critical findings violate this policy.
+            For example, if you select **CRITICAL**, apps with critical findings violate this policy.
 
-    * **Mendix runtime version is lower than** – Indicate which Mendix version is the minimum that your apps must use.
+        * **Mendix runtime version is lower than** – Indicate which Mendix version is the minimum that your apps must use.
 
-    * **Marketplace component license is not** – Select the licenses that are acceptable. If a Marketplace component has a license which is not one of the ones you select here, the policy is violated. These are the possible values:
+        * **Marketplace component license is not** – Select the licenses that are acceptable. If a Marketplace component has a license which is not one of the ones you select here, the policy is violated. These are the possible values:
 
-        * MIT
-        * BSD_2_0
-        * APACHE_V2
-        * APACHE_1_0
-        * MENDIX_EULA
-        * PARTNER_LICENSES
-        * CREATIVE_COMMONS_CC0
-        * GNU_GENERAL_PUBLIC_LICENSE_V3
-        * MENDIX_MARKETPLACE_CONTENT_TERMS
+            * MIT
+            * BSD_2_0
+            * APACHE_V2
+            * APACHE_1_0
+            * MENDIX_EULA
+            * PARTNER_LICENSES
+            * CREATIVE_COMMONS_CC0
+            * GNU_GENERAL_PUBLIC_LICENSE_V3
+            * MENDIX_MARKETPLACE_CONTENT_TERMS
 
-    * **Marketplace component support is not** – Select the support types that are acceptable. If a Marketplace component has a support type which is not one of the ones you select here, the policy is violated. These are the possible values:
+        * **Marketplace component support is not** – Select the support types that are acceptable. If a Marketplace component has a support type which is not one of the ones you select here, the policy is violated. These are the possible values:
 
-        * PARTNER
-        * SIEMENS
-        * PLATFORM
-        * COMMUNITY
+            * PARTNER
+            * SIEMENS
+            * PLATFORM
+            * COMMUNITY
 
-* **Checkpoints & Action(s)** – Select the trigger which causes the policy to be checked, and the action that is taken if the policy is violated. Currently, policy violations are checked at the time of package creation, and violations generate warnings.
+    * **Checkpoints & Action(s)** – Select the trigger which causes the policy to be checked, and the action that is taken if the policy is violated. Currently, policy violations are checked at the time of package creation, and violations generate warnings.
 
 3. On the **Policy Scope** tab, select whether you want the policy to apply to all licensed apps, or only to specific apps in your environment.
 

content/en/docs/deployment/general/subscription-management/user-metering/implementing-user-metering.md

@@ -119,7 +119,6 @@ The improved user metering capabilities are introduced in Mendix 11. These capab
 | Multi-app user identification | `system.user.name` | `system.user.name` or `NamedUserIdentifier` in User Commons v2.2.0 and above |
 | SCIM-based user deactivation | SCIM v3.0.0 and above | SCIM v4.0.0 and above |
 
-
 ## Domain Model Entities {#domain-model-entities}
 
 This section explains the entities and their attributes in your application domain model that are relevant for user metering.