add clarification on three-year limit [netlify-build]

Author: pwseg

Diff for: src/engage/product-limits.md

@@ -30,7 +30,7 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
 | Batch Compute Concurrency Limit               | 10 (default) per space                        | The number of batch computations that can run concurrently per space. When this limit is reached, Segment delays subsequent computations until current computations finish.                                                                                                                                                                                                                                                                                                                                                        |
 | Compute Throughput                            | 10000 computations per second                 | Computations include any Track or Identify call that triggers an audience or computed trait re-computation. Once the limit is reached, Segment may slow audience processing.                                                                                                                                                                                                                                                                                                                                                       |
 | Real-time to batch destination sync frequency | 12-15 hours                                   | The frequency with which Segment syncs real-time audiences to batch destinations.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| Event History                                 | `1970-01-01`                                  | Segment may not ingest events with a timestamp earlier than `1970-01-01`, which can impact audience backfills for older events. Segment stores data indefinitely, but ingestion depends on event timestamps.                                                                                                                                                                                                                                                                                                                       |
+| Event History                                 | `1970-01-01`                                  | Segment may not ingest events with a timestamp earlier than `1970-01-01`, which can impact audience backfills for older events. Segment stores data indefinitely, but ingestion depends on event timestamps. <br><br>  While Segment stores all events, event conditions typically evaluate data from the past three years by default. Your plan or configuration may allow a longer time window.                                                                                                                                  |
 | Engage Data Ingest                            | 1x the data ingested into Connections         | The amount of data transferred into the Compute Engine.                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | Audience Frequency Update                     | 1 per 8 hours                                 | Audiences that require time windows (batch audiences), [funnels](/docs/engage/audiences/#funnel-audiences), [dynamic properties](/docs/engage/audiences/#dynamic-property-references), or [account-level membership](/docs/engage/audiences/#account-level-audiences) are processed on chronological schedules. The default schedule is once every eight hours; however, this can be delayed if the "Batch Compute Concurrency Limit" is reached. Unless otherwise agreed upon, the audiences will compute at the limit set forth. |
 | Event Properties (Computed Traits)            | 10,000                                        | For Computed Traits that exceed this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values.                                                                                                                                                                                                                                                                                                                                                                               |

Diff for: src/unify/product-limits.md

@@ -46,7 +46,7 @@ Visit Segment's [pricing page](https://segment.com/pricing/){:target="_blank"} t
 | Batch Compute Concurrency Limit               | 10 (default) per space                        | The number of batch computations that can run concurrently per space. When this limit is reached, Segment delays subsequent computations until current computations finish.                                                                                                                                                                                                                                                                                                                                                        |
 | Compute Throughput                            | 10000 computations per second                 | Computations include any Track or Identify call that triggers an audience or computed trait re-computation. Once the limit is reached, Segment may slow audience processing.                                                                                                                                                                                                                                                                                                                                                       |
 | Real-time to batch destination sync frequency | 2-3 hours                                     | The frequency with which Segment syncs real-time audiences to batch destinations.                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| Event History                                 | `1970-01-01`                                  | Segment may not ingest events with a timestamp earlier than `1970-01-01`, which can impact audience backfills for older events. Segment stores data indefinitely, but ingestion depends on event timestamps.                                                                                                                                                                                                                                                                                                                       |
+| Event History                                 | `1970-01-01`                                  | Segment may not ingest events with a timestamp earlier than `1970-01-01`, which can impact audience backfills for older events. Segment stores data indefinitely, but ingestion depends on event timestamps. <br><br>  While Segment stores all events, event conditions typically evaluate data from the past three years by default. Your plan or configuration may allow a longer time window.                                                                                                                                  |
 | Engage Data Ingest                            | 1x the data ingested into Connections         | The amount of data transferred into the Compute Engine.                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | Audience Frequency Update                     | 1 per 8 hours                                 | Audiences that require time windows (batch audiences), [funnels](/docs/engage/audiences/#funnel-audiences), [dynamic properties](/docs/engage/audiences/#dynamic-property-references), or [account-level membership](/docs/engage/audiences/#account-level-audiences) are processed on chronological schedules. The default schedule is once every eight hours; however, this can be delayed if the "Batch Compute Concurrency Limit" is reached. Unless otherwise agreed upon, the audiences will compute at the limit set forth. |
 | Event Properties (Computed Traits)            | 10,000                                        | For Computed Traits that exceed this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values.                                                                                                                                                                                                                                                                                                                                                                               |