From 7f6a19a82474b247e03eeb9cb187609a1d8c242b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dominik=20S=C3=BC=C3=9F?= Date: Fri, 24 Jan 2025 10:53:44 +0100 Subject: [PATCH] Update content/en/blog/2025/observing-lambdas/index.md Co-authored-by: Tiffany Hrabusa <30397949+tiffany76@users.noreply.github.com> --- content/en/blog/2025/observing-lambdas/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/2025/observing-lambdas/index.md b/content/en/blog/2025/observing-lambdas/index.md index 53c16204db78..98153fd4fea8 100644 --- a/content/en/blog/2025/observing-lambdas/index.md +++ b/content/en/blog/2025/observing-lambdas/index.md @@ -47,7 +47,7 @@ logline, or the execution context is about to be shut down. ### This is where the magic happens Up until now, this just seems like extra work for nothing. You'll still have to -wait for the collector to ship the data, right? This is where the special +wait for the Collector to ship the data, right? This is where the special `decouple` processor comes in. It separates the receiving and exporting components while interfacing with the Lambda lifecycle. This allows for the Lambda to return, even if not all data has been sent. At the next invocation (or