Link to Event History Limits page

Author: drewhoskins-temporal

docs/develop/python/continue-as-new.mdx

@@ -80,12 +80,9 @@ See how with [`all_handlers_finished`](message-passing#wait-for-message-handlers
 
 ## When is it right to Continue-as-New using the Python SDK? {#when}
 
-Use Continue-as-New when your Workflow might hit scaling limits:
+Use Continue-as-New when your Workflow might hit [Event History Limits](/encyclopedia/workflow/workflow-execution/event#event-history-limits).
 
-- When the Event History grows too large
-- When the Workflow might get too many Updates or Signals
-
-Temporal tracks when you should Continue-as-New.
+Temporal tracks you Workflow's progress against these limits to let you know when you should Continue-as-New.
 Call `workflow.info().is_continue_as_new_suggested()` to check if it's time.
 
 ## How to test Continue-as-New using the Python SDK {#how-to-test}

docs/encyclopedia/workflow/workflow-execution/event.mdx

@@ -65,12 +65,17 @@ An append-only log of [Events](#event) for your application.
 - Event History is durably persisted by the Temporal service, enabling seamless recovery of your application state from crashes or failures.
 - It also serves as an audit log for debugging.
 
-**Event History limits**
+### Event History limits {#event-history-limits}
 
 The Temporal Service stores the complete Event History for the entire lifecycle of a Workflow Execution.
 
-The Temporal Service logs a [warning after 10Ki (10,240) Events](/workflow-execution/limits) and periodically logs additional warnings as new Events are added.
-If the Event History exceeds 50Ki (51,200) Events, the Workflow Execution is terminated.
+The Temporal Service logs a [warning after 10,240 Events](/workflow-execution/limits) and periodically logs additional warnings as new Events are added.
+
+The Workflow Execution is terminated when the Event History:
+
+- exceeds 51,200 Events.
+- contains more than 2000 Updates.
+- contains more than 10000 Signals.
 
 ### Event loop {#event-loop}