Update signal detection duration in documentation

Author: maxmilhan

src/connections/auto-instrumentation/event-builder.md

@@ -47,7 +47,7 @@ Segment collects and displays activity as signals. These signals are grouped int
 
 Segment separates signal collection from event creation. Signals represent raw user interactions, like a button click or screen view. Events, on the other hand, are analytics calls you define based on those signals. This two-step process lets you observe user behavior first, and then decide how and when to turn that behavior into structured analytics events, without needing to modify your code.
 
-Signal detection is active for 24 hours after you generate activity. Detected signals are available in the Event Builder for 72 hours.
+Signal detection is active for 24 hours after you load the app or website in debug mode. Detected signals are available in the Event Builder for 7 days.
 
 ## Create an event
 
@@ -86,4 +86,4 @@ For example, to track a login flow, you might define an Identify event that maps
 Segment uses the event name and any mapped properties to format each event according to the Segment Spec. Events you create in the Event Builder behave the same way as events sent through Segment SDKs or APIs.
 
 > info "Event type behavior in destinations"
-> While Segment handles these event types consistently, downstream tools may treat them differently. For example, Identify events often update user profiles, while Page or Screen events may be handled as pageviews instead of custom events.
+> While Segment handles these event types consistently, downstream tools may treat them differently. For example, Identify events often update user profiles, while Page or Screen events may be handled as pageviews instead of custom events.