From 7f2fcaa53393f474d6f809ff7ce431cb66f032cb Mon Sep 17 00:00:00 2001 From: Ankur Verma Date: Sat, 27 Dec 2025 19:16:44 -0500 Subject: [PATCH] Docs: Fix typo in development guide Signed-off-by: Ankur Verma --- docs/broker/filtering.md | 6 +++--- docs/decisions/eventing-and-messaging.md | 1 + docs/delivery/README.md | 4 ++-- 3 files changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/broker/filtering.md b/docs/broker/filtering.md index 6972b92335d..395cf00bf46 100644 --- a/docs/broker/filtering.md +++ b/docs/broker/filtering.md @@ -280,7 +280,7 @@ spec: Cannot be specified with the SourceAndType filter. _This example assumes the repository name is available as a CloudEvents -extension `{"repository":proposals"}`._ +extension `{"repository":"proposals"}`._ Specified with the attributes filter: @@ -309,7 +309,7 @@ spec: Cannot be specified with the SourceAndType filter. _This example assumes the repository name is available as a CloudEvents -extension `{"github.repository":proposals"}`._ +extension `{"github.repository":"proposals"}`._ Specified with the attributes filter: @@ -350,7 +350,7 @@ spec: Cannot be specified with the SourceAndType filter or the attributes filter. _This example assumes the event data is the parseable equivalent of -`{"user":{"id":"abc123"}`._ +`{"user":{"id":"abc123"}}`._ ```yaml spec: diff --git a/docs/decisions/eventing-and-messaging.md b/docs/decisions/eventing-and-messaging.md index d7180dca200..189193430e5 100644 --- a/docs/decisions/eventing-and-messaging.md +++ b/docs/decisions/eventing-and-messaging.md @@ -68,4 +68,5 @@ additional repos in the release process. ## Source documents [Proposal by Mark Fisher](https://docs.google.com/document/d/1w5Bd5kEiiMk7i7X0EUdy6PFbWUpwGTwep8I0N52esyM/edit#) + [Decision by eventing approvers](https://docs.google.com/spreadsheets/d/16aOhfRnkaGcQIOR5kiumld-GmrgGBIm9fppvAXx3mgc/edit?) diff --git a/docs/delivery/README.md b/docs/delivery/README.md index 759ee62d354..8026087a156 100644 --- a/docs/delivery/README.md +++ b/docs/delivery/README.md @@ -40,11 +40,11 @@ these situations. ### Dead Letter Sink Channels are responsible for forwarding received events to subscribers. When -they fail to do so, they are responsible for sending the failing events to an +they fail to do so, they are responsible for sending the failing events to a **dead letter sink**, potentially one per subscriber. Similarly Event Sources are responsible for sending events to a sink and when -they fail to do so, they are responsible for sending the failing events to an +they fail to do so, they are responsible for sending the failing events to a **dead letter sink**. The dead letter sink can be a channel but it does not have to.