[Auto] Lint docs

content/en/docs/control-center/security/private-connectivity/configure-private-connectivity.md

@@ -40,8 +40,8 @@ On the **Networks** tab of the **Private Connectivity** page, you can see all th
 
     * **Details**    
     <!-- * **Add DNS** -->
-	* **Add Agent**
-	<!-- * **Edit**
+    * **Add Agent**
+    <!-- * **Edit**
 	* **Delete** -->
 
 ### Adding a Network {#private-connectivity-networks-add}
@@ -71,7 +71,7 @@ To view and edit an existing network, follow these steps:
     * **Network** – The name you gave to the network. This field is editable.
     * **Network ID** – The internal ID of your network. You can copy this if, for example, you want to provide it in a support ticket for any issues with the network.
     * **External Agents** – A list of all external agents that run on your own internal infrastructure, and that have access to the network.    
-	  This field also displays the status of each agent.
+      This field also displays the status of each agent.
     <!-- * **DNS Details** – A list of domains for which you have [configured DNS](#private-connectivity-networks-dns). -->
     * **Environment Details** – A list of app environments that are using the network to connect to a resource, as well as the environment's status.
     <!-- * **Show Logs** – This allows you to see [the flow logs](https://tailscale.com/kb/1219/network-flow-logs) for your network. They can help you troubleshoot issues with connectivity on your network. -->
@@ -306,7 +306,7 @@ The page displays the following information for each resource:
 * **Status** – The status of the resource. This can be one of the following:
 
     * Enabled – Technical Contacts can request connections to the resource.
-	* Disabled – Technical Contacts cannot request connections to the resource.
+    * Disabled – Technical Contacts cannot request connections to the resource.
 
 * **Environments** – The number of app environments on Mendix Cloud that have an approved connection to the resource.
 
@@ -329,8 +329,8 @@ To view and edit a resource, follow these steps:
     * **Network** – The name of the network to which the agent exposing the resource is connected.
     * **Status** – The status of the resource. This can be one of the following:
 
-	    * **Enabled** – Users can request connections to the resource.
-	    * **Disabled** – Users cannot request connections to the resource.
+        * **Enabled** – Users can request connections to the resource.
+        * **Disabled** – Users cannot request connections to the resource.
 
     * **Environment Details** – A list of app environments that have an approved connection to the resource.
 
@@ -408,8 +408,8 @@ On the **Connections** tab of the **Private Connectivity** page, you can see all
 * **Status** – The status of the connection. This can be one of the following:
 
     * **Pending** – The connection was requested, but not yet approved. The app environment cannot connect to the resource using this connection.
-	* **Approved** – The connection is approved. The app environment can connect to the resource using this connection.
-	* **Rejected** – The connection is rejected. The app environment cannot connect to the resource using this connection.
+    * **Approved** – The connection is approved. The app environment can connect to the resource using this connection.
+    * **Rejected** – The connection is rejected. The app environment cannot connect to the resource using this connection.
 
     For details on how Technical Contacts request connections for a specific environment, refer to [Connecting to External Resources](/developerportal/deploy/connecting-to-external-resource/).
 
@@ -422,14 +422,14 @@ To view an existing connection, follow these steps:
 
     * **Request Details** – The details of the connections request:
 
-	    * **Name** – The name of the user that requested this connection.
-	    * **Status** – The status of the connection request. This can be one of the following:
+        * **Name** – The name of the user that requested this connection.
+        * **Status** – The status of the connection request. This can be one of the following:
 
-		    * **Pending** – The connection was requested, but not yet approved. The app environment cannot connect to the resource using this connection.
-		    * **Approved** – The connection is approved. The app environment can connect to the resource using this connection.
-		    * **Rejected** – The connection is rejected. The app environment cannot connect to the resource using this connection.
+            * **Pending** – The connection was requested, but not yet approved. The app environment cannot connect to the resource using this connection.
+            * **Approved** – The connection is approved. The app environment can connect to the resource using this connection.
+            * **Rejected** – The connection is rejected. The app environment cannot connect to the resource using this connection.
 
-	    * **Date** – The date and time when the connection was requested.
+        * **Date** – The date and time when the connection was requested.
 
     * **App** – The name of the app for the connection.
     * **Environment** – The name of the environment for the connection.

content/en/docs/deployment/mendix-cloud-deploy/change-plan.md

@@ -157,7 +157,6 @@ After scheduling, once the plan change process starts:
 2. If the request fails required validations, the status changes to **Ineligible**.
 3. If the request passes all required validations, the status progresses to **Completed** (if successful) or **Failed** (if an execution error occurs).
 
-
 {{% alert color="info" %}}
 After a plan change is applied, you cannot change to a new plan for the same environment for the next 6 hours.
 {{% /alert %}}

content/en/docs/deployment/mendix-cloud-deploy/environments-details.md

@@ -599,4 +599,4 @@ One custom service is available: Mendix Event Broker. This service is required t
 
 ### Enabling Custom Services
 
-Custom services are only available if the app's Technical Contact has enabled them. The custom services are enabled or disabled separately for each environment of each app. For more information, see [Services](/developerportal/deploy/environments/#services) in the *Environments* documentation.
+Custom services are only available if the app's Technical Contact has enabled them. The custom services are enabled or disabled separately for each environment of each app. For more information, see [Services](/developerportal/deploy/environments/#services) in the *Environments* documentation.

content/en/docs/deployment/mx-azure/mx-azure-monitor.md

@@ -160,4 +160,4 @@ rate(
 
 * Trigger when the reduced value is above **0.1**.
 
-This alert fires when the application consumes more than 0.1 CPU core.
+This alert fires when the application consumes more than 0.1 CPU core.

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

@@ -108,11 +108,11 @@ You can specify the following options:
     For example, setting this to **50%** will switch all clients to the updated app version once 50% of all replicas are running the updated version. If not otherwise specified, 50% is used as the default value. This option is only used if the strategy **type** is set to **PreferRolling**.
 * **rollingUpdate** - Specifies parameters for rolling updates if the Operator is able to perform the update without a restart. These parameters are used as Kubernetes [rollingUpdate](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment) parameters:
     * **maxSurge** – Specifies an absolute or percentage value for how many additional replicas can be added during the deployment process.
-      * For apps with 1 replica, the default value is **1**, to run an updated (replacement) replica in addition to the current replica, and prevent any downtime when possible.
-      * For apps with 2 or more replicas, the default value is **0**, so that no additional replicas are added during the rollout process, and instead existing replicas are stopped to avoid using additional cluster resources.
+        * For apps with 1 replica, the default value is **1**, to run an updated (replacement) replica in addition to the current replica, and prevent any downtime when possible.
+        * For apps with 2 or more replicas, the default value is **0**, so that no additional replicas are added during the rollout process, and instead existing replicas are stopped to avoid using additional cluster resources.
     * **maxUnavailable** – Specifies an absolute or percentage value for how many replicas can be stopped to be replaced with updated versions during the rollout process. Increasing this value speeds up the rollout process, but can cause performance issues.
-      * For apps with 1 replica, the default value is **0**, to ensure that at least one replica is running, and prevent downtime.
-      * For apps with 2 or more replicas, the default value is **1**, so that at most one replicas would be stopped during the update process.
+        * For apps with 1 replica, the default value is **0**, to ensure that at least one replica is running, and prevent downtime.
+        * For apps with 2 or more replicas, the default value is **1**, so that at most one replicas would be stopped during the update process.
 
 ## Configuring Pod Disruption Budget parameters in Standalone Environments {#pod-disruption-budget-in-standalone}
 
@@ -143,9 +143,9 @@ spec:
 You can specify the following options:
 
 * **maxUnavailable** – Specifies an absolute or percentage value for how many replicas can be stopped if Kubernetes needs to evict them from a node.
-  * For apps with 2 or more replicas, the default value is **1** and means that at most 1 replica can be stopped, and that Kubernetes needs to wait until a replacement replica becomes available. Increasing this value speeds up the rollout process, but can cause performance issues.
+    * For apps with 2 or more replicas, the default value is **1** and means that at most 1 replica can be stopped, and that Kubernetes needs to wait until a replacement replica becomes available. Increasing this value speeds up the rollout process, but can cause performance issues.
 * **minAvailable** – Specifies an absolute or percentage value for how many replicas need to be remain available if Kubernetes needs to evict them from a node. Increasing this value slows down the rollout process, but ensures that less replicas can be disrupted.
-  * For apps with 1 replica, the default value is **1** to ensure that at least one replica is always available, and prevent downtime.
+    * For apps with 1 replica, the default value is **1** to ensure that at least one replica is always available, and prevent downtime.
 
 {{% alert color="warning" %}}
 Kubernetes doesn't allow specifying values for both `maxUnavailable` and `minAvailable`, and specifying values for both of them will [result in an error](https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget).

content/en/docs/marketplace/platform-supported-content/modules/document-generation/_index.md

@@ -71,4 +71,4 @@ The PDF document generation service does not store pages or documents at any tim
 
 ### Dependencies
 
-* [Combo Box](https://marketplace.mendix.com/link/component/219304) widget
+* [Combo Box](https://marketplace.mendix.com/link/component/219304) widget

content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/2506-configuration/_index.md

@@ -11,4 +11,4 @@ The following pages describe the steps needed to configure the connection betwee
 * [Configuring the Connection to Teamcenter](/appstore/modules/siemens-plm/configuring-connection/)
 * [Configuring the Connection to Teamcenter X](/appstore/modules/siemens-plm/teamcenterx/)
 
-For information applying to Teamcenter Connector 2512.0.0 and above, refer to [Configuring the Connection to Teamcenter 2512.0.0 and Above](/appstore/modules/siemens-plm/configuring-connection-2512/).
+For information applying to Teamcenter Connector 2512.0.0 and above, refer to [Configuring the Connection to Teamcenter 2512.0.0 and Above](/appstore/modules/siemens-plm/configuring-connection-2512/).

content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/_index.md

@@ -37,4 +37,3 @@ Teamcenter Connector for Mendix is available on the [Mendix Marketplace](https:/
 
     * (Optional) Siemens PLM Software UI Resources. This application should be in the project that contains the Teamcenter Connector.
     * (Optional) Teamcenter Connector Sample Application. The Sample Application contains sample microflows. You do not require to download the Sample Application in the same project that also contains the Teamcenter Connector.
-

content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/designing-applications.md

@@ -55,4 +55,3 @@ If you have setup multiple Teamcenter configurations, you can choose a specific
 4. From the configurations list, click **Login** against the configuration that you want to use.
     {{< figure src="/attachments/partners/siemens/teamcenter/image016.png" alt="" class="no-border" >}}
 5. In the page that appears, log on to the chosen configuration.
-

content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/documentation-references.md

@@ -15,4 +15,4 @@ You can refer to the [Teamcenter Connector Reference](/appstore/modules/siemens-
 
 You can generate SOA APIs that are used in Active Workspace by running the genSoaApi script.
 
-For more information, refer to the [Active Workspace Customization documentation](https://docs.sw.siemens.com/doc/282219420/PL20241125556497283.Configuration/xid1211135).
+For more information, refer to the [Active Workspace Customization documentation](https://docs.sw.siemens.com/doc/282219420/PL20241125556497283.Configuration/xid1211135).

content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/services-not-included.md

@@ -10,11 +10,11 @@ description: "Describes how to use Teamcenter services that are not included in
 
 The Teamcenter connector provides two APIs for calling any service operation that is part of Teamcenter Services.
 
-* **CallTeamcenterService** — Java action
+* **CallTeamcenterService** – Java action
 
   This Java action can be used directly in any microflow and maps the Mendix domain entities to or from the JSON data structures that are used by Teamcenter Services operations.
 
-* **TcConnection.callTeamcenterService** — Java method
+* **TcConnection.callTeamcenterService** – Java method
 
   This Java method can only be used from within the Java code and requires that the caller create and parse JSONObjects directly for the call. The **TcConnector** class also exposes an entity version of the **callTeamcenterService** method that matches the Java action.
 
@@ -178,7 +178,7 @@ Following is the operation mapping file for createWorkflow SOA call:
 
 Mendix Domain Model entities are mapped to Teamcenter service operation data structures based on naming conventions. The Teamcenter structure element names (keys in JSON document) map one-to-one to the entity member (attributes or associations) names, with the following caveats:
 
-* The entity member name is prefixed with an underscore '_', for example '_type'. In this case the '_' is ignored, thus matching the Teamcenter name of 'type'.
+* The entity member name is prefixed with an underscore '\_', for example '\_type'. In this case the '\_' is ignored, thus matching the Teamcenter name of 'type'.
 * The entity member name is suffixed with '__XXX', for example, 'phone__Home'. In this case the '__Home' is ignored, thus matching the Teamcenter name of 'phone'.
 
 When traversing entities across associations, the entity names are not used. Only the associations between entities must match or be mappable.

content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/teamcenter-configuration-guide.md

@@ -31,7 +31,7 @@ Follow these steps to connect your Mendix app to Teamcenter:
 1. Log in to your Mendix app with the **Administrator** user role.
 2. Use the **NAV_AdminHomePage** button to navigate to the overview page of all Teamcenter configurations.
 
-{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-connector/configuration/teamcenter-new-configuration.png">}}
+    {{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-connector/configuration/teamcenter-new-configuration.png">}}
 
 3. Click **+ New configuration** to create a new configuration.    
     All configurations require the following fields:
@@ -242,7 +242,7 @@ Make sure the SSO setup on your local machine works before working on a deployed
 The SSO setup of the Teamcenter Connector uses deep links to access the Mendix app. We use the following paths:
 
 * `/rest`
-* `/{url_prefix}`, where the default value for `{url_prefix}` is	`/p`.
+* `/{url_prefix}`, where the default value for `{url_prefix}` is    `/p`.
 
 If the URL prefix is changed from `/p`, make sure `CONST_Deeplink_Url_Prefix` matches this URL prefix.
 

content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/teamcenter-reference.md

@@ -3854,7 +3854,7 @@ Boolean
 #### Java action `ExpandPSAllLevels`
 
 SOA URL:  
-`Cad-2007-01-StructureManagement/expandPSAllLevels ` 
+`Cad-2007-01-StructureManagement/expandPSAllLevels` 
 
 Description:  
 This actions finds the chilren at all levels given parent bomline.