diff --git a/draft-ietf-grow-wkc-behavior.xml b/draft-ietf-grow-wkc-behavior.xml
index 8daff5b..0c439aa 100644
--- a/draft-ietf-grow-wkc-behavior.xml
+++ b/draft-ietf-grow-wkc-behavior.xml
@@ -91,11 +91,11 @@
   <note title="Requirements Language">
 
     <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
-      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
-      are to be interpreted as described in <xref target="RFC2119">RFC
-      2119</xref> only when they appear in all upper case.  They may
-      also appear in lower or mixed case as English words, without
-      normative meaning.</t>
+    NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
+    "MAY", and "OPTIONAL" in this document are to be interpreted as
+    described in BCP 14 <xref target="RFC2119"/> <xref
+    target="RFC8174"/> when, and only when, they appear in all capitals,
+    as shown here.</t>
 
     </note>
 
@@ -223,9 +223,10 @@
       community" will not overwrite diverges from the IANA's list of
       Well-Known communities.  Quite a few Well-Known communities from
       IANA's list do not receive special treatment in Cisco IOS XR, and
-      at least one specific community on Cisco IOS XR's special
-      treatment list (internet == 0:0) is not really on IANA's list --
-      it's taken from the "Reserved" range [0x00000000-0x0000FFFF].</t>
+      at least one community on Cisco IOS XR's special treatment list,
+      internet == 0:0, is not formally a Well-Known Community as it is
+      not in <xref target="IANA-WKC"/>; but taken from the Reserved
+      range [0x00000000-0x0000FFFF].</t>
 
       <t>This merely notes an inconsistency.  It is not a plea to
       'protect' the entire IANA list from "set community."</t>
@@ -236,7 +237,7 @@
     
   <section anchor="note" title="Note for Those Writing RFCs for New Community-Like Attributes"> 
 
-    <t>> When establishing new [RFC1997]-like attributes (large
+    <t>When establishing new [RFC1997]-like attributes (large
     communities, wide communities, etc.), RFC authors should state
     explicitly how the > new attribute is to be handled.</t>
 
@@ -302,8 +303,9 @@
 <back>
 
   <references title="Normative References">
-    <?rfc include="reference.RFC.2119"?>
     <?rfc include="reference.RFC.1997"?>
+    <?rfc include="reference.RFC.2119"?>
+    <?rfc include="reference.RFC.8174"?>
     <reference anchor="IANA-WKC" target="https://www.iana.org/assignments/bgp-well-known-communities">
       <front>
         <title>Border Gateway Protocol (BGP) Well-Known Communities</title>