diff --git a/src/connections/destinations/catalog/actions-topsort/index.md b/src/connections/destinations/catalog/actions-topsort/index.md
index a557381d12..ba2f81f42b 100644
--- a/src/connections/destinations/catalog/actions-topsort/index.md
+++ b/src/connections/destinations/catalog/actions-topsort/index.md
@@ -10,7 +10,6 @@ Setting up an events integration is one of the 3 steps to integrate with Topsort
 
 This destination is maintained by Topsort. For any issues with the destination, [contact the Topsort Support team](mailto:support@topsort.com){:target="_blank"}.
 
-
 ## Getting started
 
 ### Intro to Topsort Events
@@ -21,11 +20,10 @@ This destination helps you track the 3 main events Topsort needs to serve the mo
 - **Click**: If the user then clicks or adds the promoted product to a cart, you should trigger a `click` event.
 - **Purchase**: When an order is completed and confirmed to be successful, report a `purchase` event to Topsort. You can report a purchase whether it has promoted products or not. Topsort takes care of filtering relevant promoted products inside the completed order given the information about promoted clicks.
 
-This destination has 3 default presets that map the Track events `'Product Viewed'`, `'Product Clicked'` and `'Order Completed'` to Topsort's `impression`, `click` and `purchase` events, respectively. If you’re not familiar with the Segment Spec, take a look to understand what the [Track method](/docs/connections/spec/track/) does. 
+This destination has 3 default presets that map the Track events `'Product Viewed'`, `'Product Clicked'` and `'Order Completed'` to Topsort's `impression`, `click` and `purchase` events, respectively. If you’re not familiar with the Segment Spec, take a look to understand what the [Track method](/docs/connections/spec/track/) does.
 
 The mappings in the Topsort destination are built based on the Segment [Ecommerce Spec](/docs/connections/spec/ecommerce/v2/). If you have different Segment Track events mapped to these action definitions, then Topsort can adapt this destination to your case. Once the destination is configured, activate only the mappings relevant to your site. See point 5 of the [set up](#set-up-your-topsort-destination) for more details.
 
-
 ### Set up your Topsort destination
 
 1. From the Segment web app, click **Catalog**, then click **Destinations**.
@@ -35,6 +33,7 @@ The mappings in the Topsort destination are built based on the Segment [Ecommerc
 5. Enable only the Track events relevant to your site and so that the events do not get duplicated with a single user action. For example, if you always trigger a `Product Clicked` event together with the `Product Added` event when a user makes a click in the "Add to cart" button, then you should enable only the `Product Clicked` event for the Topsort Destination.
 
 {% include components/actions-fields.html %}
+
 ### Track
 
 You don't need to change anything about the way you report Track events to Segment. The only extra field you need to provide, only for the `impression` and `click` events, is the `resolvedBidId` given in the winner promoted product (whether it is from the [Auctions API](https://docs.topsort.com/reference/createauctions){:target="_blank"} or the [proxy](https://docs.topsort.com/reference/listings-low-code){:target="_blank"} response). Please find below an example call to track a product listing page (PLP) click event with the `resolvedBidId` included: