Respond to linting errors

Author: MarkvanMents

content/en/docs/appstore/create-content/create-modules/_index.md

@@ -17,6 +17,7 @@ The guidelines to develop modules and submit them to the Marketplace as as follo
 * For Java dependencies, follow the following guidelines:
 
     * In versions Mendix 10.3.0 and above, use [managed dependencies](/refguide/managed-dependencies/) where possible. For versions below 10.3, ensure that Java dependencies are put in the `userlib` folder. You should also put any [unmanaged dependencies](/refguide/managed-dependencies/#unmanaged), that is, non-publicly-available *.jar* files, in the **userlib** folder.
+    
         * When putting  *.jar*  files in the **userlib** folder, make sure the name includes a version number (for example, `org.apache.commons.io-2.3.0.jar`) and is accompanied by a blank `{jarfile-including-version}.{module_name}.RequiredLib` file so that users know where the .*jar* files come from (for example, for the module *MyModule*, `org.apache.commons.io-2.3.0.jar.MyModule.RequiredLib`).
 
   {{< figure src="/attachments/appstore/submit-content/userlibBlankFiles_boxed.jpg" width="400"  >}}

content/en/docs/appstore/use-content/platform-supported-content/modules/snowflake/mendix-data-loader.md

@@ -48,15 +48,21 @@ Once the Mendix Data Loader is deployed, follow these steps to configure and use
 5. To view the status of your data source, check the **Details**.
 6. To view the configuration status, click the **Authentication Configuration** tab.
 7. To set up authentication, click **Edit**, and then provide the required information based on the selected authentication type:
-        *For basic authentication, enter the following information:
-            * **Username** – A username for basic authentication into the OData resource in your Mendix application
-            ***Password** – A password for basic authentication into the OData resource in your Mendix application
-        * For OAuth authentication, enter the following information:
-            ***Client ID** – A client ID from your OAuth provider
-            * **Client Secret** – A secret associated with the client from your OAuth provider
-            ***Token Endpoint** – An endpoint at which the token will be validated by your OAuth provider
-            * **Allowed Scopes** – Allowed and custom scopes configured on the client from your OAuth provider
-            * **Access Token Validity** – Duration (in seconds) for which the access token is valid
+
+    [//]: # (<!-- markdownlint-disable no-space-in-emphasis -->)
+
+    * For basic authentication, enter the following information:
+        * **Username** – A username for basic authentication into the OData resource in your Mendix application
+        * **Password** – A password for basic authentication into the OData resource in your Mendix application
+    * For OAuth authentication, enter the following information:
+        * **Client ID** – A client ID from your OAuth provider
+        * **Client Secret** – A secret associated with the client from your OAuth provider
+        * **Token Endpoint** – An endpoint at which the token will be validated by your OAuth provider
+        * **Allowed Scopes** – Allowed and custom scopes configured on the client from your OAuth provider
+        * **Access Token Validity** – Duration (in seconds) for which the access token is valid
+
+    [//]: # (<!-- markdownlint-enable no-space-in-emphasis -->)
+
 8. Click **Generate Script**.
 9. Click **Back** to return to the **Details** page.
 10. Click the **Ingestion Configuration** tab to set up your ingestion destination table.
@@ -77,7 +83,7 @@ Once the Mendix Data Loader is deployed, follow these steps to configure and use
 16. Click **Schedule Ingestion Task**.
 17. To view the created task, go to the **Task Management** tab, where you can monitor performed ingestion jobs, suspend or enable the task, or drop it. Currently, only one ingestion task can exist at a time.
 18. Grant the application **USAGE** privilege on a warehouse to enable scheduling of data ingestions. All data ingestions use the same warehouse.
-    You are now redirected to the **Details** page, where you can see the status of the last three ingestionse.
+    You are now redirected to the **Details** page, where you can see the status of the last three ingestions.
 19. To view the ingested data, access the schema specified in the target database within your Snowflake environment.
 
 The ingested data is stored in the target schema of the specified target database, created by the Mendix Data Loader application. This target schema serves as a staging area. After each ingestion, copy the tables from the target schema to the desired database and schema that you want to use to store the ingested data.
@@ -125,7 +131,7 @@ Additionally, you may need to verify custom claims specific to your OAuth provid
 
 ## Setting up the App Client in your OAuth Provider
 
-When setting up the OAuth provider to be able to use it with the Mendix Data Loader, you must specify aredirect URL in order for the authorization server to redirect the user back to the application. The redirect URL from your Snowflake environment has the following format:
+When setting up the OAuth provider to be able to use it with the Mendix Data Loader, you must specify a redirect URL in order for the authorization server to redirect the user back to the application. The redirect URL from your Snowflake environment has the following format:
 
 ```
 https://apps-api.c1.<cloud_region_id>.<cloud>.app.snowflake.com/oauth/complete-secret

content/en/docs/developerportal/portfolio-management/initiatives-overview/_index.md

@@ -151,8 +151,8 @@ Only Portfolio Managers and Contributors from the same company as the portfolio
 
 1. Make sure that [you have linked the Jira project to your portfolio](/developerportal/portfolio-management/integrate-with-jira/#link-jira-project).
 2. At the bottom of the **Epics** section, click **+ Add Jira Epics**.
-2. Select the Jira project to which the epics belong.
-3. Select the Jira epics. You can search by its full key or summary.
+3. Select the Jira project to which the epics belong.
+4. Select the Jira epics. You can search by its full key or summary.
 5. Click **Add** to link the selected epics to the initiative. 
 6. If you need to link epics in other Jira projects to this initiative, repeat the steps from 2 to 5, until you link all the epics. You can link up to a maximum of 20 Jira epics per initiative.
 

content/en/docs/developerportal/portfolio-management/integrate-with-jira.md

@@ -62,19 +62,19 @@ To connect your portfolio to Jira, follow these steps:
      * **Account**: This is the login name (the email address) of a user on the Jira platform with project access rights.
      * **API Token**: This is a valid API token issued by the Jira platform and assigned to the above-mentioned account. For more information on how to get this API token, see [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
 
-5. Click **Next**.
-6. Select the Jira projects you want to link to your portfolio. You can link up to a maximum of 20 Jira projects per portfolio.
+7. Click **Next**.
+8. Select the Jira projects you want to link to your portfolio. You can link up to a maximum of 20 Jira projects per portfolio.
 
     {{< figure src="/attachments/developerportal/portfolio-management/integrate-with-jira/jira-configuration-wizard-page-3.png" >}}
 
-7. Click **Save**.
+9. Click **Save**.
 
 Once the configuration is completed, your portfolio is connected to Jira, and you can see the following:
 
 {{< figure src="/attachments/developerportal/portfolio-management/integrate-with-jira/jira-integration-linked-projects.png" >}}
 
 * A card with the details of your Jira integration and the **Edit Configuration** button, which enables you to [edit the current configuration of the integration](#edit-configuration). 
-* A list with the Jira projects that are linked to this portfolio, which contains the folllowing items:
+* A list with the Jira projects that are linked to this portfolio, which contains the following items:
 
     * Project icon – This is the icon of the linked Jira project.
     * **Name** – This is the name of the linked Jira project.
@@ -99,7 +99,7 @@ If you want to edit your existing Jira configuration, for example to rotate the
 ## Deleting Jira Configuration
 
 {{% alert color="warning" %}}
-If you already have [linked Jira projects](#link-jira-project) to the portoflio, after you delete the Jira configuration, the linked Jira projects will be unlinked from the portfolio automatically.
+If you already have [linked Jira projects](#link-jira-project) to the portfolio, after you delete the Jira configuration, the linked Jira projects will be unlinked from the portfolio automatically.
 {{% /alert %}}
 
 To delete a configuration, do the following steps:
@@ -144,4 +144,4 @@ If you already have [linked epics from the Jira project to an initiative](/devel
 
     {{< figure src="/attachments/developerportal/portfolio-management/integrate-with-jira/warning-jira-project-unlink.png" >}}
 
-4. Click **Unlink** to confirm your action.
+5. Click **Unlink** to confirm your action.

content/en/docs/refguide/installation/install.md

@@ -89,7 +89,7 @@ The Mendix Studio Pro installation experience includes all the tools and framewo
 
 It is possible to prepare the prerequisite installers beforehand so the setup process can pick them up instead of downloading them from the remote location. Follow these steps to prepare the installers:
 
-5. Rename the following dependencies:
+1. Rename the following dependencies:
     * Rename the Visual C++ Redistributable for Visual Studio 2019 (x64) executable (for example, *VC_redist.x64.exe*) to*vcredist2019_x64.exe*
     * Rename the `latest` executable to *mendix_native_mobile_builder.exe*
     * Rename the *Git-{version}-64-bit.exe* executable to *git_for_windows_installer.exe*
@@ -101,7 +101,7 @@ It is possible to prepare the prerequisite installers beforehand so the setup pr
     * For Studio Pro versions 10.11.0 and above, rename the Java Development Kit 21 (x64) *msi* (for example, *OpenJDK21U-jdk_x64_windows_hotspot_21.0.4_7.msi*) to *adoptiumjdk_21_x64.msi*
     * Do not rename the Microsoft Edge WebView2 Evergreen Runtime installer *MicrosoftEdgeWebview2Setup.exe*; keep it as is
 
-6. Run the installer as described in the [Installing Mendix Studio Pro](#install) section above.
+2. Run the installer as described in the [Installing Mendix Studio Pro](#install) section above.
 
 If an error occurs during JDK installation, try the following:
 

content/en/docs/refguide/modeling/integration/use-extensions/use-the-external-database-connector.md

@@ -153,7 +153,7 @@ Do the following:
 
    b. If **Update Entity** is selected, you can see changes that will be made to the existing entity. Click **Update Entity** to save the query and the changes made to the entity in the domain model.
 
-        {{< figure src="/attachments/refguide/modeling/integration/use-the-external-database-connector/5b.png" width="600" >}}
+    {{< figure src="/attachments/refguide/modeling/integration/use-the-external-database-connector/5b.png" width="600" >}}
 
 ## Call Stored Procedure
 

content/en/docs/support/submit-support-request.md

@@ -90,9 +90,8 @@ To submit a request with Mendix Support, follow these steps:
 6. Fill in the other fields for the issue type you selected, including [Priority](#request-priority).
 7. Optionally, enable the check box that grants Mendix Support permission to access your logs for the purpose of diagnosing and troubleshooting the issue.
 
-{{% alert color="info" %}}
-Although not required, granting this permission is highly recommended because it greatly enhances Mendix Support's ability to assist you effectively. Without it, diagnosing and resolving any issues you encounter may be challenging, potentially impacting the level of support that Mendix Support can provide. Any logs collected are strictly used for providing help on your ticket and are handled with the utmost care. 
-{{% /alert %}}
+    {{% alert color="info" %}}Although not required, granting this permission is highly recommended because it greatly enhances Mendix Support's ability to assist you effectively. Without it, diagnosing and resolving any issues you encounter may be challenging, potentially impacting the level of support that Mendix Support can provide. Any logs collected are strictly used for providing help on your ticket and are handled with the utmost care. 
+    {{% /alert %}}
 
 8. Make sure all your attachments have finished uploading before clicking **Next**.