diff --git a/draft-ymbk-sidrops-rov-no-rr.xml b/draft-ymbk-sidrops-rov-no-rr.xml
index ff2c0c5..7b2e4a3 100644
--- a/draft-ymbk-sidrops-rov-no-rr.xml
+++ b/draft-ymbk-sidrops-rov-no-rr.xml
@@ -11,7 +11,7 @@
 <?rfc subcompact="no"?>
 
 <rfc category="std" consensus="true"
-     docName="draft-ymbk-sidrops-rov-no-rr-02"
+     docName="draft-ymbk-sidrops-rov-no-rr-03"
      ipr="trust200902" updates="8481">
 
 <front>
@@ -142,7 +142,7 @@
   <section anchor="experience" title="ROV Experience">
 
     <t>
-      As Route Origin Validation dropping Invalids has depoyed, some
+      As Route Origin Validation dropping Invalids has deployed, some
       router implementations have been found which, when receiving new
       RPKI data (VRPs, see <xref target="I-D.ietf-sidrops-8210bis"/>)
       issue a BGP Route Refresh <xref target="RFC7313"/> to all sending
@@ -182,6 +182,13 @@
       VRPs can reevaluate them against then current policy.
     </t>
 
+    <t>
+      Policy which may drop paths due to RPKI-based checks such as ROV,
+      ASPA, BGPsec, etc. MUST be run, and the dropped paths saved per
+      the above paragraph, before non-RPKI policies are run, as the
+      latter may change path attributes.
+    </t>
+
     <t>
       As storing these paths could cause problems in resource
       constrained devices, there MUST be a knob allowing operator
@@ -256,7 +263,8 @@
   <section anchor="acks" title="Acknowledgements">
       
     <t>
-      The authors wish to thank Ben Maddison and Nick Hilliard.
+      The authors wish to thank Ben Maddison, John Heasley, and Nick
+      Hilliard.
     </t>
     
   </section>