From 7f10396159bc75d444927504bf0c20aef70591bb Mon Sep 17 00:00:00 2001 From: Matthias Wessendorf Date: Wed, 26 Jul 2023 14:11:05 +0200 Subject: [PATCH] Update blog/docs/articles/knative-eventing-vision.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Christoph Stäbler --- blog/docs/articles/knative-eventing-vision.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/docs/articles/knative-eventing-vision.md b/blog/docs/articles/knative-eventing-vision.md index faf3b4d706..d1d888aa21 100644 --- a/blog/docs/articles/knative-eventing-vision.md +++ b/blog/docs/articles/knative-eventing-vision.md @@ -75,7 +75,7 @@ The good news is: This breaks the limitation to only use the event type metadata In addition to the above limitation, the fact that for EventType we need established connection between workloads (e.g. PingSource -> Broker) means It is not possible to tell what event type definitions are generally available in Knative Eventing, based on the installed sources/event emitters, independent of running workloads. -To address this problem, Knative Eventing will have a new Event Type Definition metadata CRD that can capture this information independently of running applications. +To address this problem, Knative Eventing will have a new EventTypeDefinition metadata CRD that captures this information independently of running applications. Details can be found in the matching [feature track document]( https://docs.google.com/document/d/1vwEWtAm28g_QY9j0b63h8sRpGhvyB1K5ViNr8X3vIiM/edit).