Small fixes for batch 3.1 and 3.2

src/_includes/content/generative-audiences-nutrition-facts.html

@@ -104,7 +104,7 @@
                         </td>
                     </tr>
                     <tr class="c4">
-                        <td class="c6" colspan="1" rowspan="1"><p class="c10"><span class="c13">Training Data Anonymized &nbsp; </span>
+                        <td class="c6" colspan="1" rowspan="1"><p class="c10"><span class="c13">Training Data Anonymized</span>
                             <span class="c0 nf-right-align"> N/A</span></p>
                         </td>
                     </tr>
@@ -141,4 +141,4 @@
                         </td>
                     </tr>
              </table>
-        </html>
+        </html>

src/_includes/content/spec-field-screen-name.md

@@ -1,4 +1,4 @@
-_<tr>
+<tr>
   <td markdown="span">`name`</td>
   <td markdown="span">*optional*</td>
   <td markdown="span">String</td>

src/_includes/content/suggested-mappings-nutrition-facts.html

@@ -99,7 +99,7 @@
                         </td>
                     </tr>
                     <tr class="c4">
-                        <td class="c6" colspan="1" rowspan="1"><p class="c10"><span class="c13">Customer Data is Shared with Model Vendor</span>
+                        <td class="c6" colspan="1" rowspan="1"><p class="c10"><span class="c13">Customer Data Shared with Model Vendor</span>
                             <span class="c0 nf-right-align">Yes</span> </p>
                         </td>
                     </tr>
@@ -142,4 +142,4 @@
                     </tr>
              </table>
         </html>
-        
+

src/_includes/content/trait-types.md

@@ -5,10 +5,10 @@ View the table below to better understand how Segment collects custom, computed,
 You can use the Profile explorer (**Unify > Profile explorer**) to view traits attached to a profile.
 
 | **Trait type**     |  **Description**          |
-|---------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | [Custom traits](/docs/unify/traits/custom-traits/)       | Traits created from source events you pass into Segment. From your sources, send custom traits as pieces of information that you know about a user in an Identify call. |
 | [Computed traits](/docs/unify/traits/computed-traits/)     | Traits collected from computations off of event and event property data from your sources. Create user or account-level calculations like `most_viewed_page` or `total_num_orders` for a customer. Learn more by viewing [types of computed traits](/docs/unify/traits/computed-traits/#types-of-computed-traits).    |
 | [SQL traits](/docs/unify/traits/sql-traits/)          | Traits created by running SQL queries on data in your warehouse. SQL traits are a type of computed trait. SQL traits help you import traits from your data warehouse back into Segment to build audiences or enhance data that you send to other destinations. |
 
 <!--
-| [Predictive traits](/docs/unify/traits/predictions/using-predictions/)  |  Segment creates Predictions as Computed Traits, with scores saved to user profiles as a percentage cohort. | -->
+| [Predictive traits](/docs/unify/traits/predictions/using-predictions/)  |  Segment creates Predictions as Computed Traits, with scores saved to user profiles as a percentage cohort. | -->

src/connections/sources/catalog/libraries/server/http-api/index.md

@@ -395,12 +395,12 @@ POST https://api.segment.io/v1/batch
 ```
 
 <table>
-<tr>
-  <th>Field</th>
-  <th></th>
-  <th>Type</th>
-  <th>Description</th>
-</tr>
+  <tr>
+    <th>Field</th>
+    <th></th>
+    <th>Type</th>
+    <th>Description</th>
+  </tr>
   <tr>
     <td>`batch` _Array_</td>
     <td>An array of Identify, Group, Track, Page and Screen method calls. Each call **must** have an `type` property with a valid method name.</td>
@@ -488,4 +488,4 @@ Segment welcomes feedback on API responses and error messages. [Reach out to sup
 
 ### Experiencing `5xx` errors
 
-If you're experiencing `5xx` errors, refresh the IP address you use to invoke Segment's HTTP API. 
+If you're experiencing `5xx` errors, refresh the IP address you use to invoke Segment's HTTP API. 

src/segment-app/iam/sso.md

@@ -161,7 +161,8 @@ You've now completed setup. For SP-initiated SSO, follow these steps:
 
 {% faq %}
 {% faqitem Do you support automatic user provisioning? %}
-Segment supports "just in time" user permissioning; new users who authenticate using your IdP are automatically created in Segment as minimal-access (read-only) members. If the user already exists in Segment then Segment associates the IdP-identity with the existing Segment user account. Segment also supports user provisioning and role mapping [using SCIM](/docs/segment-app/iam/scim/).{% endfaqitem %}
+Segment supports "just in time" user permissioning; new users who authenticate using your IdP are automatically created in Segment as minimal-access (read-only) members. If the user already exists in Segment then Segment associates the IdP-identity with the existing Segment user account. Segment also supports user provisioning and role mapping [using SCIM](/docs/segment-app/iam/scim/).
+{% endfaqitem %}
 
 {% faqitem Do you support automatic user de-provisioning? %}
 Yes, users can be automatically de-provisioned [if you use SCIM](/docs/segment-app/iam/scim/).