From 380b5f858346be98db7ad851b63f254b75cc255b Mon Sep 17 00:00:00 2001
From: Randy Bush <randy@psg.com>
Date: Thu, 21 May 2020 14:25:06 -0700
Subject: [PATCH] Geoff edit

---
 draft-ymbk-sidrops-6486bis.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/draft-ymbk-sidrops-6486bis.xml b/draft-ymbk-sidrops-6486bis.xml
index 78b22c0..3a1411c 100644
--- a/draft-ymbk-sidrops-6486bis.xml
+++ b/draft-ymbk-sidrops-6486bis.xml
@@ -574,9 +574,9 @@
   <section title="Relying Party Use of Manifests" anchor="sect-6">
 
     <t>
-      Each RP must determine which signed objects it will use for
+      Each RP MUST determine which signed objects it will use for
       validating assertions about INRs and their use (e.g., which ROAs
-      to use in the construction of route filters). Manifests are
+      to use in the construction of route filters).  Manifests are
       designed to allow an RP to detect manipulation of repository data
       and/or errors by a CA or repository manager. Unless _all_ of the
       files enumerated in a manifest can be obtained by an RP (either