diff --git a/draft-ietf-grow-wkc-behavior.xml b/draft-ietf-grow-wkc-behavior.xml
index 3f35202..19e5b1d 100644
--- a/draft-ietf-grow-wkc-behavior.xml
+++ b/draft-ietf-grow-wkc-behavior.xml
@@ -11,7 +11,7 @@
 <?rfc tocindent="yes"?>
 <?rfc tocompact="yes"?>
 
-<rfc category="std" docName="draft-ietf-grow-wkc-behavior-07" updates="1997" ipr="trust200902">
+<rfc category="std" docName="draft-ietf-grow-wkc-behavior-08" updates="1997" ipr="trust200902">
 
 <front>
 
@@ -239,7 +239,7 @@
 
     <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>
+    explicitly how the new attribute is to be handled.</t>
 
     </section>
 
@@ -252,7 +252,7 @@
     <t>Unfortunately, it would be operationally disruptive for vendors
     to change their current implementations.</t>
 
-    <t>Vendors SHOULD clearly document the behavior of "set" directive
+    <t>Vendors MUST clearly document the behavior of "set" directive
     in their implementations.</t>
 
     <t>Vendors MUST ensure that their implementations' "set" directive