minor fix

1 files changed, 8 insertions, 7 deletions

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index eddb298..7371303 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -755,7 +755,7 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
          <dd>Field as defined in the revocation message above.</dd>
        </dl>
        <t>
-         In order to verify a revocation the following steps <bcp14>MUST</bcp14> be taken:
+         In order to validate a revocation the following steps <bcp14>MUST</bcp14> be taken:
        </t>
        <ol>
          <li>The signature <bcp14>MUST</bcp14> be verified against the zone key.</li>
@@ -765,7 +765,7 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
          <bcp14>MUST NOT</bcp14> use an integer data type to calculate or represent D'.</li>
        </ol>
        <t>
-         The TTL field is informational.
+         The TTL field in the revocation message is informational.
          A revocation <bcp14>MAY</bcp14> be discarded without checking the POW
          values or the signature if the TTL (in combination with TIMESTAMP)
          indicates that the revocation has already expired.
@@ -782,12 +782,11 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
          If the current time is after the expiration date, the
          revocation is considered stale but may still be otherwise
          considered valid.
-         Stale revocations <bcp14>MAY</bcp14> be discarded.
        </t>
        <t>
          Verified revocations <bcp14>MUST</bcp14> be stored locally.
-         The implementation <bcp14>MAY</bcp14> evict stale revocations from the
-         local store at any time.
+         The implementation <bcp14>MAY</bcp14> discard stale revocations and
+         evict then from the local store at any time.
        </t>
        <t>
          Implementations <bcp14>MUST</bcp14> forward received revocations to
@@ -795,13 +794,15 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
          Should the calculated validity period differ from the TTL field value,
          the calculated value <bcp14>MUST</bcp14> be used as TTL field value
          when forwarding the revocation message.
-         Any valid revocation MAY be considered during delegation record
-         processing (<xref target="delegation_processing"/>).
          Systems may disagree on the current time, so implementations
          <bcp14>MAY</bcp14> use stale but otherwise valid
          revocations but <bcp14>SHOULD NOT</bcp14> forward them to other peers.
          Forwarded stale revocations may be discarded.
        </t>
+       <t>
+         Any valid revocation MAY be considered during delegation record
+         processing (<xref target="delegation_processing"/>).
+       </t>
      </section>