Lint fix

Author: OlufunkeMoronfolu

content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/services-not-included.md

@@ -10,11 +10,11 @@ description: "Describes how to use Teamcenter services that are not included in
 
 The Teamcenter connector provides two APIs for calling any service operation that is part of Teamcenter Services.
 
-* **CallTeamcenterService** — Java action
+* **CallTeamcenterService** – Java action
 
   This Java action can be used directly in any microflow and maps the Mendix domain entities to or from the JSON data structures that are used by Teamcenter Services operations.
 
-* **TcConnection.callTeamcenterService** — Java method
+* **TcConnection.callTeamcenterService** – Java method
 
   This Java method can only be used from within the Java code and requires that the caller create and parse JSONObjects directly for the call. The **TcConnector** class also exposes an entity version of the **callTeamcenterService** method that matches the Java action.
 
@@ -178,7 +178,7 @@ Following is the operation mapping file for createWorkflow SOA call:
 
 Mendix Domain Model entities are mapped to Teamcenter service operation data structures based on naming conventions. The Teamcenter structure element names (keys in JSON document) map one-to-one to the entity member (attributes or associations) names, with the following caveats:
 
-* The entity member name is prefixed with an underscore '_', for example '*type'. In this case the '*' is ignored, thus matching the Teamcenter name of 'type'.
+* The entity member name is prefixed with an underscore '\_', for example '\_type'. In this case the '\_' is ignored, thus matching the Teamcenter name of 'type'.
 * The entity member name is suffixed with '__XXX', for example, 'phone__Home'. In this case the '__Home' is ignored, thus matching the Teamcenter name of 'phone'.
 
 When traversing entities across associations, the entity names are not used. Only the associations between entities must match or be mappable.

content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-connector/teamcenter-configuration-guide.md

@@ -31,9 +31,9 @@ Follow these steps to connect your Mendix app to Teamcenter:
 1. Log in to your Mendix app with the **Administrator** user role.
 2. Use the **NAV_AdminHomePage** button to navigate to the overview page of all Teamcenter configurations.
 
