Script updating gh-pages from aee6892. [ci skip]

sframe-wg · Jun 25, 2024 · 8cf736a · 8cf736a
1 parent c7d0f41
commit 8cf736a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/auth48/draft-ietf-sframe-enc.html b/auth48/draft-ietf-sframe-enc.html
@@ -2418,7 +2418,7 @@ <h2 id="name-key-management">
         <h3 id="name-sender-keys">
 <a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-sender-keys" class="section-name selfRef">Sender Keys</a>
         </h3>
-<p id="section-5.1-1">If the participants in a call have a pre-existing E2E-secure channel, they can
+<p id="section-5.1-1">If the participants in a call have a preexisting E2E-secure channel, they can
 use it to distribute SFrame keys.  Each client participating in a call generates
 a fresh <code>base_key</code> value that it will use to encrypt media. The client then uses
 the E2E-secure channel to send their encryption key to the other participants.<a href="#section-5.1-1" class="pilcrow">¶</a></p>

diff --git a/auth48/draft-ietf-sframe-enc.txt b/auth48/draft-ietf-sframe-enc.txt
@@ -771,7 +771,7 @@ Figure 1: Two Options for Integrating SFrame in a Typical Media Stack
 
 5.1.  Sender Keys
 
-   If the participants in a call have a pre-existing E2E-secure channel,
+   If the participants in a call have a preexisting E2E-secure channel,
    they can use it to distribute SFrame keys.  Each client participating
    in a call generates a fresh base_key value that it will use to
    encrypt media.  The client then uses the E2E-secure channel to send