Fix linting issues

Author: MarkvanMents

content/en/docs/appstore/modules/document-generation.md

@@ -73,7 +73,7 @@ Follow the instructions in [How to Use Marketplace Content in Studio Pro](/appst
 3. In the **App Explorer**, double-click **Security** in the **App** section again, then go to the **User roles** tab and perform the following steps:
     1. Add the module role **User** from the **DocumentGeneration** module to all app user roles that should be able to generate a document.
     2. Add the module role **Administrator** from the **DocumentGeneration** module to all app user roles that should be able to [register](#register-app) the app environments on Mendix Cloud.
-4. To clean up old document requests, enable the scheduled event **SE_DocumentRequest_Cleanup** in the  **_UseMe** folder of the **DocumentGeneration** module. This wil automatically remove expired **DocumentRequest** objects after a configured offset in days. The offset is configured using the constant **DocumentGeneration.RequestCleanupOffsetInDays** (the default value is 7 days). The scheduled event runs daily at 03:00 UTC.
+4. To clean up old document requests, enable the scheduled event **SE_DocumentRequest_Cleanup** in the  **_UseMe** folder of the **DocumentGeneration** module. This will automatically remove expired **DocumentRequest** objects after a configured offset in days. The offset is configured using the constant **DocumentGeneration.RequestCleanupOffsetInDays** (the default value is 7 days). The scheduled event runs daily at 03:00 UTC.
 5. Depending on where you run the module, continue to perform the procedure in the [Running locally from Studio Pro](#run-locally) section or in the [Running on Mendix Cloud](#run-on-mendix-cloud) section.
 
 ### 3.1 Running Locally from Studio Pro {#run-locally}
@@ -161,7 +161,7 @@ The steps for each procedure are described in the sections below.
 
 3. Create a microflow that contains a **Show page** activity that opens the page you created in the previous step.
 
-{{% alert color="info" %}}If you want, you can copy **DOC_ExampleDocument_Print** microflow from the **Examples** folder to get started.{{% /alert %}}
+    {{% alert color="info" %}}If you want, you can copy **DOC_ExampleDocument_Print** microflow from the **Examples** folder to get started.{{% /alert %}}
 
 4. Create a microflow with the **Generate PDF from page** action to render this page as a PDF document. Configure the **Generate PDF from page** action as follows:
     1. Select the microflow you created in the previous step for the **Page microflow** property.

content/en/docs/developerportal/app-insights/mini-surveys.md

@@ -153,7 +153,7 @@ To create a mini survey, follow these steps:
    * **Conditions** – The conditions you enter here do not affect the mini survey directly. You still need to configure these conditions later in Studio Pro.
      * **Where** – Describe the location where the mini survey appears.
      * **When & How** – Describe what can trigger the mini survey to appear.
-     * **Target User Group (Optional)** – Describe the target user group you would like to reach. Leaving the text box empty means you woud like to reach all users.
+     * **Target User Group (Optional)** – Describe the target user group you would like to reach. Leaving the text box empty means you would like to reach all users.
      * **Attachments (Optional)** – Add attachments if needed. Supported formats are Microsoft Office files, .*pdf*, .*text*, .*png*, and .*jpeg*.
    * **Settings** – The settings in this section take effect immediately. You do not need to implement these settings later in Studio Pro.
      * **Runtime** –  Set the start and end time of the mini survey.
@@ -183,7 +183,7 @@ To edit a mini survey, perform the following steps:
 
 Before the start time of the mini survey is reached, you should implement the survey in Studio Pro. Otherwise, users will not actually receive the mini survey, even if it has the [Status](#survey-status) of **Running** on the **Survey Overview** page. You can [reset the start time in the Settings section](#edit-survey) if you need more time to implement the survey in Studio Pro.
 
-# 3.3.1 Obtaining an API Key {#obtain-api-key}
+#### 3.3.1 Obtaining an API Key {#obtain-api-key}
 
 To obtain an API key for the implementation, follow these steps:
 
@@ -228,7 +228,7 @@ A mini survey has the following opt-out rules:
 
 Survey opt-out rule is a variable cached to your internet browser. You can reset and show a survey multiple times by clearing your browser cache. If you are testing, we recommend you use the **TEST_MODE** constant to avoid clearing every time.
 
-{{% alert color="info" %}}In a future release, we will allow you to customise these opt-out rules from the App Insights portal.{{% /alert %}} 
+{{% alert color="info" %}}In a future release, we will allow you to customize these opt-out rules from the App Insights portal.{{% /alert %}} 
 
 ### 3.6 Unfinished Surveys
 

content/en/docs/releasenotes/developer-portal/_index.md

@@ -15,7 +15,7 @@ For release notes on Mendix Cloud and deployment options, see [Deployment](/rele
 
 To see the current status of the Mendix Developer Portal and Control Center, see [Mendix Status](https://status.mendix.com/). Here you can also see planned maintenance and past incidents.
 
-# 2023
+## 2023
 
 ### August 28, 2023