code format fix

src/connections/destinations/actions.md

@@ -339,14 +339,19 @@ Below are two examples demonstrating how to use Liquid templates in Segment mapp
 ##### Example 1: Standardize email addresses
 This example converts an email address to lowercase and removes extra whitespace, ensuring consistency for a destination.
 
-```json
-{% if event.properties.email %}
-  {{ event.properties.email | downcase | strip }}
-{% else %}
-  {{ event.properties.email | default: "[email protected]" }}
-{% endif %}
+
+```
+  {% raw %}
+  {% if event.properties.email %}
+    {{ event.properties.email | downcase | strip }}
+  {% else %}
+    {{ event.properties.email | default: "[email protected]" }}
+  {% endif %}
+  {% endraw %}
 ```
+
 Input: `event.properties.email` = "[email protected]"
+
 Output: [email protected]
 
 Explanation:
@@ -358,18 +363,23 @@ Explanation:
 ##### Example 2: Transform phone number with conditional logic
 This example formats a phone number by removing non-digit characters, adding a country code, and prepending a plus sign.
 
-```json
-{% if event.properties.phone %}
-  {% assign phone = event.properties.phone | strip | remove: "-" | remove: "(" | remove: ")" | remove: " " %}
-  {% if phone | slice: 0, 1 != "1" %}
-    {% assign phone = phone | prepend: "1" %}
+
+```
+  {% raw %}
+  {% if event.properties.phone %}
+    {% assign phone = event.properties.phone | strip | remove: "-" | remove: "(" | remove: ")" | remove: " " %}
+    {% if phone | slice: 0, 1 != "1" %}
+      {% assign phone = phone | prepend: "1" %}
+    {% endif %}
+    {{ phone | prepend: "+" }}
+  {% else %}
+    {{ event.properties.phone | default: "" }}
   {% endif %}
-  {{ phone | prepend: "+" }}
-{% else %}
-  {{ event.properties.phone | default: "" }}
-{% endif %}
+  {% endraw %}
 ```
+
 Input: `event.properties.phone` = "(123) 456-7890"
+
 Output: +11234567890
 
 Explanation:

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

@@ -29,7 +29,7 @@ If you have a non-standard or high volume usage plan, you have unique Linked Aud
 
 Name | Limit | Details 
 ---- | ----- | --------
-RETL row limit | 150 million | The audience compute fails if the total output exceeds the limit. 
+RETL row limit | 150 million | The audience compute fails if the total output exceeds the limit. This limit is the sum of the total linked audience profile membership count and the total number of entity relationships for the profiles in the audience.
 RETL column limit | 500 columns | The audience compute fails if the number of columns exceeds the limit. 
 Global concurrent audience runs | 5 total within any given space | New audience runs are queued once the limit is reached and will start execution once prior audience runs complete. If you need a higher global concurrent audience runs limit, contact [[email protected]](mailto:[email protected]){:target="_blank"}.
 Event Size | 32 KB | Segment doesn’t emit messages for profiles whose total related entities and enrichments exceed the limit.
@@ -56,4 +56,4 @@ To improve performance and manage compute costs, follow these best practices:
 - Run on a dedicated warehouse cluster if you're operating at enterprise scale.
 - Stagger audience sync schedules to reduce concurrency and avoid bottlenecks.
 
-Following this guidance will help you keep audience syncs running efficiently even as your scale grows.
+Following these guidances help you keep audience syncs running efficiently even as your scale grows.