chore: Fix table

Author: CristhianMotoche

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/trubrics/index.md

@@ -19,7 +19,7 @@ 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 --->