Merge pull request #8100 from segmentio/DOCSPLAT-3056-fixes-1

DOCSPLAT 3056 Simplify serialization

Author: rchinn1

src/connections/destinations/catalog/optimizely-web/index.md

@@ -135,7 +135,7 @@ This appends an additional property in your "Experiment Viewed" events called `n
 
 #### Sending Experiment Viewed event properties as Google Analytics Custom Dimensions
 
-If you're sending your experiment data to Google Analytics in the form of `track` calls, Segment recommends creating hit-scoped custom dimensions in Google Analytics with titles like "Experiment Name" and "Variation Name," and then map the properties to those Custom Dimensions accordingly. For example, if you set Custom Dimension 5 to "Experiment Name" and Custom Dimension 1 to "Variation Name," here's how you'd configure the mappings in your Segment<>GA settings:
+If you're sending your experiment data to Google Analytics in the form of `track` calls, Segment recommends creating hit-scoped custom dimensions in Google Analytics with titles like "Experiment Name" and "Variation Name," and then map the properties to those Custom Dimensions accordingly. For example, if you set Custom Dimension 5 to "Experiment Name" and Custom Dimension 1 to "Variation Name," here's how you'd configure the mappings in your Segment\<>GA settings:
 
   ![A screenshot of the Custom Dimensions tab of Optimizely.](images/customdimensions.png)
 
@@ -195,7 +195,7 @@ If you are sending anonymous data to Optimizely X Full Stack using their server-
 
 ### No Data for Anonymous Users
 
-Segment does not map any data to Optimizely from the Segment<>Optimizely Web destination for anonymous users - in other words, to map `track` and `page` data, a user must be `identified` with a `userId`.
+Segment does not map any data to Optimizely from the Segment\<>Optimizely Web destination for anonymous users - in other words, to map `track` and `page` data, a user must be `identified` with a `userId`.
 
 ### Lower Experiment Viewed counts inside Segment and other tools vs. Optimizely unique visitors
 

src/connections/destinations/catalog/personas-facebook-custom-audiences/index.md

@@ -110,7 +110,8 @@ Once created, the audience should be available in Facebook in ten minutes unless
 [Trait Enrichment](/docs/engage/trait-activation/trait-enrichment/) allows you to send an expanded list of identifiers or traits to Facebook, so that Facebook can try to use these additional data points to match to their user profiles. If you have this feature enabled and implemented any of these traits in your Segment tracking, Engage can send this data to Facebook. Segment can now also sync multiple emails if the profile contains more than one. Additionally as part of this feature, Segment hashes fields before sending them downstream to Facebook, if required. (See the table below for hashing requirements.) Note that the trait data implemented in your Segment tracking must match the naming convention and format specified in the table below, otherwise Segment can't send it to Facebook.
 
 
-| **Name**        | **Trait Key formats supported**   | **Facebook Keys**  | **FB Hashing Required** | **FB Guidelines**     |
+| **Name**    | **Trait Key formats supported**                              | **Facebook Keys**  | **FB Hashing Required** | **FB Guidelines**     |
+| ----------- | ------------------------------------------------------------ | -------------------- | ----------------------- | --------------------- |
 | Email       |                                                              | EMAIL                | Yes (Segment does the hashing for you. In case you are *already* hashing emails, emails will get sent to Facebook double-hashed. Facebook will still match on double-hashed emails, but this is *not* recommended.                  | Trim leading, trail whitespace, and convert all characters to lowercase.                                                                                  |
 | Mobile ID   |                                                              | MADID                | No                  | Use all lowercase, keep hyphens.                                                                                                                          |
 | First Name  | first_name<br>firstname<br>firstName<br>first                | FN                   | Yes                 | Use `a`-`z` only. Lowercase only, no punctuation. Special characters in UTF8 format.                                                                      |

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

@@ -32,7 +32,7 @@ For purchase events, you should send an event called `Order Completed` per our s
 
 ### Features
 #### Labels
-When you call `page`, `track` or `screen`, we'll pass the page name, event name or screen name and the category (if provided) to Quantcast as a label. The standard label will look like this "<title>" for page or screen, and "<name>" for track events. If you enable Quantcast for advertisers then we'll send "_fp.event.<name>" to match Quantcast's internal data structures for advertisers. If you do not pass any `category` or `name` for a `.page()` call, we will fallback on Quantcast's default label.
+When you call `page`, `track` or `screen`, we'll pass the page name, event name or screen name and the category (if provided) to Quantcast as a label. The standard label will look like this "\<title>" for page or screen, and "\<name>" for track events. If you enable Quantcast for advertisers then we'll send "_fp.event.\<name>" to match Quantcast's internal data structures for advertisers. If you do not pass any `category` or `name` for a `.page()` call, we will fallback on Quantcast's default label.
 
 Here's an example for Quantcast Advertisers:
 

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

@@ -19,8 +19,8 @@ This destination is maintained by Trubrics. For any issues with the destination,
 4. Go to the [Trubrics app](https://app.trubrics.com){:target="_blank"}, and copy the **Project API key** from the settings page.
 5. Enter the **Project API Key** in the Trubrics destination settings in Segment, then enable the destination.
 6. Add mappings for your AI/user properties.
- - To learn more about adding mappings, see [Trubrics <> Segment Mapping Events](https://www.loom.com/share/3bc3a02cf38d47b4b865c50314dbc8fb){:target="_blank”}.
+  - To learn more about adding mappings, see [Trubrics \<> Segment Mapping Events](https://www.loom.com/share/3bc3a02cf38d47b4b865c50314dbc8fb){:target="_blank”}.
 
  <!--- TODO: write this instead of having it in a video --->
 
-{% include components/actions-fields.html %}
+{% include components/actions-fields.html %}

src/connections/functions/destination-functions.md

@@ -371,7 +371,7 @@ async function getAccessToken () {
 
 ### Functions permissions
 
-{% include content/functions/perms.md%}
+{% include content/functions/perms.md %}
 
 
 ### Editing and deleting functions

src/connections/functions/environment.md

@@ -119,7 +119,7 @@ View Segment's [Public API](https://docs.segmentapis.com/tag/Functions){:target=
 
 ## Functions permissions
 
-{% include content/functions/perms.md%}
+{% include content/functions/perms.md %}
 
 ## ️Settings and secrets
 

src/connections/functions/insert-functions.md

@@ -480,7 +480,7 @@ You can view Segment's list of [Integration Error Codes](/docs/connections/integ
 
 ### Functions permissions
 
-{% include content/functions/perms.md%}
+{% include content/functions/perms.md %}
 
 
 ### Editing and deleting functions

src/connections/functions/source-functions.md

@@ -391,7 +391,7 @@ Segment only attempts to run your source function again if a **Retry** error occ
 ### Source functions permissions
 
 
-{% include content/functions/perms.md%}
+{% include content/functions/perms.md %}
 
 
 ### Editing and deleting source functions

src/connections/sources/catalog/cloud-apps/autopilothq/index.md

@@ -50,8 +50,7 @@ Additionally, Autopilot also sends `email` and `contact_id` under `context.trait
   </tr>
   <tr>
    <td>Email Marked as Spam</td>
-   <td>Recipient marked message as spam
-  </td>
+   <td>Recipient marked message as spam</td>
   </tr>
   <tr>
    <td>Email Opened</td>

src/connections/sources/catalog/cloud-apps/blueshift/index.md

@@ -12,7 +12,7 @@ In your favorite BI or analytics tool, you'll be able to analyze your email camp
 
 ## Getting Started
 
-1. From your workspace's segment.com/<your-workspace>/sources page, click Add source.
+1. From your workspace's segment.com/\<your-workspace>/sources page, click Add source.
 2. Choose Blueshift.
 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you'd like, but we recommend sticking to something that reflects the Source itself, like Blueshift for nickname and Blueshift for the schema name.
 4. The next page ("Overview") will surface your Segment write key for Blueshift. Copy this write key.