Merge pull request #7026 from segmentio/moloco-info-box-fix

Fix info/notes box sections that have wrong spacing

Author: forstisabella

src/connections/destinations/catalog/actions-moloco-rmp/index.md

@@ -42,7 +42,7 @@ analytics.identify('361b1fdfbeaa9d64a13c033eb9f970dc6740f6bc', {
 Once a user is identified, each call to Segment's [Track method](/docs/connections/spec/track/) automatically records the user ID.
 Users that are not logged in can be tracked using an [anonymousID](/docs/connections/spec/identify/#anonymous-id). Moloco Commerce Media does not use anonymousIDs for users that are not logged in. Segment recommends formatting your anonymousID in UUID format.
 
-> info" "
+> info " "
 > If you hash the user ID before sending it to Moloco, ensure you reuse the same hashed ID when calling other Moloco APIs.
 
 

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

@@ -54,10 +54,11 @@ For example, you might send a letter in which you need to include the recipient'
 If you aren't familiar with the Segment Spec, see the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call with Inkit would look like:
 
 
-> note""
-> All address elements should be satisified within the segment's user identity
-(exception of address_line_2 which is a custom entry)
-Expected Requirements
+> note " "
+> All address elements should be satisfied within the Segment's user identity, with the (exception of address_line_2 which is a custom entry).
+
+
+Expected Requirements:
 
 ```js
 analytics.identify('userId123', {

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

@@ -3,21 +3,18 @@ title: Retina AI Destination
 rewrite: true
 id: 5f287bfa332cce0b1ed18331
 ---
-# Retina AI Segment Destination
 
 [Retina AI](https://retina.ai/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} is a customer intelligence partner that provides accurate **customer-level lifetime value** metrics at or before their first transaction. You can use this to improve targeting, ad relevance, conversion rates, and customer loyalty.
 
 Retina AI maintains this destination. For any issues with the destination, contact the [Retina AI Support Team](mailto:info@retina.ai).
 
-> note"
+> info " "
 > The Retina AI Destination is in beta, which means that they are still actively developing the destination. To join the beta program, or if you have any feedback to help improve the Retina AI Destination and its documentation, contact the [Retina AI Support Team](mailto:info@retina.ai).
 
 
 ## Getting Started
 
-
-
-To integrate Retina AI with Segment as a **Destination**:
+To integrate Retina AI with Segment as a destination:
 1. From your Segment UI's Destinations page click on “Add Destination”.
 2. Search for “Retina” in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. Add the “API Key” that Retina AI provides through a secure data transfer to your Segment workspace.
@@ -87,5 +84,3 @@ If you aren't familiar with the Segment Spec, take a look at the [Alias method d
 ```js
 analytics.alias("507f191e81");
 ```
-
----

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

@@ -16,7 +16,7 @@ This destination is maintained by Userlist. For any issues with the destination,
 2.  Search for "Userlist" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3.  In the Userlist Segment destination settings, enter your Userlist "Push API Key". You can find this key in your [Userlist Push API settings](https://app.userlist.com/settings/push){:target="_blank"}.
 
-> info""
+> info ""
 > **NOTE:** The Userlist Destination does not support tracking anonymous users, and returns a 400 error if you send `track` or `group` call for unidentified users. To prevent this, make sure you make an Identify call before you make Track or Group calls. You can also disregard this error if you sent calls you do not intend Userlist to process.
 
 ## Identify