Fix formatting issues in linter

Author: OlufunkeMoronfolu

content/en/docs/control-center/security/policies.md

@@ -43,45 +43,45 @@ You can create a policy by defining your own details.
 
 2. On the **Policy Definition** tab, fill in the following details:
 
-* **Policy Name** – A relevant name for your policy, such as one indicating what the policy checks.
-* **Description** – A description of the goal of the policy, which covers why it needs to be adhered to, and how to fix its violations.
-* **Policy Conditions** – Define the conditions under which the policy is considered violated. These are the available conditions and their values:
+    * **Policy Name** – A relevant name for your policy, such as one indicating what the policy checks.
+    * **Description** – A description of the goal of the policy, which covers why it needs to be adhered to, and how to fix its violations.
+    * **Policy Conditions** – Define the conditions under which the policy is considered violated. These are the available conditions and their values:
 
-    * **Any finding severity is** – Choose which severity level violates the policy. You can select one or more of the following values:
+        * **Any finding severity is** – Choose which severity level violates the policy. You can select one or more of the following values:
 
-        * **LOW**
-        * **MEDIUM**
-        * **HIGH**
-        * **CRITICAL**
+            * **LOW**
+            * **MEDIUM**
+            * **HIGH**
+            * **CRITICAL**
 
-        For example, if you select **CRITICAL**, apps with critical findings violate this policy.
+            For example, if you select **CRITICAL**, apps with critical findings violate this policy.
 
-    * **Mendix runtime version is lower than** – Indicate which Mendix version is the minimum that your apps must use.
+        * **Mendix runtime version is lower than** – Indicate which Mendix version is the minimum that your apps must use.
 
-    * **Marketplace component license is not** – Select the licenses that are acceptable. If a Marketplace component has a license which is not one of the ones you select here, the policy is violated. These are the possible values:
+        * **Marketplace component license is not** – Select the licenses that are acceptable. If a Marketplace component has a license which is not one of the ones you select here, the policy is violated. These are the possible values:
 
-        * MIT
-        * BSD_2_0
-        * APACHE_V2
-        * APACHE_1_0
-        * MENDIX_EULA
-        * PARTNER_LICENSES
-        * CREATIVE_COMMONS_CC0
-        * GNU_GENERAL_PUBLIC_LICENSE_V3
-        * MENDIX_MARKETPLACE_CONTENT_TERMS
+            * MIT
+            * BSD_2_0
+            * APACHE_V2
+            * APACHE_1_0
+            * MENDIX_EULA
+            * PARTNER_LICENSES
+            * CREATIVE_COMMONS_CC0
+            * GNU_GENERAL_PUBLIC_LICENSE_V3
+            * MENDIX_MARKETPLACE_CONTENT_TERMS
 
-    * **Marketplace component support is not** – Select the support types that are acceptable. If a Marketplace component has a support type which is not one of the ones you select here, the policy is violated. These are the possible values:
+        * **Marketplace component support is not** – Select the support types that are acceptable. If a Marketplace component has a support type which is not one of the ones you select here, the policy is violated. These are the possible values:
 
-        * PARTNER
-        * SIEMENS
-        * PLATFORM
-        * COMMUNITY
+            * PARTNER
+            * SIEMENS
+            * PLATFORM
+            * COMMUNITY
 
-* **Checkpoints & Action(s)** – Select the trigger which causes the policy to be checked, and the action that is taken if the policy is violated. Currently, policy violations are checked at the time of package creation, and violations generate warnings.
+    * **Checkpoints & Action(s)** – Select the trigger which causes the policy to be checked, and the action that is taken if the policy is violated. Currently, policy violations are checked at the time of package creation, and violations generate warnings.
 
-1. On the **Policy Scope** tab, select whether you want the policy to apply to all licensed apps, or only to specific apps in your environment.
+3. On the **Policy Scope** tab, select whether you want the policy to apply to all licensed apps, or only to specific apps in your environment.
 
-2. Select one of these actions:
+4. Select one of these actions:
 
     * **Cancel** – Discard the policy.
     * **Save as Inactive** – Save the policy, but do not enforce it yet.

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

@@ -76,7 +76,7 @@ If you want to use specific resources, you should instead expose a new endpoint
 9. Click **Back** to return to the **Details** page.
 10. Click the **Ingestion Configuration** tab to set up your ingestion destination table.
 11. Click **Create** to start setting up the Ingestion Configuration.
-    ***Target Database** – Name of the database for data ingestion
+    * **Target Database** – Name of the database for data ingestion
     * **Target Schema** – Target schema where all data will be ingested
 12. Click **Save**.
 13. Click the **Data Ingestion** tab, where you can start your data ingestion or set up a schedule.

content/en/docs/workstation/management/wks-monitoring.md

@@ -18,16 +18,15 @@ You can access the Usage Reports by performing the following steps:
 
 1. To view the reports for all workspaces that you own or administer, go to Workstation Management, and click **My Usage Report**.
 
-    {{< figure src="/attachments/workstation/wks-usage1.png" class="no-border" >}}
+    {{< figure src="/attachments/workstation/wks-usage1.png" >}}
 
 2. To view a report for all workspaces that are owned by your company, go to Workstation Management and click **Company Usage Report**. 
 
-{{% alert color="info" %}}
-The **Company Usage Report** tab is accessible only to users who have the Mendix Admin role assigned in [Control Center](/control-center/).
-{{% /alert %}}
+    {{% alert color="info" %}}The **Company Usage Report** tab is accessible only to users who have the Mendix Admin role assigned in [Control Center](/control-center/).
+    {{% /alert %}}
 
-1. To view the reports for a specific workspace, open the workspace in Workstation Management, and then click **Usage**.
+3. To view the reports for a specific workspace, open the workspace in Workstation Management, and then click **Usage**.
 
-    {{< figure src="/attachments/workstation/wks-usage2.png" class="no-border" >}}
+    {{< figure src="/attachments/workstation/wks-usage2.png" >}}
 
 The Usage Reports display information about the usage trends for each Workstation Client both daily and over time.