diff --git a/draft-ietf-sidrops-rov-no-rr.xml b/draft-ietf-sidrops-rov-no-rr.xml
index cb6520b..0a7bb31 100644
--- a/draft-ietf-sidrops-rov-no-rr.xml
+++ b/draft-ietf-sidrops-rov-no-rr.xml
@@ -121,7 +121,7 @@ q      Refresh to its neighbors because it has received new RPKI data.
       might be covered by these new RPKI data.  This will be perceived
       as rude by those neighbors as it passes a serious resource burden
       on to them.  This document recommends implementations keep and
-      mark paths affected by RPKI-based policy so Route Refresh is no
+      mark paths affected by RPKI-based policy, so Route Refresh is no
       longer needed.
     </t>
 
@@ -149,7 +149,7 @@ q      Refresh to its neighbors because it has received new RPKI data.
       BGP speaker 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
-      BGP peers so that it can reevaluate the received paths aginst the
+      BGP peers so that it can reevaluate the received paths against the
       new data.
     </t>
 
@@ -193,7 +193,7 @@ q      Refresh to its neighbors because it has received new RPKI data.
     <t>
       If new RPKI data arrive which invalidate the best route, and the
       BGP speaker did not keep all alternatives, then it MUST issue a
-      route refresh so those alternatives may be evaluated for best
+      route refresh, so those alternatives may be evaluated for best
       route.
     </t>