diff --git a/draft-lenders-core-dnr.md b/draft-lenders-core-dnr.md
index daf3a68..b084674 100644
--- a/draft-lenders-core-dnr.md
+++ b/draft-lenders-core-dnr.md
@@ -63,7 +63,6 @@ informative:
   RFC8323: coap-tcp
   RFC8484: doh
   RFC8613: oscore
-  RFC9176: core-rd
   RFC9250: doq
   RFC9203: ace-oscore
   RFC9528: edhoc
@@ -124,11 +123,10 @@ CoAP offers three security modes:
   addition to transport security.
 
   OSCORE keys have a limited lifetime and need to be set up.
-  Keys can be received from an ACE Authorization Server (AS), as described in the ACE OSCORE profile {{-ace-oscore}}, or, alternatively to support “zero-touch", through an EDHOC key exchange {{-edhoc}}, 
-  as described in the ACE EDHOC profile {{-ace-edhoc}}.
+  Keys can be received from an ACE Authorization Server (AS), as described in the ACE OSCORE profile {{-ace-oscore}}, or, alternatively to support “zero-touch”, through an EDHOC key exchange {{-edhoc}}, as described in the ACE EDHOC profile {{-ace-edhoc}}.
 
-The SVCB-based discovery of a CoAP service in mode “no security" is covered in {{-coap-indication}}, and a CoAP service in the mode “transport security" in {{-coap-dtls-svcb}}.
-The discovery of CoAP services in mode "object security" is not specified.
+The SVCB-based discovery of a CoAP service in mode “no security” is covered in {{-coap-indication}}, and a CoAP service in the mode “transport security” in {{-coap-dtls-svcb}}.
+The discovery of CoAP services in mode “object security” is not specified.
 To guide future specifications, this document clarifies aspects when using SVCB in the context of CoAP and object security.
 
 # Terminology