diff --git a/draft-ietf-sidrops-rov-no-rr.xml b/draft-ietf-sidrops-rov-no-rr.xml
index b8dbc73..f44c6f1 100644
--- a/draft-ietf-sidrops-rov-no-rr.xml
+++ b/draft-ietf-sidrops-rov-no-rr.xml
@@ -10,7 +10,7 @@
 
 <rfc category="std" consensus="true"
      submissionType="IETF" 
-     docName="draft-ietf-sidrops-rov-no-rr-04"
+     docName="draft-ietf-sidrops-rov-no-rr-05"
      ipr="trust200902" updates="8481">
 
 <front>
@@ -185,10 +185,9 @@
     </t>
 
     <t>
-      When RPKI data cause one or more paths to be dropped by operator
-      policy due to ROV, those paths MUST NOT be evaluated for best
-      route, but MUST be saved (either separately or marked) so they may
-      be reevaluated with respect to new RPKI data.
+      A route that is dropped by operator policy due to ROV MUST be
+      considered ineligible and MUST be kept in the Adj-RIB-In for
+      potential future evaluation.
     </t>
 
     <t>
@@ -242,12 +241,12 @@
     </t>
 
     <t>
-      If the BGP speaker has insufficient resources to support either of
-      the two proposed options, it MUST NOT be used for Route Origin
-      Validation.  The equiptment should either be replaced with capable
-      equipement or ROV not used.  I.e. the knob in <xref target="rib"/>
-      should only be used in very well known and controlled
-      circumstances.
+      If the BGP speaker's equipment has insufficient resources to
+      support either of the two proposed options, it MUST NOT be used
+      for Route Origin Validation.  The equiptment should either be
+      replaced with capable equipement or ROV not used.  I.e. the knob
+      in <xref target="rib"/> should only be used in very well known and
+      controlled circumstances.
     </t>
 
     <t>