diff --git a/draft-ietf-grow-wkc-behavior.xml b/draft-ietf-grow-wkc-behavior.xml
index c492514..15cad5b 100644
--- a/draft-ietf-grow-wkc-behavior.xml
+++ b/draft-ietf-grow-wkc-behavior.xml
@@ -83,7 +83,7 @@
     community handling across their networks, taking the inconsistent
     behaviors from the various BGP implementations they operate into
     consideration.  This document recommends specific actions to limit
-    future inconsistency, namely BGP implementors should not create
+    future inconsistency, namely BGP implementors must not create
     further inconsistencies from this point forward.</t>
 
   </abstract>
@@ -236,11 +236,9 @@
     
   <section anchor="note" title="Note for Those Writing RFCs for New Community-Like Attributes"> 
 
-    <t>Care should be taken when establishing new <xref
-    target="RFC1997"/>-like attributes (large communities, wide
-    communities, etc.), RFCs MUST make clear how the new community
-    attribute is to to be handled, avoiding repeating
-    inconsistencies.</t>
+    <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>
 
     </section>
 
@@ -271,11 +269,6 @@
     a neighbor ASN, the operator should confirm with that neighbor how
     the community will be treated.</t>
 
-    <t>Network operators are encouraged to limit their use of the "set"
-    directive (within reason), to improve the readability of their
-    configurations and hopefully to achieve behavioral consistency
-    across platforms.</t>
-    
     </section>
 
   <section anchor="security" title="Security Considerations">