From 0645c8682e46291a41d822a5dae5b72ee98801f7 Mon Sep 17 00:00:00 2001 From: ezio Date: Tue, 21 Jan 2025 12:38:41 +0000 Subject: [PATCH] easier to understand tailworker doc --- src/content/docs/workers/observability/logs/tail-workers.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/workers/observability/logs/tail-workers.mdx b/src/content/docs/workers/observability/logs/tail-workers.mdx index 4bc84300502b70e..bbd694235f8bc57 100644 --- a/src/content/docs/workers/observability/logs/tail-workers.mdx +++ b/src/content/docs/workers/observability/logs/tail-workers.mdx @@ -24,7 +24,7 @@ A Tail Worker is automatically invoked after the invocation of a producer Worker To configure a Tail Worker: 1. [Create a Worker](/workers/get-started/guide) to serve as the Tail Worker. -2. Add a [`tail()`](/workers/runtime-apis/handlers/tail/) handler to your Worker. The `tail()` handler is invoked every time the producer Worker a Tail Worker is connected to is invoked. The following Worker code is a Tail Worker that sends its data to an HTTP endpoint: +2. Add a [`tail()`](/workers/runtime-apis/handlers/tail/) handler to your Worker. The `tail()` handler is invoked every time the producer Worker to which a Tail Worker is connected is invoked. The following Worker code is a Tail Worker that sends its data to an HTTP endpoint: ```js export default {