-{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-connector/configuration/teamcenter-new-configuration.png">}}
+    {{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-connector/configuration/teamcenter-new-configuration.png">}}
 
-1. Click **+ New configuration** to create a new configuration.    
+3. Click **+ New configuration** to create a new configuration.    
     All configurations require the following fields:
 
     * **Configuration Name** – A unique identifier for the configuration. This can be used in a subsequent microflow to identify which environment to connect to.
@@ -48,7 +48,7 @@ Follow these steps to connect your Mendix app to Teamcenter:
 
     If your Teamcenter instance is using SSO, additional steps are required. Follow the steps in the [Teamcenter SSO](#teamcenter-sso) and [Teamcenter X SSO](#teamcenter-x-sso) sections before continuing.
 
-2. Click **Save**.
+4. Click **Save**.
 
 ### Testing the Connection {#test-the-connection}
 

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

@@ -68,7 +68,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/marketplace/platform-supported-content/services/event-broker.md

@@ -170,14 +170,12 @@ The creation process for AWS SQS bridges includes two additional steps on the Me
 #### Configure Service
 
 1. Configure the service by filling out the following:
+    * **Event Broker Space** – the space where the bridge will operate
+    * **Name** – the name you want to call the bridge
+    * **AWS region** – the AWS region where your bridge operates
+    {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/aws-sqs/ebb_aws_sqs_configure.png" width="400" >}}
 
-* **Event Broker Space** – the space where the bridge will operate
-* **Name** – the name you want to call the bridge
-* **AWS region** – the AWS region where your bridge operates
-
-  {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/aws-sqs/ebb_aws_sqs_configure.png" width="400" >}}
-
-1. Click **Next** to continue the configuration.
+2. Click **Next** to continue the configuration.
 
 #### Connect Events
 
@@ -258,13 +256,13 @@ Add the object below to your Access Policy of the AWS SQS queue if it is receivi
 
 1. Configure the service by filling out the following:
 
-* **Event Broker Space** – the space where the bridge will operate
-* **Name** – the name you want to call the bridge
-* **AWS region** – the AWS region where your bridge operates
+    * **Event Broker Space** – the space where the bridge will operate
+    * **Name** – the name you want to call the bridge
+    * **AWS region** – the AWS region where your bridge operates
 
-  {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/ebb_http_configure.png" width="400" >}}
+    {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/ebb_http_configure.png" width="400" >}}
 
-1. Click **Next** to connect events to your bridge.
+2. Click **Next** to connect events to your bridge.
 
 #### Connect Events
 
@@ -296,15 +294,15 @@ To run the HTTP bridge from your client, include a Bearer token in the request h
 
 1. Configure the service by filling out the following:
 
-* **Event Broker Space** – the space where the bridge will operate
-* **Name** – the name you want to call the bridge
-* **Storage Account** – the storage account to access
-* **Storage SAS Token** – the storage SAS Token
-* **Container Path** – the path of the container where the messages will be stored
+    * **Event Broker Space** – the space where the bridge will operate
+    * **Name** – the name you want to call the bridge
+    * **Storage Account** – the storage account to access
+    * **Storage SAS Token** – the storage SAS Token
+    * **Container Path** – the path of the container where the messages will be stored
 
     {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/azure-blob-storage/ebb_azure_blob_configure.png" >}}
 
-1. Click **Next** to connect events to your bridge.
+2. Click **Next** to connect events to your bridge.
 
 #### Connect Events
 
@@ -329,20 +327,18 @@ Once the Mendix Event Broker Bridge has been successfully deployed, its configur
 
 1. Configure the service by filling out the following:
 
-* **Event Broker Space** – the space where the bridge will operate
-* **Name** – the name you want to call the bridge
-* **Bucket** – the path of the container where the messages will be stored
-* **AWS Region for Bucket** – the AWS region where your S3 bucket is located
-* **AWS Role (to Assume)** – the Amazon Resource Name (ARN) of the IAM role that the Event Broker Bridge will assume to access your S3 bucket; this role must be configured with appropriate permissions and a trust policy allowing the Event Broker to assume it
-* **AWS Role's External Id** – a unique identifier that provides additional security when the Event Broker assumes your AWS role; this shared secret ensures that only authorized Mendix Event Broker instances can assume the role
+    * **Event Broker Space** – the space where the bridge will operate
+    * **Name** – the name you want to call the bridge
+    * **Bucket** – the path of the container where the messages will be stored
+    * **AWS Region for Bucket** – the AWS region where your S3 bucket is located
+    * **AWS Role (to Assume)** – the Amazon Resource Name (ARN) of the IAM role that the Event Broker Bridge will assume to access your S3 bucket; this role must be configured with appropriate permissions and a trust policy allowing the Event Broker to assume it
+    * **AWS Role's External Id** – a unique identifier that provides additional security when the Event Broker assumes your AWS role; this shared secret ensures that only authorized Mendix Event Broker instances can assume the role
 
-{{% alert color="info" %}}
-For detailed instructions on how to create the IAM role and obtain these values, see [Configure AWS Authentication for S3 Bridge](#configure-aws-s3-authentication).
-{{% /alert %}}
+        {{% alert color="info" %}}For detailed instructions on how to create the IAM role and obtain these values, see [Configure AWS Authentication for S3 Bridge](#configure-aws-s3-authentication).{{% /alert %}}
 
-{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/aws-s3/ebb_aws_s3_configure.png"  >}}
+    {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/aws-s3/ebb_aws_s3_configure.png"  >}}
 
-1. Click **Next** to connect events to your bridge.
+2. Click **Next** to connect events to your bridge.
 
 #### Connect Events
 
@@ -489,7 +485,7 @@ To edit a bridge:
 **AWS S3** 
     {{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/edit-bridge/ebb_aws_s3_edit_mode.png" class="no-border" >}}
 
-1. Once you have made your changes, you can:
+4. Once you have made your changes, you can:
    * Click **Apply** to save and apply the changes. A confirmation message will indicate if the changes were successful. Changes to the event configuration take effect when applied. After applying changes, the bridge status will change to **Reconfiguring** and will return to **Running** once the reconfiguration is complete.
    * Click **Cancel** to exit editing mode without saving any changes.