diff --git a/content/en/docs/control-center/security/private-connectivity/configure-private-connectivity.md b/content/en/docs/control-center/security/private-connectivity/configure-private-connectivity.md
index 55ea1096f98..64cc7883662 100755
--- a/content/en/docs/control-center/security/private-connectivity/configure-private-connectivity.md
+++ b/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.
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/change-plan.md b/content/en/docs/deployment/mendix-cloud-deploy/change-plan.md
index ff6aa6dfaea..0fd40e99f2b 100644
--- a/content/en/docs/deployment/mendix-cloud-deploy/change-plan.md
+++ b/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 %}}
diff --git a/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md b/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md
index 33c5b9a5139..81fc4076e0a 100644
--- a/content/en/docs/deployment/mendix-cloud-deploy/environments-details.md
+++ b/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.
\ No newline at end of file
+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.
diff --git a/content/en/docs/deployment/mx-azure/mx-azure-monitor.md b/content/en/docs/deployment/mx-azure/mx-azure-monitor.md
index 598ed34914c..e1a9ccacab2 100644
--- a/content/en/docs/deployment/mx-azure/mx-azure-monitor.md
+++ b/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.
\ No newline at end of file
+This alert fires when the application consumes more than 0.1 CPU core.
diff --git a/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md b/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md
index 007b618a6b2..71b615d2b9c 100644
--- a/content/en/docs/deployment/private-cloud/reduced-downtime-deployment.md
+++ b/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).
diff --git a/content/en/docs/marketplace/platform-supported-content/modules/document-generation/_index.md b/content/en/docs/marketplace/platform-supported-content/modules/document-generation/_index.md
index f5b133654e7..8897d151622 100644
--- a/content/en/docs/marketplace/platform-supported-content/modules/document-generation/_index.md
+++ b/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
\ No newline at end of file
+* [Combo Box](https://marketplace.mendix.com/link/component/219304) widget
diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/2506-configuration/_index.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/2506-configuration/_index.md
index 7f61f8356f2..260fc06c410 100644
--- a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/2506-configuration/_index.md
+++ b/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/).
\ No newline at end of file
+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/).
diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/_index.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/_index.md
index c3e3386d0a9..0df0911a1fa 100644
--- a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/_index.md
+++ b/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.
-
diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/designing-applications.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/designing-applications.md
index 8671ab7afa6..0c9f4e5e985 100755
--- a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/designing-applications.md
+++ b/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.
-
diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/documentation-references.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/documentation-references.md
index a9ce6385969..52411531799 100644
--- a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/documentation-references.md
+++ b/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).
\ No newline at end of file
+For more information, refer to the [Active Workspace Customization documentation](https://docs.sw.siemens.com/doc/282219420/PL20241125556497283.Configuration/xid1211135).
diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/services-not-included.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/services-not-included.md
index 31accee1d0c..89345f86d03 100755
--- a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/services-not-included.md
+++ b/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.
diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/teamcenter-configuration-guide.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/teamcenter-configuration-guide.md
index ebc8b65d7b7..61f3a64d515 100755
--- a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/teamcenter-configuration-guide.md
+++ b/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.
 
diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/teamcenter-reference.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/teamcenter-reference.md
index d5c332b104b..bf02f9d80da 100755
--- a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/teamcenter-reference.md
+++ b/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.  
diff --git a/content/en/docs/marketplace/platform-supported-content/services/event-broker.md b/content/en/docs/marketplace/platform-supported-content/services/event-broker.md
index 9d55cbee795..26d201bed1c 100644
--- a/content/en/docs/marketplace/platform-supported-content/services/event-broker.md
+++ b/content/en/docs/marketplace/platform-supported-content/services/event-broker.md
@@ -170,12 +170,10 @@ The creation process for AWS SQS bridges includes two additional steps on the Me
 #### Configure Service
 
 1. Configure the service by filling out the following:
-
-* **Event Broker Space** – the space where the bridge will operate
-* **Name** – the name you want to call the bridge
-* **AWS region** – the AWS region where your bridge operates
-
-  {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/aws-sqs/ebb_aws_sqs_configure.png" width="400" >}}
+    * **Event Broker Space** – the space where the bridge will operate
+    * **Name** – the name you want to call the bridge
+    * **AWS region** – the AWS region where your bridge operates
+    {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/aws-sqs/ebb_aws_sqs_configure.png" width="400" >}}
 
 2. Click **Next** to continue the configuration.
 
@@ -258,11 +256,11 @@ Add the object below to your Access Policy of the AWS SQS queue if it is receivi
 
 1. Configure the service by filling out the following:
 
-* **Event Broker Space** – the space where the bridge will operate
-* **Name** – the name you want to call the bridge
-* **AWS region** – the AWS region where your bridge operates
+    * **Event Broker Space** – the space where the bridge will operate
+    * **Name** – the name you want to call the bridge
+    * **AWS region** – the AWS region where your bridge operates
 
-  {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/ebb_http_configure.png" width="400" >}}
+    {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/ebb_http_configure.png" width="400" >}}
 
 2. Click **Next** to connect events to your bridge.
 
@@ -296,11 +294,11 @@ To run the HTTP bridge from your client, include a Bearer token in the request h
 
 1. Configure the service by filling out the following:
 
-* **Event Broker Space** – the space where the bridge will operate
-* **Name** – the name you want to call the bridge
-* **Storage Account** – the storage account to access
-* **Storage SAS Token** – the storage SAS Token
-* **Container Path** – the path of the container where the messages will be stored
+    * **Event Broker Space** – the space where the bridge will operate
+    * **Name** – the name you want to call the bridge
+    * **Storage Account** – the storage account to access
+    * **Storage SAS Token** – the storage SAS Token
+    * **Container Path** – the path of the container where the messages will be stored
 
     {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/azure-blob-storage/ebb_azure_blob_configure.png" >}}
 
@@ -323,25 +321,22 @@ Once the Mendix Event Broker Bridge has been successfully deployed, its configur
 
 {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/azure-blob-storage/ebb_azure_blob_overview.png" class="no-border" >}}
 
-
 ### Configuring a Bridge with AWS S3 {#bridge-with-aws-s3}
 
 #### Configure Service
 
 1. Configure the service by filling out the following:
 
-* **Event Broker Space** – the space where the bridge will operate
-* **Name** – the name you want to call the bridge
-* **Bucket** – the path of the container where the messages will be stored
-* **AWS Region for Bucket** – the AWS region where your S3 bucket is located
-* **AWS Role (to Assume)** – the Amazon Resource Name (ARN) of the IAM role that the Event Broker Bridge will assume to access your S3 bucket; this role must be configured with appropriate permissions and a trust policy allowing the Event Broker to assume it
-* **AWS Role's External Id** – a unique identifier that provides additional security when the Event Broker assumes your AWS role; this shared secret ensures that only authorized Mendix Event Broker instances can assume the role
+    * **Event Broker Space** – the space where the bridge will operate
+    * **Name** – the name you want to call the bridge
+    * **Bucket** – the path of the container where the messages will be stored
+    * **AWS Region for Bucket** – the AWS region where your S3 bucket is located
+    * **AWS Role (to Assume)** – the Amazon Resource Name (ARN) of the IAM role that the Event Broker Bridge will assume to access your S3 bucket; this role must be configured with appropriate permissions and a trust policy allowing the Event Broker to assume it
+    * **AWS Role's External Id** – a unique identifier that provides additional security when the Event Broker assumes your AWS role; this shared secret ensures that only authorized Mendix Event Broker instances can assume the role
 
-{{% alert color="info" %}}
-For detailed instructions on how to create the IAM role and obtain these values, see [Configure AWS Authentication for S3 Bridge](#configure-aws-s3-authentication).
-{{% /alert %}}
+        {{% alert color="info" %}}For detailed instructions on how to create the IAM role and obtain these values, see [Configure AWS Authentication for S3 Bridge](#configure-aws-s3-authentication).{{% /alert %}}
 
-{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/aws-s3/ebb_aws_s3_configure.png"  >}}
+    {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/aws-s3/ebb_aws_s3_configure.png"  >}}
 
 2. Click **Next** to connect events to your bridge.
 
@@ -362,7 +357,6 @@ Once the Mendix Event Broker Bridge has been successfully deployed, its configur
 
 {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/aws-s3/ebb_aws_s3_overview.png" class="no-border" >}}
 
-
 #### Configure AWS Authentication for S3 Bridge {#configure-aws-s3-authentication}
 
 The Mendix Event Broker runs in AWS and uses cross-account authentication to securely access your S3 bucket. This authentication mechanism leverages AWS IAM roles with trust policies and external IDs to ensure secure, controlled access.
@@ -441,7 +435,6 @@ The policy above grants the minimum required permissions for the Event Broker to
 
 Use the Role ARN and External ID when configuring your AWS S3 bridge in the Event Broker Manager.
 
-
 ### Managing Bridges
 
 After creating a bridge, you can modify and manage its configuration through the Event Broker Manager.
@@ -492,7 +485,6 @@ To edit a bridge:
 **AWS S3** 
     {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/edit-bridge/ebb_aws_s3_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** once the reconfiguration is complete.
    * Click **Cancel** to exit editing mode without saving any changes.
diff --git a/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md b/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md
index b806cda5c84..d42eed9b4a9 100644
--- a/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md
+++ b/content/en/docs/marketplace/platform-supported-content/widgets/richtext/_index.md
@@ -289,7 +289,7 @@ This code will trigger a new event called **imageSelected** and bubble up the ev
 
 Rich Text version 4 still has limitations that we will continue improving in the future. Current notable limitations are as follows:
 
-- Tables only support basic formatting. The following formatting options are not yet supported:
-    - Nested tables
-    - Table header
-    - Table caption
+* Tables only support basic formatting. The following formatting options are not yet supported:
+    * Nested tables
+    * Table header
+    * Table caption
diff --git a/content/en/docs/quickstarts/responsive-web-app.md b/content/en/docs/quickstarts/responsive-web-app.md
index 39562d726b2..ec47802a376 100644
--- a/content/en/docs/quickstarts/responsive-web-app.md
+++ b/content/en/docs/quickstarts/responsive-web-app.md
@@ -66,7 +66,6 @@ Confirm by clicking **Create App**.
 A starter app is a ready-to-use app template that gives you a basic structure, like navigation, layout, and common components, so you don’t have to start from scratch. It helps you get up and running faster while still giving you full control to customize your app as needed.
 {{% /alert %}}
 
-
 ## Explore Studio Pro Interface
 
 You should see the app open in **Studio Pro**, with the **welcome page** open. Before we continue, let's take a quick tour of the main interface:
@@ -122,7 +121,6 @@ After getting familiar with the Studio Pro interface, you can begin building you
 Domain models are comprised of [entities](/refguide/entities/) (similar to a table in traditional SQL). Entities have [attributes](/refguide/attributes/) (similar to fields). [Properties](/refguide/entities/#properties) define the names of the entities. Entities can relate to each other as one-to-one, one-to-many, or many-to-many. The relations between entities are called [associations](/refguide/associations/). Entities can inherit their properties and attributes from other entities by creating a [Generalization](/refguide/generalization-and-association/#generalization-specialization-and-inheritance) of an entity.
 {{% /alert %}}
 
-
 ### Create an Entity 
 
 To create an entity, follow these steps:
@@ -170,7 +168,6 @@ An employee will be required to complete and upload important documents and cont
 **Generalizations** allow an entity to inherit properties from another. When an entity is a generalization of another, it inherits all the attributes of the original. In this case, Document is a generalization of FileDocument, which will allow it to store anything you might consider a file (this includes images, PDFs, Microsoft Office documents, and more).
 {{% /alert %}}
 
-
 ## Create User Interface
 
 Now that you have created your domain model, you can develop the front-end of your application. Your page is pre-filled with some elements you can add to, edit, or delete. At the top of the page, the label **Home**, along with some welcome text below it, can be seen. 
@@ -234,9 +231,9 @@ Now that we have created a basic front end for your app, we can add some logic.
 1. As the expression above results in a **true** and **false** result, we need to create a **branching path** from the decision - a path for each possible result. **Select** the decision, then from a corner **click and drag** away to create the new alternative path. Ensure to **define** which path is for the true result and the false result by **right-clicking** them both and under **condition value** choosing true and false.
 1. On the **false path**, add a **validation feedback action**. Double click to open its **properties**, enter the following details, and click **OK**:
 
- 1. Variable → Employee
- 1. Member → FirstName
- 1. Template → Please enter a Firstname for the employee
+1. Variable → Employee
+1. Member → FirstName
+1. Template → Please enter a Firstname for the employee
 
 1. Now on the **true path**, repeat this step for the **LastName** and **JobRole** attributes as well.
 
diff --git a/content/en/docs/refguide/installation/upgrading-from-10-to-11/atlas4-migration.md b/content/en/docs/refguide/installation/upgrading-from-10-to-11/atlas4-migration.md
index 3e3d3e023ce..cfc99f5dcbc 100644
--- a/content/en/docs/refguide/installation/upgrading-from-10-to-11/atlas4-migration.md
+++ b/content/en/docs/refguide/installation/upgrading-from-10-to-11/atlas4-migration.md
@@ -111,13 +111,16 @@ In Atlas 4, your `theme/web/custom-variables.scss` file (or any custom SASS file
 
 * Declaration Syntax:
     * Atlas 3 (SASS variables):
+
         ```scss
         // SASS variables at the file root level
         $brand-primary: #264ae5;
         $font-size-default: 14px;
         $bg-color: #f8f8f8;
         ```
+
     * Atlas 4 (CSS variables):
+
         ```scss
         // All global CSS variables must be within :root block
         :root {
@@ -126,8 +129,10 @@ In Atlas 4, your `theme/web/custom-variables.scss` file (or any custom SASS file
           --bg-color: #f8f8f8;
         }
         ```
+
 * Usage Syntax:
     * Atlas 3 (SASS variables):
+
         ```scss
         .my-element {
           color: $brand-primary;
@@ -135,7 +140,9 @@ In Atlas 4, your `theme/web/custom-variables.scss` file (or any custom SASS file
           font-size: $font-size-default;
         }
         ```
+
     * Atlas 4 (CSS variables):
+
         ```css
         .my-element {
           color: var(--brand-primary); /* Use var() function to reference CSS variables */
@@ -161,6 +168,7 @@ SASS offers many built-in functions (like `mix()`, `darken()`, `lighten()`) that
 In SASS, `mix()` blends two colors. The CSS equivalent is `color-mix()`. For more information, see the code samples below:
 
 * SASS `mix()` example:
+
     ```scss
     // SASS variables
     $link-color: #264ae5;
@@ -171,7 +179,9 @@ In SASS, `mix()` blends two colors. The CSS equivalent is `color-mix()`. For mor
       background-color: mix($link-color, $gray-light, 50%);
     }
     ```
+
 * CSS `color-mix()` example,
+
     ```css
     :root {
       --link-color: #264ae5;
@@ -185,15 +195,17 @@ In SASS, `mix()` blends two colors. The CSS equivalent is `color-mix()`. For mor
     ```
 
 Understanding `color-mix()` syntax:
-  * `in srgb`: specifies the color space for mixing. `srgb` is a common and safe choice for web
-  * `var(--link-color) 50%`: the first color and its percentage contribution
-  * `var(--gray-light)`: the second color (gets the remaining percentage, for example: 50%)
+
+* `in srgb`: specifies the color space for mixing. `srgb` is a common and safe choice for web
+* `var(--link-color) 50%`: the first color and its percentage contribution
+* `var(--gray-light)`: the second color (gets the remaining percentage, for example: 50%)
 
 #### Other Commonly Used SASS Functions 
 
 For other SASS functions like `darken()`, `lighten()`, `rgba()`, `transparentize()`, and others, please browse the guidance below:
 
 * **`rgba()` / `hsla()`:** These have direct CSS equivalents and can be used with CSS variables:
+
     ```css
     :root { 
       --my-red-rgb: 255, 0, 0; /* Store as comma-separated RGB values */
@@ -207,12 +219,14 @@ For other SASS functions like `darken()`, `lighten()`, `rgba()`, `transparentize
 * **`darken()` / `lighten()`:** Native CSS equivalents are not as direct, but you can use `color-mix()` in combination with `black` or `white` to achieve similar results:
     
     **To darken a color:**
+
     ```css
     /* Darken by approximately 20% */
     background-color: color-mix(in srgb, var(--brand-primary) 80%, black);
     ```
     
     **To lighten a color:**
+
     ```css
     /* Lighten by approximately 20% */
     background-color: color-mix(in srgb, var(--brand-primary) 80%, white);
@@ -226,9 +240,9 @@ The Atlas core theme (`themesource/atlas_core/web/themes/_theme-default.scss`) u
 
 Atlas 4 has backward compatibility which helps modules using SASS variables still function. However, there are some limitations due to how the two technologies work (pre-processor versus runtime interpretation):
 
-*   **`_theme-default.scss` (Atlas variables with default values)** — This file, located at `themesource/atlas_core/web/themes/_theme-default.scss`, defines the **official Atlas 4 CSS variables**. These are the variables your custom theme should aim to use. You will notice that many of these variables share names with their SASS predecessors (for example, `--brand-primary`, `--font-size-default`), but are now true CSS variables.
+* **`_theme-default.scss` (Atlas variables with default values)** — This file, located at `themesource/atlas_core/web/themes/_theme-default.scss`, defines the **official Atlas 4 CSS variables**. These are the variables your custom theme should aim to use. You will notice that many of these variables share names with their SASS predecessors (for example, `--brand-primary`, `--font-size-default`), but are now true CSS variables.
 
-*   **`_css-variables-mappings.scss` (Compatibility file)** — This file, located at `themesource/atlas_core/web/_css-variables-mappings.scss`, defines a mixin `legacy-variables()`. When this mixin is included (which Atlas does internally), it creates **CSS variables with the same names as many of the old Atlas SASS variables**, and assigns them the **compiled value of those SASS variables** using SASS interpolation (`#{$variable}`).
+* **`_css-variables-mappings.scss` (Compatibility file)** — This file, located at `themesource/atlas_core/web/_css-variables-mappings.scss`, defines a mixin `legacy-variables()`. When this mixin is included (which Atlas does internally), it creates **CSS variables with the same names as many of the old Atlas SASS variables**, and assigns them the **compiled value of those SASS variables** using SASS interpolation (`#{$variable}`).
 
     **Example from `_css-variables-mappings.scss`:**
 
@@ -241,6 +255,7 @@ Atlas 4 has backward compatibility which helps modules using SASS variables stil
       }
     }
     ```
+
     This mechanism ensures that if an internal Atlas component's SASS still references a SASS variable like `$brand-primary`, it will eventually resolve to `var(--brand-primary)` (a CSS variable). This is primarily for enabling transition while staying backwards compatible.
 
 How you should use this information:
@@ -260,9 +275,9 @@ Before making any changes, create a complete backup of your Mendix project. Cons
 
 Do the following steps before your migration begins:
 
-1.  Create a full backup of your Mendix project or commit to version control.
-1.  Ensure you are using Mendix Studio Pro 11 or later.
-1.  In your Mendix project, update the Atlas UI module to its latest Atlas 4 compatible version via the Marketplace. Also, ensure you update all other Marketplace modules, especially `Atlas Web Content` if used, as they may also require Atlas 4 compatibility.
+1. Create a full backup of your Mendix project or commit to version control.
+1. Ensure you are using Mendix Studio Pro 11 or later.
+1. In your Mendix project, update the Atlas UI module to its latest Atlas 4 compatible version via the Marketplace. Also, ensure you update all other Marketplace modules, especially `Atlas Web Content` if used, as they may also require Atlas 4 compatibility.
 
 ### 2.2 Converting theme/web/custom-variables.scss
 
@@ -279,9 +294,9 @@ This section, where you convert `theme/web/custom-variables.scss`, is critical f
   {{% /alert %}}
     
 1. Declare CSS Variables:
-    *   Wrap all your SASS variable declarations within a `:root { ... }` block.
-    *   Change the SASS variable syntax (`$variable-name: value;`) to CSS variable syntax (`--variable-name: value;`).
-    *   **Important Note on Unchanged Variables:** With CSS variables, you only need to declare variables in `custom-variables.scss` if you are *overriding* their default values from Atlas. Any Atlas variables that you are not changing from their default can be safely removed from your `custom-variables.scss` file, reducing clutter and improving clarity. For SASS, it was technically necessary to include them even if unchanged, but this is no longer the case.
+    * Wrap all your SASS variable declarations within a `:root { ... }` block.
+    * Change the SASS variable syntax (`$variable-name: value;`) to CSS variable syntax (`--variable-name: value;`).
+    * **Important Note on Unchanged Variables:** With CSS variables, you only need to declare variables in `custom-variables.scss` if you are *overriding* their default values from Atlas. Any Atlas variables that you are not changing from their default can be safely removed from your `custom-variables.scss` file, reducing clutter and improving clarity. For SASS, it was technically necessary to include them even if unchanged, but this is no longer the case.
         
     Here is an example conversion:
 
@@ -300,7 +315,8 @@ This section, where you convert `theme/web/custom-variables.scss`, is critical f
       +   --bg-color: #f8f8f8;
       + }
       ```
-1.  Handle Imports (if any) — If your `custom-variables.scss` previously imported other SASS files that defined variables (for example `@import 'my-design-system/_colors.scss';`), those imported files also need to be updated to declare CSS variables within a `:root` block.
+
+1. Handle Imports (if any) — If your `custom-variables.scss` previously imported other SASS files that defined variables (for example `@import 'my-design-system/_colors.scss';`), those imported files also need to be updated to declare CSS variables within a `:root` block.
 
 ### 2.3 Updating SASS Variable Usage in Your SCSS Files
 
@@ -372,7 +388,7 @@ There are 3 approaches for achieving module compatibility, depending on if the m
 
 If you own the module, this is the cleanest approach and ensures the module is truly Atlas 4 ready.
 
-1.  Open the module's **.scss** files where SASS variables are used:
+1. Open the module's **.scss** files where SASS variables are used:
     * If the module uses Atlas 3 SASS variables (for example, `$brand-primary`), replace them with the corresponding Atlas 4 CSS variables as defined in `themesource/atlas_core/web/themes/_theme-default.scss` (for example, `var(--brand-primary)`). Use the mapping table in Section 4.3 as a reference.
     * If the module defines its own custom SASS variables, convert them to CSS variables within a `:root` block in a dedicated module `_variables.scss` file, and then update their usage throughout the module:
 
@@ -394,8 +410,8 @@ If you cannot directly modify a Marketplace module (because updates would overwr
 
 To override its styles in your main theme, do the following:
 
-1.  Use browser developer tools to find the specific CSS class names or selectors used by the module's elements.
-1.  In your main theme's SCSS files (for example, a new file imported by `main.scss` in your theme), write override rules.
+1. Use browser developer tools to find the specific CSS class names or selectors used by the module's elements.
+1. In your main theme's SCSS files (for example, a new file imported by `main.scss` in your theme), write override rules.
 
     ```scss
     // In theme/web/sass/custom/_overrides.scss (or similar)
@@ -416,9 +432,9 @@ For popular Marketplace modules, the module developers will likely release Atlas
 
 When creating new custom modules for Atlas 4, employ these best practices:
 
-*  Define and use CSS variables for all your module's styling.
-*  For common styling (colors, spacing, fonts), use Atlas 4's core CSS variables (for example, `--brand-primary`, `--spacing-medium`). This ensures consistency with the main theme.
-*  If your module has specific configurable styles, consider defining them as CSS variables within the module. This allows users to easily customize your module from their `custom-variables.scss` without modifying the module's core files:
+* Define and use CSS variables for all your module's styling.
+* For common styling (colors, spacing, fonts), use Atlas 4's core CSS variables (for example, `--brand-primary`, `--spacing-medium`). This ensures consistency with the main theme.
+* If your module has specific configurable styles, consider defining them as CSS variables within the module. This allows users to easily customize your module from their `custom-variables.scss` without modifying the module's core files:
 
     ```css
     // In themesource/MyNewModule/web/sass/_variables.scss
@@ -433,7 +449,9 @@ When creating new custom modules for Atlas 4, employ these best practices:
       border-radius: var(--my-new-module-border-radius);
     }
     ```
+
     Users can then override these in their `custom-variables.scss`:
+
     ```css
     // In theme/web/custom-variables.scss
     :root {
@@ -452,16 +470,16 @@ This section addresses common problems you might encounter during the Atlas 4 mi
 **Possible Causes & Solutions:**
 
 * Missing `$use-css-variables: true;` declaration:
-   * Solution: Ensure this line is at the top of your `theme/web/custom-variables.scss` file.
+    * Solution: Ensure this line is at the top of your `theme/web/custom-variables.scss` file.
 
 * CSS variables not wrapped in `:root` block:
-   * Solution: All CSS variable declarations must be inside a `:root { }` block.
+    * Solution: All CSS variable declarations must be inside a `:root { }` block.
 
 * Browser caching old compiled CSS:
-   * Solution: Perform a hard refresh in your browser (<kbd>Cmd</kbd>+Shift<kbd>Shift</kbd>+<kbd>R</kbd> on macOS, Ctrl+Shift+R on Windows/Linux) or clear your browser cache.
+    * Solution: Perform a hard refresh in your browser (<kbd>Cmd</kbd>+Shift<kbd>Shift</kbd>+<kbd>R</kbd> on macOS, Ctrl+Shift+R on Windows/Linux) or clear your browser cache.
 
 * SASS compilation errors:
-   * Solution: Check the Studio Pro console for SASS compilation errors. Fix any syntax errors in your SCSS files.
+    * Solution: Check the Studio Pro console for SASS compilation errors. Fix any syntax errors in your SCSS files.
 
 ### Issue: CSS Variables Not Recognized
 
@@ -470,13 +488,13 @@ This section addresses common problems you might encounter during the Atlas 4 mi
 **Possible Causes & Solutions:**
 
 * Variable not defined:
-   * Solution: Ensure the CSS variable is declared in a `:root` block in your `custom-variables.scss` or is available from Atlas core variables.
+    * Solution: Ensure the CSS variable is declared in a `:root` block in your `custom-variables.scss` or is available from Atlas core variables.
 
 * Typo in variable name:
-   * Solution: CSS variable names are case-sensitive. Check for typos like `--brand-Primary` vs `--brand-primary`.
+    * Solution: CSS variable names are case-sensitive. Check for typos like `--brand-Primary` vs `--brand-primary`.
 
 * Scope issues:
-   * Solution: CSS variables defined outside `:root` have limited scope. Use `:root` for global variables.
+    * Solution: CSS variables defined outside `:root` have limited scope. Use `:root` for global variables.
 
 ### Issue: Colors Look Different After Migration
 
@@ -485,13 +503,13 @@ This section addresses common problems you might encounter during the Atlas 4 mi
 **Possible Causes & Solutions:**
 
 * SASS function conversion issues:
-   * Solution: SASS functions like `darken()` and `lighten()` don't translate 1:1 to CSS `color-mix()`. You may need to adjust percentages. Test and tweak values.
+    * Solution: SASS functions like `darken()` and `lighten()` don't translate 1:1 to CSS `color-mix()`. You may need to adjust percentages. Test and tweak values.
 
 * Color space differences:
-   * Solution: `color-mix()` uses color spaces like `srgb`. Different color spaces can produce slightly different results than SASS functions.
+    * Solution: `color-mix()` uses color spaces like `srgb`. Different color spaces can produce slightly different results than SASS functions.
 
 * Fallback to Atlas defaults:
-   * Solution: If you removed too many variables from `custom-variables.scss`, some might be falling back to Atlas defaults. Re-add any custom values you want to preserve.
+    * Solution: If you removed too many variables from `custom-variables.scss`, some might be falling back to Atlas defaults. Re-add any custom values you want to preserve.
 
 ### Issue: Module Styling Inconsistent
 
@@ -500,13 +518,13 @@ This section addresses common problems you might encounter during the Atlas 4 mi
 **Possible Causes & Solutions:**
 
 * Module has not been migrated:
-   * Solution: Check if the module's SCSS files still use SASS variables. Follow the steps in [Part 3](#ensuring-module-compatibility) to update the module.
+    * Solution: Check if the module's SCSS files still use SASS variables. Follow the steps in [Part 3](#ensuring-module-compatibility) to update the module.
 
 * Marketplace module not Atlas 4 compatible:
-   * Solution: Check for updates to the module in the Mendix Marketplace. If unavailable, consider overriding styles in your main theme or contacting the module maintainer.
+    * Solution: Check for updates to the module in the Mendix Marketplace. If unavailable, consider overriding styles in your main theme or contacting the module maintainer.
 
 * Missing module variable mappings:
-   * Solution: The module may use custom SASS variables not covered by Atlas. You'll need to convert these manually.
+    * Solution: The module may use custom SASS variables not covered by Atlas. You'll need to convert these manually.
 
 ## Part 5: Quick Reference
 
@@ -545,4 +563,4 @@ Always review regex replacements carefully before applying them. Complex SASS us
 * [Design Properties](/apidocs-mxsdk/apidocs/design-properties/)
 * [Atlas UI Reference App](https://atlasdesignsystem.mendixcloud.com/)
 * [CSS Custom Properties - MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/CSS/--*)
-* [CSS color-mix() Function - MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/color-mix)
\ No newline at end of file
+* [CSS color-mix() Function - MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/color-mix)
diff --git a/content/en/docs/refguide/runtime/custom-settings/s3-encryption-key-update.md b/content/en/docs/refguide/runtime/custom-settings/s3-encryption-key-update.md
index 751309d18dd..3befa71d401 100644
--- a/content/en/docs/refguide/runtime/custom-settings/s3-encryption-key-update.md
+++ b/content/en/docs/refguide/runtime/custom-settings/s3-encryption-key-update.md
@@ -66,4 +66,4 @@ This Java action can be repeatedly called from a microflow that reads objects of
 
 Here, a list of FileDocument objects is retrieved, for example 100, ordered by the `FileID` attribute, and passed to the `JA_RefreshFileContents` Java action. This is repeated until all the batches of files are processed. The microflow logs and stores the `FileID` attribute of the last processed file in each batch in case the process gets interrupted.
 
-This microflow can be executed in a task queue.
\ No newline at end of file
+This microflow can be executed in a task queue.
diff --git a/content/en/docs/refguide10/runtime/custom-settings/s3-encryption-key-update.md b/content/en/docs/refguide10/runtime/custom-settings/s3-encryption-key-update.md
index 45a698d4e3e..b077260cbf7 100644
--- a/content/en/docs/refguide10/runtime/custom-settings/s3-encryption-key-update.md
+++ b/content/en/docs/refguide10/runtime/custom-settings/s3-encryption-key-update.md
@@ -66,4 +66,4 @@ This Java action can be repeatedly called from a microflow that reads objects of
 
 Here, a list of FileDocument objects is retrieved, for example 100, ordered by the `FileID` attribute, and passed to the `JA_RefreshFileContents` Java action. This is repeated until all the batches of files are processed. The microflow logs and stores the `FileID` attribute of the last processed file in each batch in case the process gets interrupted.
 
-This microflow can be executed in a task queue.
\ No newline at end of file
+This microflow can be executed in a task queue.
diff --git a/content/en/docs/refguide9/runtime/custom-settings/s3-encryption-key-update.md b/content/en/docs/refguide9/runtime/custom-settings/s3-encryption-key-update.md
index c9d78c69aba..6503631698a 100644
--- a/content/en/docs/refguide9/runtime/custom-settings/s3-encryption-key-update.md
+++ b/content/en/docs/refguide9/runtime/custom-settings/s3-encryption-key-update.md
@@ -66,4 +66,4 @@ This Java action can be repeatedly called from a microflow that reads objects of
 
 Here, a list of FileDocument objects is retrieved, for example 100, ordered by the `FileID` attribute, and passed to the `JA_RefreshFileContents` Java action. This is repeated until all the batches of files are processed. The microflow logs and stores the `FileID` attribute of the last processed file in each batch in case the process gets interrupted.
 
-This microflow can be executed in a task queue.
\ No newline at end of file
+This microflow can be executed in a task queue.
diff --git a/content/en/docs/releasenotes/deployment/mendix-cloud/2019.md b/content/en/docs/releasenotes/deployment/mendix-cloud/2019.md
index 9f2973e1312..388abe65db9 100644
--- a/content/en/docs/releasenotes/deployment/mendix-cloud/2019.md
+++ b/content/en/docs/releasenotes/deployment/mendix-cloud/2019.md
@@ -236,4 +236,4 @@ If you run services that connect to a `*.mendixcloud.com` endpoint AND use a sta
 #### Fixes
 
 * We fixed issues regarding incorrect values for some application constants for some Mendix Cloud v4 and v3 applications. (Tickets 77302, 77390, 77505, 77797)
-* We addressed and fixed an issue that prevented some Mendix Cloud v3 users from being able to change the Java version of their applications. (Tickets 77251, 77652)
\ No newline at end of file
+* We addressed and fixed an issue that prevented some Mendix Cloud v3 users from being able to change the Java version of their applications. (Tickets 77251, 77652)
diff --git a/content/en/docs/releasenotes/deployment/mendix-cloud/2023.md b/content/en/docs/releasenotes/deployment/mendix-cloud/2023.md
index a1334ba1e05..7b33b628143 100644
--- a/content/en/docs/releasenotes/deployment/mendix-cloud/2023.md
+++ b/content/en/docs/releasenotes/deployment/mendix-cloud/2023.md
@@ -218,4 +218,4 @@ weight: 4
 
 #### Improvements
 
-* We have introduced support for [Dynatrace](/developerportal/operate/dynatrace-metrics/) monitoring in Mendix Cloud v4.
\ No newline at end of file
+* We have introduced support for [Dynatrace](/developerportal/operate/dynatrace-metrics/) monitoring in Mendix Cloud v4.
diff --git a/content/en/docs/releasenotes/deployment/mendix-cloud/2024.md b/content/en/docs/releasenotes/deployment/mendix-cloud/2024.md
index 68e02b7db91..130da858a98 100644
--- a/content/en/docs/releasenotes/deployment/mendix-cloud/2024.md
+++ b/content/en/docs/releasenotes/deployment/mendix-cloud/2024.md
@@ -170,4 +170,4 @@ weight: 3
 #### Bug Fixes
 
 * We have fixed an issue with two-factor authentication (2FA) on the **Metrics** and **Logs** pages. The 2FA is now session based and not at the account level.
-* Memory-related metrics graphs now display in gibibytes (GiB) and not gigabytes (GB).
\ No newline at end of file
+* Memory-related metrics graphs now display in gibibytes (GiB) and not gigabytes (GB).
diff --git a/content/en/docs/releasenotes/deployment/mendix-cloud/2025.md b/content/en/docs/releasenotes/deployment/mendix-cloud/2025.md
index fcb10cea2d8..8dcef15e714 100644
--- a/content/en/docs/releasenotes/deployment/mendix-cloud/2025.md
+++ b/content/en/docs/releasenotes/deployment/mendix-cloud/2025.md
@@ -223,4 +223,4 @@ You can now change your plan from the [Plan Details](/developerportal/deploy/env
 
 #### Improvements
 
-* Based on user feedback, the [new UI](/developerportal/deploy/environments/) now also contains UX improvements to the **Environments Overview** page for paid apps.
\ No newline at end of file
+* Based on user feedback, the [new UI](/developerportal/deploy/environments/) now also contains UX improvements to the **Environments Overview** page for paid apps.
diff --git a/content/en/docs/releasenotes/digital-execution/2025.md b/content/en/docs/releasenotes/digital-execution/2025.md
index 8d57e841bc9..8f817307519 100644
--- a/content/en/docs/releasenotes/digital-execution/2025.md
+++ b/content/en/docs/releasenotes/digital-execution/2025.md
@@ -17,4 +17,4 @@ numberless_headings: true
 
 The [Compass](https://compass.home.mendix.com/) tool is made available to teams who want to plan and streamline the implementation of their first Mendix app. With the Compass tool, you can define your own vision of low-code and the apps that you want to build with Mendix, and then simplify their implementation by following a number of predefined best-practice milestones and action points. For more information about the tool, see [Preparing to launch your First Mendix App with Compass](/developerportal/compass/).
 
-{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
\ No newline at end of file
+{{% alert color="info" %}} This feature is currently available to participating customers. For more information, contact your Customer Success Manager. {{% /alert %}}
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2017.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2017.md
index b81ff5f640b..d47f7caf492 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2017.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2017.md
@@ -13,4 +13,4 @@ numberless_headings: true
 
 #### New Features
 
-* Private company App Store content is now indicated in the **Template** browser with a lock icon.
\ No newline at end of file
+* Private company App Store content is now indicated in the **Template** browser with a lock icon.
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2018.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2018.md
index 6472165b2e3..25f2f5bc23c 100644
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2018.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2018.md
@@ -42,4 +42,3 @@ The existing SAP Blank app template has been replaced by a new Fiori Blank app t
 #### Breaking Changes
 
 The new **SAP OData Connector** will break existing projects which are using the SAP Cloud Connector. The SAP OData Connector no longer supports the “Use Cloud Connector” attribute. This is now embedded in the destination service configuration. See [SAP Destination Service](/developerportal/deploy/sap-cloud-platform/sap-destination-service/) for more details.
-
diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2025.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2025.md
index 544b4d3f6fa..40b2acecd67 100755
--- a/content/en/docs/releasenotes/marketplace/general-marketplace/2025.md
+++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2025.md
@@ -16,7 +16,6 @@ numberless_headings: true
 * You can now deprecate Marketplace components that are no longer maintained. This helps keep a clean and reliable Marketplace ecosystem, with full visibility into the content that is no longer supported, as well as its recommended alternatives.    
   For details, refer to [Deprecating Marketplace Content](/appstore/deprecate-content/).
 
-
 ## October 2025
 
 ### October 9, 2025
diff --git a/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md b/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md
index 949f0de94d8..27debe647f3 100644
--- a/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md
+++ b/content/en/docs/releasenotes/mobile/mendix-native-mobile-builder.md
@@ -33,11 +33,11 @@ To fix this issue, do the following:
 
 ### iOS Location Permission Change
 
-- We changed the criterion for location permissions on iOS. It used to be required by default, but can now be opted in or out of from the **Native Permissions** screen.
+* We changed the criterion for location permissions on iOS. It used to be required by default, but can now be opted in or out of from the **Native Permissions** screen.
 
 ### Features
 
-- We added support for `MEDIA` permissions on Android targeting OS 13+. The permissions are now shown in the Native Builder. Subsequently, this also fixes cases of these permissions not working correctly on these devices.
+* We added support for `MEDIA` permissions on Android targeting OS 13+. The permissions are now shown in the Native Builder. Subsequently, this also fixes cases of these permissions not working correctly on these devices.
 
 ## Release 1.0.144 {#10143}
 
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.18.md b/content/en/docs/releasenotes/studio-pro/10/10.18.md
index 0cffb6a7c23..d641fb3e9e6 100644
--- a/content/en/docs/releasenotes/studio-pro/10/10.18.md
+++ b/content/en/docs/releasenotes/studio-pro/10/10.18.md
@@ -15,18 +15,18 @@ weight: 82
 
 ### Improvements
 
-- We introduced a new log node named `SystemTask` for logging system management actions.
-- We improved the performance of runtime statistics collection.
-- We improved the scheduling of cluster node management actions.
-- We added batching to the `session keep-alive` and `last action execution update` maintenance tasks. The batch size can be changed using the `SessionKeepAliveUpdateBatchSize` and `LastActionExecutionUpdateBatchSize` runtime settings.
-- We now remove web service user sessions if they are expired.
-- We now cleanup expired sessions in batches instead of all at once.
+* We introduced a new log node named `SystemTask` for logging system management actions.
+* We improved the performance of runtime statistics collection.
+* We improved the scheduling of cluster node management actions.
+* We added batching to the `session keep-alive` and `last action execution update` maintenance tasks. The batch size can be changed using the `SessionKeepAliveUpdateBatchSize` and `LastActionExecutionUpdateBatchSize` runtime settings.
+* We now remove web service user sessions if they are expired.
+* We now cleanup expired sessions in batches instead of all at once.
 
 ### Fixes
 
-- We fixed an issue where trying to delete a huge number (millions) of anonymous sessions during startup would cause out of memory errors. We now delete sessions and anonymous users in batches to avoid this problem. (Ticket 257047)
-- We now avoid resetting failed login count during login when it is already zero. (Ticket 260858)
-- We fixed the issue that invalid sessions without an associated user were never removed from the database.
+* We fixed an issue where trying to delete a huge number (millions) of anonymous sessions during startup would cause out of memory errors. We now delete sessions and anonymous users in batches to avoid this problem. (Ticket 257047)
+* We now avoid resetting failed login count during login when it is already zero. (Ticket 260858)
+* We fixed the issue that invalid sessions without an associated user were never removed from the database.
 
 ## 10.18.12 {#101812}
 
diff --git a/content/en/docs/releasenotes/studio-pro/10/10.24.md b/content/en/docs/releasenotes/studio-pro/10/10.24.md
index e2be8f2553e..989034bbbd1 100644
--- a/content/en/docs/releasenotes/studio-pro/10/10.24.md
+++ b/content/en/docs/releasenotes/studio-pro/10/10.24.md
@@ -21,48 +21,49 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for
 * We introduced a new log node named **SystemTask** for logging system management actions.
 * We improved the performance of runtime statistics collection.
 * We improved the scheduling of cluster node management actions.
-- We aligned the order of the options of the **Use React Client** setting with the order of other settings.
-- We improved the performance of the **Best Practice Recommender**. It now runs faster and uses less memory.
-- We improved the performance of documents operations (**add**, **rename**, **delete**, and more) in the App Explorer.
-- We added batching to the `session keep-alive` and `last action execution update` maintenance tasks. The batch size can be changed using the `SessionKeepAliveUpdateBatchSize` and `LastActionExecutionUpdateBatchSize` runtime settings.
-- We changed the timing of initializing Micrometer gauges during Runtime startup. Previously, the gauges were initialized too early in the startup sequence which would lead to the following warning message; `Failed to apply the value function for the gauge 'mx.runtime.stats.sessions.named_user_sessions'`. Now, gauges are initialized after the database connection has fully initialized, which also gets rid of the warning messages in the logs.
-- We now support tags for the `tcpjsonlines` log subscriber. These can be configured with the `tags` property in the configuration of the log subscriber.
-- We now include tracing information for the `tcpjsonlines` log subscriber, if `includeTracingInformation` is set to `true` when creating the log subscriber. Additionally `traceIdAttribute` and `spanIdAttribute` can be passed to configure what the attributes of the trace and span ids should be in the output JSON log.
+* We aligned the order of the options of the **Use React Client** setting with the order of other settings.
+* We improved the performance of the **Best Practice Recommender**. It now runs faster and uses less memory.
+* We improved the performance of documents operations (**add**, **rename**, **delete**, and more) in the App Explorer.
+* We added batching to the `session keep-alive` and `last action execution update` maintenance tasks. The batch size can be changed using the `SessionKeepAliveUpdateBatchSize` and `LastActionExecutionUpdateBatchSize` runtime settings.
+* We changed the timing of initializing Micrometer gauges during Runtime startup. Previously, the gauges were initialized too early in the startup sequence which would lead to the following warning message; `Failed to apply the value function for the gauge 'mx.runtime.stats.sessions.named_user_sessions'`. Now, gauges are initialized after the database connection has fully initialized, which also gets rid of the warning messages in the logs.
+* We now support tags for the `tcpjsonlines` log subscriber. These can be configured with the `tags` property in the configuration of the log subscriber.
+* We now include tracing information for the `tcpjsonlines` log subscriber, if `includeTracingInformation` is set to `true` when creating the log subscriber. Additionally `traceIdAttribute` and `spanIdAttribute` can be passed to configure what the attributes of the trace and span ids should be in the output JSON log.
 
 ### Fixes
 
-- We fixed an issue that caused slow serialization of Mendix objects in microflow responses when entity access was not applied during retrieval. Serialization speed is now comparable as when entity access is applied. (Ticket 226097)
-- We fixed an issue where the **Find Advanced** > **Unused Items** feature would list enumerations as unused, even when they were actually used (in Microflow expressions). Now, enumerations whose values are used in your project are no longer falsely reported as unused. (Ticket 253576)
-- We fixed an issue where creating a new branch from a tag was not working. (Ticket 259691)
+* We fixed an issue that caused slow serialization of Mendix objects in microflow responses when entity access was not applied during retrieval. Serialization speed is now comparable as when entity access is applied. (Ticket 226097)
+* We fixed an issue where the **Find Advanced** > **Unused Items** feature would list enumerations as unused, even when they were actually used (in Microflow expressions). Now, enumerations whose values are used in your project are no longer falsely reported as unused. (Ticket 253576)
+* We fixed an issue where creating a new branch from a tag was not working. (Ticket 259691)
+
 * In the logic editors, we fixed a performance issue while running a project with many microflows locally. (Ticket 259254)
-- We fixed an issue where a view entity loaded without entity access would throw an exception if used in a location that requires entity access. (Ticket 260557)
-- We fixed the issue where typing in a Dataset document was slow, causing delays in displaying each character. (Ticket 263330)
-- We fixed an issue where Studio Pro repeatedly displayed the error “OQL View Entity is out of sync with the OQL Query” even after syncing the query. The error would reappear after reopening the app, causing confusion and unnecessary sync attempts. (Ticket 263811)
-- We fixed an issue where write permissions could not be removed for attributes that were converted to read-only types (such as AutoNumber). (Ticket 265906)
-- We fixed an issue where sorting by column did not work after using the text search on a grid. (Ticket 266400)
-- We fixed an issue where Studio Pro could crash when importing a font for an [icon collection](/refguide/icon-collection/). (Ticket 266772)
-- We fixed an issue where an incorrectly configured [placeholder text](/refguide/text-box/#placeholder-text) did not show a consistency error and could result in an error during deployment. (Ticket 266923) 
-- The OQL function DATEPART with MILLISECOND now also works on HSQLDB and SAP HANA.
-- We resolved an issue where passwords, when having write access for the password attribute, could be modified directly through the `synchronize_objects` API.
-- We fixed an issue with modern client offline apps that caused data sources of the home page to be executed too early, causing errors because the offline system was not fully initialized.
-- We fixed an issue that was causing excluded modules to be included in the **main.scss** when generating layered CSS
-- We fixed the check version functionality which allowed users to perform version control operations on either revisions created on older Studio Pro versions, or on files with invalid metadata:
+* We fixed an issue where a view entity loaded without entity access would throw an exception if used in a location that requires entity access. (Ticket 260557)
+* We fixed the issue where typing in a Dataset document was slow, causing delays in displaying each character. (Ticket 263330)
+* We fixed an issue where Studio Pro repeatedly displayed the error “OQL View Entity is out of sync with the OQL Query” even after syncing the query. The error would reappear after reopening the app, causing confusion and unnecessary sync attempts. (Ticket 263811)
+* We fixed an issue where write permissions could not be removed for attributes that were converted to read-only types (such as AutoNumber). (Ticket 265906)
+* We fixed an issue where sorting by column did not work after using the text search on a grid. (Ticket 266400)
+* We fixed an issue where Studio Pro could crash when importing a font for an [icon collection](/refguide/icon-collection/). (Ticket 266772)
+* We fixed an issue where an incorrectly configured [placeholder text](/refguide/text-box/#placeholder-text) did not show a consistency error and could result in an error during deployment. (Ticket 266923) 
+* The OQL function DATEPART with MILLISECOND now also works on HSQLDB and SAP HANA.
+* We resolved an issue where passwords, when having write access for the password attribute, could be modified directly through the `synchronize_objects` API.
+* We fixed an issue with modern client offline apps that caused data sources of the home page to be executed too early, causing errors because the offline system was not fully initialized.
+* We fixed an issue that was causing excluded modules to be included in the **main.scss** when generating layered CSS
+* We fixed the check version functionality which allowed users to perform version control operations on either revisions created on older Studio Pro versions, or on files with invalid metadata:
     * Affected operations are: rebase, merge, merge feature branch, cherry-pick and revert.
-- We added keyboard accelerators to the **Find Usages** and **Show Call Hierarchy** options in context menus.
-- We fixed an issue in the logic editors in the **Change Object** dialog where setting lists of objects through the **Generate** dialog incorrectly showed an error.
-- We fixed an issue where during runtime on iOS, the runtime URL would not get properly created when there were more path parts included.
-- We fixed an issue where an Oops pop-up window was displayed when **Edit** > **Find** returned new JSON structure documents.
-- We fixed an issue in Import mapping and Export mapping in Studio Pro where elements except first of the child array in JSON were omitted.
-- We fixed a bug that caused exceptions when undoing the addition of custom widget to a page (from the recommender, Maia, or <kbd>Ctrl</kbd> + **Drag and Drop**) while the properties tab was open and that widget was selected.
-- We now correctly set the log node name as the **node** attribute and the exception cause as the **cause** attribute for the OpenTelemetry log subscriber.
-- We fixed an issue where calling the `get_license_information` while using a SALT license would cause an error.
-- We fixed an issue where offline objects with GUID identifiers were sent to the server when a microflow was called from within a nanoflow, causing a "Global identifier should be a number" error. These unsynced offline objects are now filtered out before being sent. (Ticket 267059)
+* We added keyboard accelerators to the **Find Usages** and **Show Call Hierarchy** options in context menus.
+* We fixed an issue in the logic editors in the **Change Object** dialog where setting lists of objects through the **Generate** dialog incorrectly showed an error.
+* We fixed an issue where during runtime on iOS, the runtime URL would not get properly created when there were more path parts included.
+* We fixed an issue where an Oops pop-up window was displayed when **Edit** > **Find** returned new JSON structure documents.
+* We fixed an issue in Import mapping and Export mapping in Studio Pro where elements except first of the child array in JSON were omitted.
+* We fixed a bug that caused exceptions when undoing the addition of custom widget to a page (from the recommender, Maia, or <kbd>Ctrl</kbd> + **Drag and Drop**) while the properties tab was open and that widget was selected.
+* We now correctly set the log node name as the **node** attribute and the exception cause as the **cause** attribute for the OpenTelemetry log subscriber.
+* We fixed an issue where calling the `get_license_information` while using a SALT license would cause an error.
+* We fixed an issue where offline objects with GUID identifiers were sent to the server when a microflow was called from within a nanoflow, causing a "Global identifier should be a number" error. These unsynced offline objects are now filtered out before being sent. (Ticket 267059)
 
 ### Breaking Changes
     
-- Curly braces in a [placeholder text](/refguide/text-box/#placeholder-text) (for example, `{Name}`) must now be escaped with an extra opening curly brace (for example, `{{Name}`) to prevent the text from being incorrectly interpreted as a placeholder expression.
-- We upgraded the AWS S3 library used for S3 file storage backend from version 1 to 2. This new version of the library has stricter configuration handling and only supports AES for client side encryption. More information can be found in [Amazon S3 SDK Upgrade](/refguide10/amazon-s3-sdk-upgrade/) and [S3 Storage Service Settings](/refguide10/custom-settings/#amazon-s3-storage-service-settings).
-- Added a consistency check for code actions that have a file name that does not match the casing of the document name, which could cause issues on certain operating systems and when deploying to the cloud environment.
+* Curly braces in a [placeholder text](/refguide/text-box/#placeholder-text) (for example, `{Name}`) must now be escaped with an extra opening curly brace (for example, `{{Name}`) to prevent the text from being incorrectly interpreted as a placeholder expression.
+* We upgraded the AWS S3 library used for S3 file storage backend from version 1 to 2. This new version of the library has stricter configuration handling and only supports AES for client side encryption. More information can be found in [Amazon S3 SDK Upgrade](/refguide10/amazon-s3-sdk-upgrade/) and [S3 Storage Service Settings](/refguide10/custom-settings/#amazon-s3-storage-service-settings).
+* Added a consistency check for code actions that have a file name that does not match the casing of the document name, which could cause issues on certain operating systems and when deploying to the cloud environment.
 
 ## 10.24.13 {#102413}
 
diff --git a/content/en/docs/releasenotes/studio-pro/11/11.6.md b/content/en/docs/releasenotes/studio-pro/11/11.6.md
index 16c0800d39f..637d7594e67 100644
--- a/content/en/docs/releasenotes/studio-pro/11/11.6.md
+++ b/content/en/docs/releasenotes/studio-pro/11/11.6.md
@@ -16,28 +16,29 @@ mts: true
 
 ### Improvements
     
-- Entities set to online synchronization mode can now be used by non-pluggable widgets on offline pages.
-- We added a configurable option **Use new string behavior** in the **Runtime** tab that controls how null and undefined values are handled for string attributes in the client. The new behavior (default for new projects) keeps these values as null to maintain consistency between nanoflows and microflows, while the old behavior converts them to empty strings. This option provides backward compatibility and gives developers time to migrate to the new more consistent behavior.
-- We have improved session cleanup performance.
+* Entities set to online synchronization mode can now be used by non-pluggable widgets on offline pages.
+* We added a configurable option **Use new string behavior** in the **Runtime** tab that controls how null and undefined values are handled for string attributes in the client. The new behavior (default for new projects) keeps these values as null to maintain consistency between nanoflows and microflows, while the old behavior converts them to empty strings. This option provides backward compatibility and gives developers time to migrate to the new more consistent behavior.
+* We have improved session cleanup performance.
 
 ### Fixes
 
-- We fixed an issue when the last attributes were truncated in entity **Properties** dialog boxes. (Tickets 51278, 255882, 256106, 260953, 266554)
-- We fixed an issue where a widget configured with an incorrect type of primitive parameter did not show a consistency error and could result in an error in the client.
-- We fixed an issue where the **Find Advanced** > **Unused Items** feature would list enumerations as unused, even when they were actually used (in microflow expressions). Now, enumerations whose values are used in your project are no longer falsely reported as unused. (Ticket 253576)
-- We fixed the issue where typing in a dataset document was slow, causing delays in displaying each character. (Ticket 263330)
+* We fixed an issue when the last attributes were truncated in entity **Properties** dialog boxes. (Tickets 51278, 255882, 256106, 260953, 266554)
+* We fixed an issue where a widget configured with an incorrect type of primitive parameter did not show a consistency error and could result in an error in the client.
+* We fixed an issue where the **Find Advanced** > **Unused Items** feature would list enumerations as unused, even when they were actually used (in microflow expressions). Now, enumerations whose values are used in your project are no longer falsely reported as unused. (Ticket 253576)
+* We fixed the issue where typing in a dataset document was slow, causing delays in displaying each character. (Ticket 263330)
+
 * In the logic editors, we fixed an issue which occurred when an extracted microflow did not have all the parameters for a newly created activity. (Ticket 265542)
-- We fixed an issue with the [tab container](/refguide/tab-container/) widget. It would reset to the first tab when returning to the page, causing data sources to reload unnecessarily and other tabs to be blocked. (Tickets 266083, 266090, 267249)
-- We fixed an issue on macOS where, when while typing in the search field, the text would get highlighted automatically and overwritten by subsequent characters. (Ticket 267303) 
-- We fixed an issue that caused setting the image of a building block to show an error dialog box instead of resizing the image. (Ticket 268856)
-- We fixed an issue where a remote entities with decimal primary keys would cause errors on startup on existing deployments.
-- We fixed an issue with modern client offline apps that caused data sources of the home page to be executed too early causing errors because the offline system was not fully initialized.
-- We fixed an issue where **Maia Explain for Microflows** crashes sometimes.
-- We fixed an issue in Maia chat causing it to crash when a Studio Pro version attribute was missing in a reference.
-- We fixed scenarios in Android where navigating fields of a data view of different types was not be possible while using an external keyboard.
-- We fixed an issue where an interruption while fetching data would lead to model changes not being displayed properly in the new **History** pane.
-- We fixed an issue during local development where system texts would not be updated in the application when hot-reloading. They are now correctly updated without the need to fully restart the server.
-- We fixed an issue where an **Oops** pop-up window appeared when page actions with return value mappings were copied and pasted or extracted to a snippet.
+* We fixed an issue with the [tab container](/refguide/tab-container/) widget. It would reset to the first tab when returning to the page, causing data sources to reload unnecessarily and other tabs to be blocked. (Tickets 266083, 266090, 267249)
+* We fixed an issue on macOS where, when while typing in the search field, the text would get highlighted automatically and overwritten by subsequent characters. (Ticket 267303) 
+* We fixed an issue that caused setting the image of a building block to show an error dialog box instead of resizing the image. (Ticket 268856)
+* We fixed an issue where a remote entities with decimal primary keys would cause errors on startup on existing deployments.
+* We fixed an issue with modern client offline apps that caused data sources of the home page to be executed too early causing errors because the offline system was not fully initialized.
+* We fixed an issue where **Maia Explain for Microflows** crashes sometimes.
+* We fixed an issue in Maia chat causing it to crash when a Studio Pro version attribute was missing in a reference.
+* We fixed scenarios in Android where navigating fields of a data view of different types was not be possible while using an external keyboard.
+* We fixed an issue where an interruption while fetching data would lead to model changes not being displayed properly in the new **History** pane.
+* We fixed an issue during local development where system texts would not be updated in the application when hot-reloading. They are now correctly updated without the need to fully restart the server.
+* We fixed an issue where an **Oops** pop-up window appeared when page actions with return value mappings were copied and pasted or extracted to a snippet.
 
 ## 11.6.2 {#1162}
 
@@ -47,13 +48,13 @@ mts: true
 
 ### Improvements
 
-- We now log a critical warning instead of aborting runtime startup if the S3 region is not configured.
+* We now log a critical warning instead of aborting runtime startup if the S3 region is not configured.
 
 ### Fixes
 
-- We fixed an issue in consumed OData services that have external enumeration values that are reserved words such as `Int`. The runtime would prepend an underscore to these values when applying a filter. (Ticket 265706)
-- We added keyboard accelerators to the **Find Usages** and **Show Call Hierarchy** options in context menus.
-- We fixed the refresh of commit statuses after **Push** (**Local** > **Synced**) and **Pull** (**On Server** > **Synced**).
+* We fixed an issue in consumed OData services that have external enumeration values that are reserved words such as `Int`. The runtime would prepend an underscore to these values when applying a filter. (Ticket 265706)
+* We added keyboard accelerators to the **Find Usages** and **Show Call Hierarchy** options in context menus.
+* We fixed the refresh of commit statuses after **Push** (**Local** > **Synced**) and **Pull** (**On Server** > **Synced**).
 
 ## 11.6.1 {#1161}
 
@@ -63,31 +64,31 @@ mts: true
 
 ### Improvements
     
-- We introduced a new log node named **SystemTask** for logging system management actions.
-- We improved the performance of runtime statistics collection.
-- We improved the performance of the **Best Practice Recommender**. It now runs faster while using less memory.
-- We improved the performance of [document](/developerportal/general/documents/) operations (**add**, **rename**, **delete**, and more) in the **App Explorer**.
-- We added batching to the `session keep-alive` and `last action execution update` maintenance tasks. The batch size can be changed using the `SessionKeepAliveUpdateBatchSize` and `LastActionExecutionUpdateBatchSize` runtime settings.
-- We now support tags for the `tcpjsonlines` log subscriber. These can be configured with the `tags` property in the configuration of the log subscriber.
-- For the `tcpjsonlines` log subscriber we now include tracing information if `includeTracingInformation` is set to `true` when creating the log subscriber. Additionally, `traceIdAttribute` and `spanIdAttribute` can be passed to configure the attributes of the trace and span IDs in the output JSON log.
+* We introduced a new log node named **SystemTask** for logging system management actions.
+* We improved the performance of runtime statistics collection.
+* We improved the performance of the **Best Practice Recommender**. It now runs faster while using less memory.
+* We improved the performance of [document](/developerportal/general/documents/) operations (**add**, **rename**, **delete**, and more) in the **App Explorer**.
+* We added batching to the `session keep-alive` and `last action execution update` maintenance tasks. The batch size can be changed using the `SessionKeepAliveUpdateBatchSize` and `LastActionExecutionUpdateBatchSize` runtime settings.
+* We now support tags for the `tcpjsonlines` log subscriber. These can be configured with the `tags` property in the configuration of the log subscriber.
+* For the `tcpjsonlines` log subscriber we now include tracing information if `includeTracingInformation` is set to `true` when creating the log subscriber. Additionally, `traceIdAttribute` and `spanIdAttribute` can be passed to configure the attributes of the trace and span IDs in the output JSON log.
 
 ### Fixes
 
-- We fixed an issue where sorting by column would not work after using the text search on a grid. (Ticket 266400)
-- We fixed an issue where Studio Pro could crash when importing a font for an [icon collection](/refguide/icon-collection/). (Ticket 266772)
-- We fixed an issue where an incorrectly configured [placeholder text](/refguide/text-box/#placeholder-text) did not show a consistency error and could result in an error during deployment. (Ticket 266923) 
-- We resolved an issue where passwords, when having write access for the password attribute, could be modified directly through the `synchronize_objects` API.
-- We fixed an issue that was causing excluded modules to be included in **main.scss** when generating layered CSS.
-- We fixed an issue where pasting a view entity together with its associated persistent entity would cause a freeze and an Oops pop-up window.
-- In the logic editors, we fixed a bug that causes Maia Explain for Microflows to crash.
-- We fixed an issue where an Oops pop-up window was displayed when **Edit** > **Find** returned new JSON structure documents.
-- We fixed an issue in consumed REST services in Studio Pro where sending a request to a URL that contained invalid characters would result in an Oops pop-up window.
-- We now correctly set the log node name as the "node" attribute and the exception cause as the "cause" attribute for the OpenTelemetry log subscriber.
-- We fixed an issue where calling the `get_license_information` while using a SALT license would cause an error.
+* We fixed an issue where sorting by column would not work after using the text search on a grid. (Ticket 266400)
+* We fixed an issue where Studio Pro could crash when importing a font for an [icon collection](/refguide/icon-collection/). (Ticket 266772)
+* We fixed an issue where an incorrectly configured [placeholder text](/refguide/text-box/#placeholder-text) did not show a consistency error and could result in an error during deployment. (Ticket 266923) 
+* We resolved an issue where passwords, when having write access for the password attribute, could be modified directly through the `synchronize_objects` API.
+* We fixed an issue that was causing excluded modules to be included in **main.scss** when generating layered CSS.
+* We fixed an issue where pasting a view entity together with its associated persistent entity would cause a freeze and an Oops pop-up window.
+* In the logic editors, we fixed a bug that causes Maia Explain for Microflows to crash.
+* We fixed an issue where an Oops pop-up window was displayed when **Edit** > **Find** returned new JSON structure documents.
+* We fixed an issue in consumed REST services in Studio Pro where sending a request to a URL that contained invalid characters would result in an Oops pop-up window.
+* We now correctly set the log node name as the "node" attribute and the exception cause as the "cause" attribute for the OpenTelemetry log subscriber.
+* We fixed an issue where calling the `get_license_information` while using a SALT license would cause an error.
 
 ### Breaking Changes
 
-- Curly braces in a [placeholder text](/refguide/text-box/#placeholder-text) (for example, `{Name}`) must now be escaped with an extra opening curly brace (for example, `{{Name}`) to prevent the text from being incorrectly interpreted as a placeholder expression.
+* Curly braces in a [placeholder text](/refguide/text-box/#placeholder-text) (for example, `{Name}`) must now be escaped with an extra opening curly brace (for example, `{{Name}`) to prevent the text from being incorrectly interpreted as a placeholder expression.
 
 ## 11.6.0 {#1160}
 
diff --git a/content/en/docs/releasenotes/studio-pro/9/9.24.md b/content/en/docs/releasenotes/studio-pro/9/9.24.md
index 7e4f5719453..f1e1aee4a99 100644
--- a/content/en/docs/releasenotes/studio-pro/9/9.24.md
+++ b/content/en/docs/releasenotes/studio-pro/9/9.24.md
@@ -19,48 +19,48 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 9 release for a
 
 ### Improvements
     
-- We introduced a new log node named **SystemTask** for logging system management actions.
-- We added support for Oracle 23.
-- We added support for the following database versions:
-    - PostgreSQL 18
-    - Microsoft SQL Server 2025
-- We added batching to the `session keep-alive` and `last action execution update` maintenance tasks. The batch size can be changed using the `SessionKeepAliveUpdateBatchSize` and `LastActionExecutionUpdateBatchSize` runtime settings.
-- We now remove web service user sessions if they are expired.
-- We now cleanup expired sessions in batches instead of all at once.
+* We introduced a new log node named **SystemTask** for logging system management actions.
+* We added support for Oracle 23.
+* We added support for the following database versions:
+    * PostgreSQL 18
+    * Microsoft SQL Server 2025
+* We added batching to the `session keep-alive` and `last action execution update` maintenance tasks. The batch size can be changed using the `SessionKeepAliveUpdateBatchSize` and `LastActionExecutionUpdateBatchSize` runtime settings.
+* We now remove web service user sessions if they are expired.
+* We now cleanup expired sessions in batches instead of all at once.
 
 ### Fixes
 
 * We upgraded libraries to fix the following CVEs: CVE-2025-58056, CVE-2025-58057, CVE-2025-55163, CVE-2025-22227.
 * We upgraded the JDBC driver for Microsoft SQL Server to version 12.6.5, because of [CVE-2025-59250](https://www.cve.org/CVERecord?id=CVE-2025-59250).
     * If you connect to SQL Server using integrated security in a module such as [Database Connector](https://marketplace.mendix.com/link/component/2888), you may need to update the JDBC driver in `userlib` as well.
-- We fixed an issue that caused slow serialization of Mendix objects in microflow responses when entity access was not applied during retrieval. Serialization speed is now comparable as when entity access is applied. (Ticket 226097)
-- We fixed an error in the Studio Pro installer when the installer is checking if the .NET version is already installed or not. (Ticket 253218)
-- We fixed an issue where trying to delete a huge amount (millions) of anonymous sessions during startup would cause OOM errors. We now delete sessions and anonymous users in batches to avoid this problem. (Ticket 257047)
-- We fixed an issue where JSON Import mappings stopped finding objects. (Ticket 258507)
-- In the logic editors, we fixed a performance issue that affected locally running projects containing several microflows. (Ticket 259254)
-- We fixed an issue where unsaved changes of the **System Text** editor would be committed when running the app locally. (Ticket 259664)
-- We fixed an issue that prevented some users to authenticate in Studio Pro. (Ticket 259700)
-- SQLite files are now included in the service worker’s pre-cache list to ensure they are available offline. (Ticket 264140, Ticket 264910)
-- We resolved an issue where passwords, when having write access for the password attribute, could be modified directly through the `synchronize_objects` API.
-- We fixed an error while changing application settings after renaming the project folder.
-- We fixed the following bugs in the version selector:
-    - When opening a widget **.mpk** the file was kept on hold even after closing the dialog popup, preventing it to be renamed or opened.
-    - Closing the **Version not found** dialog popup launched the selected Studio Pro version instead of just closing the dialog popup.
-    - The Studio Pro versions were not displayed with the correct format.
-- We now allow first time users to use Studio Pro without login in when opening Studio Pro for the first time.
-- We fixed an issue in Studio Pro where restarting Windows with an open app and then opening the app again would result in a warning dialog about the app already being open.
-- We fixed the issue that invalid sessions without an associated user were never removed from the database.
+* We fixed an issue that caused slow serialization of Mendix objects in microflow responses when entity access was not applied during retrieval. Serialization speed is now comparable as when entity access is applied. (Ticket 226097)
+* We fixed an error in the Studio Pro installer when the installer is checking if the .NET version is already installed or not. (Ticket 253218)
+* We fixed an issue where trying to delete a huge amount (millions) of anonymous sessions during startup would cause OOM errors. We now delete sessions and anonymous users in batches to avoid this problem. (Ticket 257047)
+* We fixed an issue where JSON Import mappings stopped finding objects. (Ticket 258507)
+* In the logic editors, we fixed a performance issue that affected locally running projects containing several microflows. (Ticket 259254)
+* We fixed an issue where unsaved changes of the **System Text** editor would be committed when running the app locally. (Ticket 259664)
+* We fixed an issue that prevented some users to authenticate in Studio Pro. (Ticket 259700)
+* SQLite files are now included in the service worker’s pre-cache list to ensure they are available offline. (Ticket 264140, Ticket 264910)
+* We resolved an issue where passwords, when having write access for the password attribute, could be modified directly through the `synchronize_objects` API.
+* We fixed an error while changing application settings after renaming the project folder.
+* We fixed the following bugs in the version selector:
+    * When opening a widget **.mpk** the file was kept on hold even after closing the dialog popup, preventing it to be renamed or opened.
+    * Closing the **Version not found** dialog popup launched the selected Studio Pro version instead of just closing the dialog popup.
+    * The Studio Pro versions were not displayed with the correct format.
+* We now allow first time users to use Studio Pro without login in when opening Studio Pro for the first time.
+* We fixed an issue in Studio Pro where restarting Windows with an open app and then opening the app again would result in a warning dialog about the app already being open.
+* We fixed the issue that invalid sessions without an associated user were never removed from the database.
 
 ### Deprecations
     
-- We dropped support for the following database versions that are no longer supported by the vendors:
-    - MariaDB 10.5
-    - Microsoft SQL Server 2019
-    - MySQL 8.0
+* We dropped support for the following database versions that are no longer supported by the vendors:
+    * MariaDB 10.5
+    * Microsoft SQL Server 2019
+    * MySQL 8.0
 
 ### Breaking Changes
     
-- We upgraded the AWS S3 library used for S3 file storage backend from version 1 to 2. This new version of the library has stricter configuration handling and only supports AES for client side encryption. More information can be found in [Amazon S3 SDK Upgrade](/refguide9/amazon-s3-sdk-upgrade/) and [S3 Storage Service Settings](/refguide9/custom-settings/#amazon-s3-storage-service-settings).
+* We upgraded the AWS S3 library used for S3 file storage backend from version 1 to 2. This new version of the library has stricter configuration handling and only supports AES for client side encryption. More information can be found in [Amazon S3 SDK Upgrade](/refguide9/amazon-s3-sdk-upgrade/) and [S3 Storage Service Settings](/refguide9/custom-settings/#amazon-s3-storage-service-settings).
 
 ## 9.24.40
 
diff --git a/content/en/docs/workstation/wks-message-syntax.md b/content/en/docs/workstation/wks-message-syntax.md
index 037436e5b88..3710f0e19b0 100644
--- a/content/en/docs/workstation/wks-message-syntax.md
+++ b/content/en/docs/workstation/wks-message-syntax.md
@@ -37,7 +37,6 @@ Before sending messages to the File Device, review the following points:
 * Delimiter - The `#` character is used as a delimiter within messages. Paths and data may not contain the `#` character. 
 * Case sensitivity - File and directory paths may be case-sensitive depending on the underlying operating system. For example, Linux paths are typically case-sensitive, while Windows paths are not.
  
-
 ### Message
 
 * `0#Path` - Initiate watching for changes in the specified `Path`. If `Path` is a directory, the device will watch for changes within that directory (creation, deletion, renaming, or modification of files/subdirectories). If `Path` is a file, the device will watch for changes to that specific file (modification, deletion, or renaming).