fixed typo eent->event

Author: tulshi

openid-sharedsignals-framework-1_0.html

@@ -1595,7 +1595,7 @@ <h3 id="name-subject-members">
           <h4 id="name-existing-caep-and-risc-even">
 <a href="#section-3.1.1" class="section-number selfRef">3.1.1. </a><a href="#name-existing-caep-and-risc-even" class="section-name selfRef">Existing CAEP and RISC Events</a>
           </h4>
-<p id="section-3.1.1-1">Event types already defiend in the CAEP (<span>[<a href="#CAEP" class="cite xref">CAEP</a>]</span>) and RISC (<span>[<a href="#RISC" class="cite xref">RISC</a>]</span>) drafts MAY use a <code>subject</code> field within the <code>events</code> claim of the SSF eent to describe the primary Subject Principal of the event. SSF Transmitters SHOULD include the top-level <code>sub_id</code> claim even for these existing event types.<a href="#section-3.1.1-1" class="pilcrow">¶</a></p>
+<p id="section-3.1.1-1">Event types already defiend in the CAEP (<span>[<a href="#CAEP" class="cite xref">CAEP</a>]</span>) and RISC (<span>[<a href="#RISC" class="cite xref">RISC</a>]</span>) drafts MAY use a <code>subject</code> field within the <code>events</code> claim of the SSF event to describe the primary Subject Principal of the event. SSF Transmitters SHOULD include the top-level <code>sub_id</code> claim even for these existing event types.<a href="#section-3.1.1-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="new-event-types">

openid-sharedsignals-framework-1_0.md

@@ -270,7 +270,7 @@ Subject Principals are identified by Subject Members defined below.
 A Subject Member of a SSF event describes a subject of the event. A top-level claim named `sub_id` SHOULD be used to describe the primary Subject Principal of the event.
 
 ### Existing CAEP and RISC Events
-Event types already defiend in the CAEP ({{CAEP}}) and RISC ({{RISC}}) drafts MAY use a `subject` field within the `events` claim of the SSF eent to describe the primary Subject Principal of the event. SSF Transmitters SHOULD include the top-level `sub_id` claim even for these existing event types.
+Event types already defiend in the CAEP ({{CAEP}}) and RISC ({{RISC}}) drafts MAY use a `subject` field within the `events` claim of the SSF event to describe the primary Subject Principal of the event. SSF Transmitters SHOULD include the top-level `sub_id` claim even for these existing event types.
 
 ### New Event Types
 New event types MUST use the top-level `sub_id` claim and MUST NOT use the `subject` field in the `events` claim to describe the primary Subject Principal.

openid-sharedsignals-framework-1_0.txt

@@ -182,7 +182,7 @@ Tulshibagwale, et al.        Standards Track                    [Page 3]
 
    Event types already defiend in the CAEP ([CAEP]) and RISC ([RISC])
    drafts MAY use a subject field within the events claim of the SSF
-   eent to describe the primary Subject Principal of the event.  SSF
+   event to describe the primary Subject Principal of the event.  SSF
    Transmitters SHOULD include the top-level sub_id claim even for these
    existing event types.