Merge pull request mendix#6476 from mendix/lint-docs

[Auto] Lint docs

Author: MarkvanMents

content/en/docs/appstore/connectors/aws/aws-authentication.md

@@ -185,13 +185,13 @@ If you have credentials that have been generated without the help of the **GetSe
     * **AccessKeyId** - your IAM access key 
     * **SecretAccesskey** - your secret access key
     * **Provider** - set to *_Session*
-		
+        
 2. Create a **SessionToken** object with the following parameters:
     * **Token** - your token 
     * **Credentials_SessionToken** - the association between **Credentials** and **SessionToken** 
 
 {{< figure src="/attachments/appstore/connectors/aws-authentication/association.png" >}}
-		
+        
 You can then use the above as a valid set of credentials.
 
 ### 4.2 Implementing Static Credentials {#static}

content/en/docs/appstore/connectors/aws/aws-sqs.md

@@ -583,7 +583,7 @@ The input and output for this service are shown in the table below:
 
 | Input | Output |
 | --- | --- |
-| `SendMessageBatchRequest`, `Credentials`, `AWS Region ` | `SendMessageBatchResponse` |
+| `SendMessageBatchRequest`, `Credentials`, `AWS Region` | `SendMessageBatchResponse` |
 
 #### 4.3.2 Receive Messages {#receive-messages}
 

content/en/docs/appstore/connectors/sap/sap-xsuaa-connector.md

@@ -293,4 +293,4 @@ You can picture the authentication as shown below:
 
 ## 5 Upgrading the XSUAA Connector
 
-Version 2.1.1 of the XSUAA Connector for SAP Business Technology Platform uses a new user administration module called **SapAuthentication**. If you are upgrading from version 2.0.0 or below, you will need to migrate your existing users from **Administration.Account** to **SapAuthentication.SapUser** using the [User Migration](/appstore/modules/user-migration-module/) Marketplace module.
+Version 2.1.1 of the XSUAA Connector for SAP Business Technology Platform uses a new user administration module called **SapAuthentication**. If you are upgrading from version 2.0.0 or below, you will need to migrate your existing users from **Administration.Account** to **SapAuthentication.SapUser** using the [User Migration](/appstore/modules/user-migration-module/) Marketplace module.

content/en/docs/appstore/creating-content/connector-guide-build/connector-guide-best-practices.md

@@ -432,7 +432,6 @@ When calling a REST service, you can run into an error. This can be one of two t
 1. Error with a response
 2. Error without a response
 
-
 If there is no response, the default error handling is enough. This will typically occur when the endpoint is down or when you get a timeout.
 
 If there is a response the error message will contain the error code and the reason, but not the message. For that reason, add an additional log message with the response and then rethrow the error. Add details about the request that will help the developer.

content/en/docs/appstore/general/share-app-store-content.md

@@ -120,7 +120,6 @@ Follow these steps to describe your content:
 
     {{% alert color="warning" %}}You can use rich text in the editor. However, using rich text at the beginning of the description is not recommended, as the rich text will not get rendered properly. You should add a few lines of regular text before using rich text.{{% /alert %}}
 
-
 5. Select the location where you want to publish your component:
 
     * <a id="public-app-store"></a>**Public Marketplace (all Mendix users)** – your component will be available to the Mendix community (this content will have to be reviewed and approved by Mendix before it is available)

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/appstore/modules/mendix-mini-surveys.md

@@ -44,7 +44,7 @@ To import this module into your app, follow the instructions in [How to Use Mark
 
 {{% alert color="info" %}}Once the start time of the mini survey is reached, the mini survey will start running, and all the target users of the mini survey will receive the survey automatically.{{% /alert %}}
 
- ## 4 FAQ {#faq} 
+## 4 FAQ {#faq} 
 
 ### 4.1 How to Use a Constant Variable for Survey ID to Show a Survey? 
 
@@ -73,7 +73,8 @@ If your app uses a master layout page and many child pages. You can place one Mi
 ### 4.5 What Are the Survey Opt-Out Rules? {#survey-rules} 
 
 A mini survey has the following opt-out rules: 
- * If a user has closed a survey, without answering any questions, then the survey will not show again to this user.
+
+* If a user has closed a survey, without answering any questions, then the survey will not show again to this user.
 
 * If a user has answered one or more questions in a survey, but did not finished the survey, then the survey will show again. However, if the user has closed the survey before finishing for the second time, the survey will not show again to this user.
 

content/en/docs/appstore/partner-solutions/apd/ig/_index.md

@@ -14,4 +14,3 @@ description: "Presents a list of APD/APM installation guides for each APD/APM ve
 The *APD Installation Guides* are organized according to the APD version.
 
 ## 2 Documents in This Section
-

content/en/docs/appstore/partner-solutions/ats/ht/v2/_index.md

@@ -7,4 +7,3 @@ description_list: true
 ---
 
 These are the documents in this section:
-

content/en/docs/appstore/widgets/tooltip.md

@@ -65,4 +65,4 @@ This option defines how the tooltip will be triggered.
 
 {{% alert color="warning" %}}
 On mobile devices the **Hover** option will be triggered on touch.
-{{% /alert %}}
+{{% /alert %}}