Respond to linting errors

Author: MarkvanMents

content/en/docs/appstore/create-content/create-solutions/implement-solutions/sol-upgrade.md

@@ -33,7 +33,7 @@ To upgrade a solution, follow these steps:
 
     {{< figure src="/attachments/appstore/create-content/implement-solutions/solution-upgrade.png" alt="Upgrade Solution" class="no-border" >}}
 
-{{% alert color="info" %}}In Studio Pro 9 and below, this option must be enabled by setting a feature flag. Since Studio Pro 10, it is available for general use and no longer hidden behind a flag.{{% /alert %}}
+    {{% alert color="info" %}}In Studio Pro 9 and below, this option must be enabled by setting a feature flag. Since Studio Pro 10, it is available for general use and no longer hidden behind a flag.{{% /alert %}}
 
 2. Select the solution package file (*.mxsolution*) provided by the ISV and click **OK**.
 3. Once solution upgrade is completed, a new commit to the **solution-releases** branch line is created. This commit contains the unchanged new version of the solution (as provided by the ISV). You cannot make any changes in this branch, as that would render the solution incompatible with upgrades or lead to unpredictable errors during upgrades.

content/en/docs/appstore/use-content/platform-supported-content/modules/genai/snowflake-cortex.md

@@ -51,10 +51,10 @@ The [Snowflake showcase app](https://marketplace.mendix.com/link/component/22584
 
     This section contains the following pages:
 
-        1. Introduction
-        2. ANOMALY DETECTION (Machine Learning)
-        3. COMPLETE and TRANSLATE (Large Language Models)
-        4. Analyst (Cortex Analyst)
+    1. Introduction
+    2. ANOMALY DETECTION (Machine Learning)
+    3. COMPLETE and TRANSLATE (Large Language Models)
+    4. Analyst (Cortex Analyst)
 
 3. To see how a Snowflake function is called, right-click on the corresponding **SQLStatement** field, and then click **Go to data source microflow**.
 

content/en/docs/refguide/mobile/distributing-mobile-apps/building-native-apps/bitrise.md

@@ -53,7 +53,7 @@ To set up your build project, do the following:
    * Project or Workspace path: `ios/NativeTempalte.xcworkspace`
    * Scheme name: `nativeTemplate`
    * Distribution method: [Choose the distribution method you want to use](https://developer.apple.com/videos/play/wwdc2019/304/)
-   * Build stack: Choose the altest Xcode version compatible with your Mendix version
+   * Build stack: Choose the latest Xcode version compatible with your Mendix version
 1. Finish creating the project.
 1. Abort the build if one starts automatically (you first need to setup code signing and adjust the workflow).
 
@@ -90,7 +90,7 @@ Add a missing npm command by doing the following:
 
 By default, Bitrise targets both Android and iOS. If you do not need to build for both operating systems (OS), remove all actions related to that OS and skip all steps below related to it as well.
 
-For example, if you only target iOS, you can remove the actions **Install missing Androide SDK components** and **Android Build**. This will significantly speed up your builds and save credits.
+For example, if you only target iOS, you can remove the actions **Install missing Android SDK components** and **Android Build**. This will significantly speed up your builds and save credits.
 
 ### Add Android Code Signing (Android only)
 

content/en/docs/refguide/runtime/monitoring-mendix-runtime.md

@@ -536,19 +536,21 @@ Returns feedback about the Mendix Runtime.
 
 ## Logging
 
-Log subscriber is what renders logs. By changing log subscribers it is possible to configure the logs format. 
-For that you need to make three steps:
+A log subscriber renders logs. By changing log subscribers it is possible to configure the log format. 
+For that you need to do three things:
 
 1. Get the name of your current log subscriber
 2. Delete your current log subscriber
 3. Create new log subscriber
 
-### Request to get the name of your current log subscriber
+### Request to Get the Name of Your Current Log Subscriber
 
 ```json
 {"action": "get_log_settings", "params": {"sort": "subscriber"}}
 ```
 
+ [//]: # (<!-- markdownlint-disable no-duplicate-heading -->)
+
 ### Example Response
 
 ```json
@@ -569,7 +571,7 @@ For that you need to make three steps:
 
 If the `feedback` is not empty use the name of your current log subscriber in the next request. In this example the name is `"ConsoleLogSubscriber"`.
 
-### Request to delete your current log subscriber
+### Request to Delete Your Current Log Subscriber
 
 ```json
 {"action": "remove_log_subscriber", "params": {"name": "ConsoleLogSubscriber"}}
@@ -586,7 +588,7 @@ If the `feedback` is not empty use the name of your current log subscriber in th
 
 It is possible to have multiple log subscribers running simultaneously, if several log subscribers were created then each of them will be writing the same log lines. 
 
-### Request to create new log subscriber in Json format
+### Request to Create New Log Subscriber in Json Format
 
 ```json
 {
@@ -620,7 +622,7 @@ This configuration will produce logs similar to these:
 {"node":"Core","level":"INFO","ddtags":"env:test","service":"my-application-name","message":"Mendix Runtime is now shut down.","timestamp":1734629114260}
 ```
 
-### Request to create new log subscriber in simple text format
+### Request to Create New Log Subscriber in Simple Text Format
 
 ```json
 {
@@ -643,3 +645,5 @@ This configuration will produce logs similar to these:
 ```
 
 This will write logs to standard output in simple text format.
+
+[//]: # (<!-- markdownlint-enable no-duplicate-heading -->)

content/en/docs/refguide/runtime/tracing-in-runtime.md

@@ -44,8 +44,7 @@ Below we list the supported tracing-related runtime settings. See [Configure the
 
 | Name | Description | Default |
 |------|-------------|---------|
-| `OpenTelemetry.Enabled` | Can be set to `true` or `false` in order to disable or enable tracing.<br/> {{% alert color="info" %}}
-We support dynamically enabling/disabling tracing using this setting, but the other settings will only be applied the first time you enable tracing.{{% /alert %}} | `false` |
+| `OpenTelemetry.Enabled` | Can be set to `true` or `false` in order to disable or enable tracing.<br/> {{% alert color="info" %}} We support dynamically enabling/disabling tracing using this setting, but the other settings will only be applied the first time you enable tracing.{{% /alert %}} | `false` |
 | `otel.service.name` | The name of the service. | `unknown_service:java` |
 | `otel.resource.attributes` | The resource attributes to include in every span. Example: `attribute1=value1,attribute2=value2` | |
 | `otel.traces.exporter` | Comma-separated list of span exporters. Supported values are: `otlp`, `console`, `logging-otlp`, and `none`. | `otlp` |