avoid peers

1 files changed, 5 insertions, 5 deletions

diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 6a207cb..277113f 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -673,8 +673,8 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
            The field <bcp14>SHOULD</bcp14> be set to EPOCH * 1.1.
            Given an average number of leading zeros D', then the field value
            <bcp14>MAY</bcp14> be increased up to (D'-D) * EPOCH * 1.1.
-           Lower or higher values may result in rejection of the message
-           by other peers.
+           Lower or higher values may result in rejection of the revocation
+           message when broadcast.
            The EPOCH is extended by
            10% in order to deal with unsynchronized clocks.
          </dd>
@@ -790,14 +790,14 @@ zTLD[126..129].zTLD[63..125].zTLD[0..62]
          evict then from the local store at any time.
        </t>
        <t>
-         Implementations <bcp14>MUST</bcp14> forward received revocations to
-         other peers if they are valid and not stale.
+         Implementations <bcp14>MUST</bcp14> broadcast received revocations to
+         if they are valid and not stale.
          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.
          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.
+         revocations but <bcp14>SHOULD NOT</bcp14> broadcast them.
          Forwarded stale revocations may be discarded.
        </t>
        <t>