diff --git a/rfcs/0006-cdevents/README.md b/rfcs/0006-cdevents/README.md
index 35b60ce57e..de4bc43c3b 100644
--- a/rfcs/0006-cdevents/README.md
+++ b/rfcs/0006-cdevents/README.md
@@ -68,7 +68,7 @@ then this section can be replaced with the actual documentation.
 Optional if existing discussions and/or issues are linked in the motivation section.
 -->
 
-Users of multiple different CI/CD tools such as Tekton and Flux could use CDEvents as a potential way to enable interoperability. For example, a user may want a Flux resource to reconcile after Tekton has done something.
+Users of multiple different CI/CD tools such as Tekton and Flux could use CDEvents as a potential way to enable interoperability. For example, a user may want a Flux resource to reconcile as part of a Tekton `pipeline`.
 The Tekton `pipeline` will fire off a CDEvent to the CloudEvents Broker. A subscription that the user will have set up externally, e.g. with the [knative broker](https://knative.dev/docs/eventing/brokers/) will then send a relevant CDEvent to the CDEvent Receiver within Flux. 
 
 ![usecase](cdevents-flux-tekton.png)