[Workers] Clarify scope of tail workers (#18507)

* [Workers] Clarify scope of tail workers

* Update src/content/docs/workers/observability/logs/tail-workers.mdx

---------

Co-authored-by: ToriLindsay <[email protected]>

Author: markdembo

src/content/docs/workers/observability/logs/tail-workers.mdx

@@ -17,7 +17,7 @@ Tail Workers are available to all customers on the Workers Paid and Enterprise t
 
 ![Tail Worker diagram](~/assets/images/workers/platform/tail-workers.png)
 
-A Tail Worker is automatically invoked after the invocation of a producer Worker (the Worker the Tail Worker will track) that contains the application logic. It captures events after the producer has finished executing. You can filter, change the format of the data and send events to any HTTP endpoint. For quick debugging, Tail Workers can be used to send logs to [KV](/kv/api/) or any database.
+A Tail Worker is automatically invoked after the invocation of a producer Worker (the Worker the Tail Worker will track) that contains the application logic. It captures events after the producer has finished executing. Events throughout the request lifecycle, including potential sub-requests via [Service Bindings](/workers/runtime-apis/bindings/service-bindings/) and [Dynamic Dispatch](/cloudflare-for-platforms/workers-for-platforms/get-started/configuration/), will be included. You can filter, change the format of the data, and send events to any HTTP endpoint. For quick debugging, Tail Workers can be used to send logs to [KV](/kv/api/) or any database.
 
 ## Configure Tail Workers