chore: fixes for batch 5.1

Author: carlota-moh

src/connections/destinations/catalog/actions-sendgrid-audiences/index.md

@@ -61,15 +61,15 @@ Segment supports sending Engage user profile traits to SendGrid Contact User Att
 
 1. Use [Trait Enrichment](/docs/engage/trait-activation/trait-enrichment/) to include specific user profile traits when syncing users to a SendGrid List. 
 2. Standard User Attributes: Use the [Sync Audience Action](#sync-audience-action)'s User Attributes field to map the following [Contact Profile Fields](https://www.twilio.com/docs/sendgrid/ui/managing-contacts/segmenting-your-contacts#contact-profile-fields){:target="_blank”} to SendGrid:
- - First Name
- - Last Name
- - Phone Number (must be in [E.164](https://www.twilio.com/docs/glossary/what-e164){:target="_blank”} format)
- - Address Line 1
- - Address Line 2
- - City
- - State/Province/Region
- - Country
- - Postal Code
+    - First Name
+    - Last Name
+    - Phone Number (must be in [E.164](https://www.twilio.com/docs/glossary/what-e164){:target="_blank”} format)
+    - Address Line 1
+    - Address Line 2
+    - City
+    - State/Province/Region
+    - Country
+    - Postal Code
 3. Custom User Attributes: Define a custom User Attribute in SendGrid, then use [Sync Audience ](#sync-audience-action) Action to send custom User Attributes to SendGrid using the Custom Fields field. You can only send string, number, and date values to SendGrid with this method.
 
 ### Supported identifiers 

src/connections/destinations/catalog/actions-tiktok-pixel/index.md

@@ -7,7 +7,7 @@ id: 64c1690a9f08c84a420aba78
 
 [TikTok Pixel](https://ads.tiktok.com/marketing_api/docs?id=1739583652957185){:target="_blank"} is a piece of code that you can place on your website that allows you to share website events with TikTok. With TikTok for Business Tools, the Pixel can help you measure traffic on your website, measure ad campaign performance, optimize your campaigns and find new customers.
 
-### Benefits of TikTok Pixel
+## Benefits of TikTok Pixel
 
 Use data collected from TikTok Pixel to:
 - **Build marketing audiences**: Create custom Audiences based on website visitor events, like viewing a product page or making a purchase. Audiences can be used to re-engage previous site visitors or model lookalikes to find new customers. 

src/connections/destinations/catalog/actions-vwo-cloud/index.md

@@ -93,12 +93,12 @@ To integrate Segment with VWO FullStack:
 By adding the VWO Cloud mode destination to your Segment audiences, you can export audiences to your VWO account to target your campaigns in VWO. To achieve this, perform the following steps:
 
 1. Navigate to **Engage > Engage Settings**, and click **Destinations**. 
-- Ensure that you're in the Engage space you plan to use for VWO.
+  - Ensure that you're in the Engage space you plan to use for VWO.
 2. Click **Add Destination**.
 3. Search for “VWO Cloud Mode (Actions)” and select the destination. Click **Add Destination**.
 4. On the **Select Source** screen, you'll see your Engage space selected as the source. Click **Confirm Source**.
 5. Select the VWO Cloud mode destination that you’ve created and navigate to the **Settings** tab. Name your destination and enter your **VWO Account ID**. Toggle **Enable Destination** on and click **Save Changes**.
-- You'll find your VWO account ID at the top of the VWO dashboard.
+  - You'll find your VWO account ID at the top of the VWO dashboard.
 6. Navigate to the **Mappings** tab and click **New Mapping**. Under **PRE-BUILT MAPPINGS**, select **Sync Audience**, then click **Save**.
 7. The **STATUS** of the mapping displays as disabled by default. Enable the mapping using the toggle. 
 8. Navigate to **Engage > Audiences**. Choose an existing Engage audience or create a new one to export to VWO.

src/connections/destinations/catalog/adobe-analytics/settings.md

@@ -46,11 +46,11 @@ The Adobe Analytics destination automatically works with Segment's standard [Eco
   <tr>
     <td>Order Completed</td>
     <td>`purchase`</td>
+  </tr>
   <tr>
     <td>Cart Opened</td>
     <td>`scOpen`</td>
   </tr>
-  </tr>
 </table>
 
 Segment sends the Ecommerce event data to Adobe just as it would send a standard Track event. These Ecommerce events are automatically mapped and sent to Adobe Analytics along with product description data. If you implement Segment events using the Ecommerce spec and naming conventions, you do **NOT** need to create a mapping in your Segment Adobe destination settings. You only need to map **event names** if you want to set them as the value of an `eVar`. To learn more about configuring `eVars` see [the section below on configuring conversion variables in your destination settings.](#conversion-variables---evars)
@@ -357,7 +357,7 @@ The Segment Adobe Analytics Merchandising setting runs as follows:
   If you don't include a value, Segment sends the event without one, and Adobe understands this as an increment of `1`. If you configure a value and the value is not present on the `track` or `page` call, Segment does not send the event to Adobe.
 - Map of product eVars to set on the products string. This is only supported at the product level, as expected by Adobe Analytics. <!-- TODO LR Note: this whole section could use work, but this part is especially confusing-->
 
-> info "Product Added, Product Removed, and Product Viewed events do not use the "products" array"
+> info "Product Added, Product Removed, and Product Viewed events do not use the products array"
 > Product Added, Product Removed, and Product Viewed events store product information in the top level property object rather than in the "products" array. When adding an eVar to these events, specify `properties.key` as the Segment key in the mapping.
 > 
 > For more information, see the [Product Added Spec](/docs/connections/spec/ecommerce/v2/#product-added).

src/connections/destinations/catalog/amplitude/index.md

@@ -97,7 +97,7 @@ When you use the **Track All Pages** setting, Segment sends a `Loaded a Page` ev
 The following settings are available on iOS for device-mode connections.
 
 | Setting Name      | When events will be sent to Amplitude | Amplitude Event Name | Example for `{"name": "Settings", "category": "Merchant" }` |
-| ----------------- | ------------------------------------- | -------------------- |
+| ----------------- | ------------------------------------- | -------------------- | ----------- |
 | Track All Pages   | Always                                | Viewed (Name)        | "Viewed Settings"                                           |
 | Track All Screens | Always                                | Loaded a Screen      | "Loaded a Screen"                                           |
 
@@ -159,7 +159,7 @@ The table below represents default behavior.
 
 | Library     | Default                 | Fallback      |
 | ----------- | ----------------------- | ------------- |
-| A.js        | Generated by Amplitude] | `anonymousId` |
+| A.js        | Generated by Amplitude  | `anonymousId` |
 | Server-side | `context.device.id`     | `anonymousId` |
 | iOS         | Generated by Amplitude  | n/a           |
 | Android     | Generated by Amplitude  | n/a           |
@@ -181,8 +181,8 @@ If you're using the "Prefer Advertising ID for Device ID" setting with one of ou
 
 | Library | Default       | Fallback                |
 | ------- | ------------- | ----------------------- |
-| iOS     | `anonymousId` | [Generated by Amplitude |
-| Android | `anonymousId` | [Generated by Amplitude |
+| iOS     | `anonymousId` | Generated by Amplitude |
+| Android | `anonymousId` | Generated by Amplitude |
 
 ### Device ID priority