From 42b45b14132ec941a49a6a0b1c09c25c5f3a5c7f Mon Sep 17 00:00:00 2001
From: adamkenihan <adam.kenihan@est.tech>
Date: Fri, 14 Jun 2024 14:48:40 +0100
Subject: [PATCH] Small changes to non-goals and summary

Signed-off-by: adamkenihan <adam.kenihan@est.tech>
---
 rfcs/NNNN-cdevents-provider/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/rfcs/NNNN-cdevents-provider/README.md b/rfcs/NNNN-cdevents-provider/README.md
index 4f7bb724..28b60920 100644
--- a/rfcs/NNNN-cdevents-provider/README.md
+++ b/rfcs/NNNN-cdevents-provider/README.md
@@ -17,7 +17,7 @@ Must be one of `provisional`, `implementable`, `implemented`, `deferred`, `rejec
 
 ## Summary
 
-This RFC proposes to add a `Provider` type to the Flux notification-controller API for the sending of CDEvents.
+This RFC proposes to add a `Provider` type to the Flux notification-controller API for sending [CDEvents](https://github.com/cdevents).
 
 When `Provider` objects configured to send CDEvents are alerted by a Flux event, they will utilise a user defined mapping of Flux and CDEvents events to send an appropriate CDEvent payload to a defined URL.
 <!--
@@ -43,7 +43,7 @@ know that this has succeeded?
 
 ### Non-Goals
 
-A CDEvent receiver is already implemented into Flux 2.3.0.
+Implementing CDEvents into every Flux controller that is not the notification controller. 
 
 <!--
 What is out of scope for this RFC? Listing non-goals helps to focus discussion