Merge pull request #323 from ekr/issue298_freshness

Freshness -> keying material. Fixes #298

Author: ekr

draft-ietf-mls-architecture.md

@@ -1492,7 +1492,7 @@ still be holding old keying material and thus be a threat to both FS and PCS if
 it is later compromised.
 
 MLS partially defends against this problem by active members including
-freshness. However, not much can be done on the inactive side especially in the
+new keying material. However, not much can be done on the inactive side especially in the
 case where the client has not processed messages.
 
 > **Recommendation:** Mandate key updates from clients that are not otherwise

rfc9750-draft.xml

@@ -1751,7 +1751,7 @@ replacement of keying material, any client which is persistently offline may
 still be holding old keying material and thus be a threat to both FS and PCS if
 it is later compromised.</t>
           <t>MLS partially defends against this problem by active members including
-freshness. However, not much can be done on the inactive side especially in the
+new keying material. However, not much can be done on the inactive side especially in the
 case where the client has not processed messages.
 
 <!-- [rfced] Section 8.2.2:  We had trouble following this sentence.