chore: fixes segment serialization batch 4.1

Author: carlota-moh

src/connections/sources/catalog/libraries/server/node/index.md

@@ -404,7 +404,7 @@ const onExit = async () => {
 ```
 
 ### Collect unflushed events 
-If you need to preserve all of your events in the instance of a forced timeout, even ones that came in after analytics.flush({ close: true }) was called, you can still collect those events by using:
+If you need to preserve all of your events in the instance of a forced timeout, even ones that came in after `analytics.flush({ close: true })` was called, you can still collect those events by using:
 
 ```javascript
 const unflushedEvents = []

src/connections/spec/common.md

@@ -278,7 +278,7 @@ The `sentAt` timestamp specifies the clock time for the client's device when the
 
 **Note**: The `sentAt` timestamp is not useful for any analysis since it's tainted by user's clock skew.
 
-> warning "Segment now adds `sentAt` to a payload when the batch is complete and initially tried to the Segment API for the Swift, Kotlin, and C# mobile libraries"
+> warning "Segment now adds sentAt to a payload when the batch is complete and initially tried to the Segment API for the Swift, Kotlin, and C# mobile libraries"
 > This update changes the value of the Segment-calculated `timestamp` to align closer with the `receivedAt` value rather than the `originalTimestamp` value. For most users who are online when events are sent, this does not significantly impact their data. However, if your application utilizes an offline mode where events are queued up for any period of time, the `timestamp` value for those users now more closely reflects when Segment received the events rather than the time they occurred on the users' devices. 
 
 

src/engage/audiences/linked-audiences-iterable.md

@@ -71,6 +71,7 @@ In Iterable, do the following:
 ![A screenshot of the test event page](/docs/engage/images/send-test-event.png) 
 
 If the event is sent successfully to Iterable, you will see a `“message”: “success”` response in Segment.
+
 2. Open Iterable and check the [Campaign tab in Messaging Insights](https://support.iterable.com/hc/en-us/articles/360052814452-Messaging-Insights#viewing-metrics){:target="_blank"} (Insights > Messaging Insights > Campaigns > _[Your Unique Campaign])_ to confirm that Iterable has sent the message. 
 3. If your email doesn’t look the way you want it to, adjust the [Handlebars syntax](https://support.iterable.com/hc/en-us/articles/205480365-Personalizing-Templates-with-Handlebars#referencing-user-profile-and-event-fields-with-handlebars){:target="_blank"} in Iterable, and send another test event. See the following [personalization examples](#handlebars-examples-to-use-in-iterable){:target="_blank"} for more specific details. 
 4. When you’re finished testing your campaign, proceed to [Enable your Linked Audience](/docs/engage/audiences/linked-audiences/#step-4-enable-your-linked-audience).

src/engage/campaigns/email-campaigns.md

@@ -76,7 +76,7 @@ Follow these steps to test your campaign:
 
 1. In the **Send an email** pane, navigate to Body, then click **Test email**.
 2. If your template has profile traits, enter a trait value for the test email. This ensures that your merge tags work as expected.
-- To test a default value, leave the profile traits field blank. Default values must be assigned in your merge tags. For example, `loyal customer` would be the default for the following merge tag: {% raw %}```{{profile.traits.first_name | default: "loyal customer"}}```{% endraw %}.
+        - To test a default value, leave the profile traits field blank. Default values must be assigned in your merge tags. For example, `loyal customer` would be the default for the following merge tag: {% raw %}```{{profile.traits.first_name | default: "loyal customer"}}```{% endraw %}.
 3. In the **Recipients** field, enter the email address(es) that will receive your test email.
 4. Click **Send test email**.
 

src/engage/campaigns/sms-campaigns.md

@@ -60,7 +60,7 @@ Follow these steps to test your campaign:
 
 1. In the **Send an SMS** pane, click **Test SMS**.
 2. If your template has profile traits, enter a trait value for the test SMS. This ensures that your merge tags work as expected.
-- To test a default value, leave the profile traits field blank. Default values must be assigned in your merge tags. For example, `loyal customer` would be the default for the following merge tag: {% raw %}```{{profile.traits.first_name | default: "loyal customer"}}```{% endraw %}.
+    - To test a default value, leave the profile traits field blank. Default values must be assigned in your merge tags. For example, `loyal customer` would be the default for the following merge tag: {% raw %}```{{profile.traits.first_name | default: "loyal customer"}}```{% endraw %}.
 3. In the **Recipients** field, enter the phone number(s) that will receive your test SMS.
 4. Click **Send test SMS**.
 

src/engage/content/email/template.md

@@ -44,10 +44,10 @@ You can send test emails before you include a template in marketing campaigns.
 1. Select the email template you want to test on the Templates screen.
 2. From the Template Settings page, click **Test email**.
 3. If your template has profile traits, enter a trait value for the test email. This ensures that your merge tags work as expected.
-- To test a default value, leave the profile traits field blank. Default values must be assigned in your merge tags. For example, `loyal customer` would be the default for the following merge tag: {% raw %}```{{profile.traits.first_name | default: "loyal customer"}}```{% endraw %}.
-- To test traits with arrays, you must input the array in JSON format. For example, `[“item1”, “item2”]` or `[{“itemName”: “shoes”}]`. If you don't use JSON format for arrays in the test message side sheet, your template might not render as expected. 
+    - To test a default value, leave the profile traits field blank. Default values must be assigned in your merge tags. For example, `loyal customer` would be the default for the following merge tag: {% raw %}```{{profile.traits.first_name | default: "loyal customer"}}```{% endraw %}.
+    - To test traits with arrays, you must input the array in JSON format. For example, `[“item1”, “item2”]` or `[{“itemName”: “shoes”}]`. If you don't use JSON format for arrays in the test message side sheet, your template might not render as expected. 
 4. Enter recipient email addresses for the test message.
-- Profiles that you send test messages to must have a userId in Segment.
+    - Profiles that you send test messages to must have a userId in Segment.
 5. Select **Send test email**.
 
 {% comment %} 
@@ -73,7 +73,7 @@ Engage supports dynamic sending using merge tags. Personalize email content by a
 As you configure the template, click **Merge Tags** and select the profile traits to include. Engage inserts the merge tags based on cursor placement.
 
 > success ""
-> - For all merge tags, you must add a `default` value inside a single quote. For example: {% raw %}`{{profile.traits.traits | default: 'Default'}}`{% endraw %}
+> - For all merge tags, you must add a `default` value inside a single quote. For example: `{{profile.traits.traits | default: 'Default'}}`
 > - Only use variable tags in [liquid sytax](https://liquidjs.com/tags/overview.html){:target="blank"}.
 
 The following table contains a description and some best practices for all fields in the email template. Asterisks indicate required fields.