Incorporate feedback from @tulshi

Author: FragLegs

openid-sharedsignals-framework-1_0.html

@@ -2771,7 +2771,7 @@ <h5 id="name-updating-a-streams-configur">
 <p id="section-7.1.1.3-3">Transmitter-Supplied properties beside the stream_id MAY be present,
 but they MUST match the expected value. Missing Transmitter-Supplied
 properties will be ignored by the Transmitter. The <code>events_delivered</code> property,
-if present, MUST match the Transmitter's expected value <em>before</em> any updates are applied.<a href="#section-7.1.1.3-3" class="pilcrow">¶</a></p>
+if present, MUST match the Transmitter's expected value before any updates are applied.<a href="#section-7.1.1.3-3" class="pilcrow">¶</a></p>
 <p id="section-7.1.1.3-4">The following is a non-normative example request to replace an Event Stream's
 configuration:<a href="#section-7.1.1.3-4" class="pilcrow">¶</a></p>
 <span id="name-example-update-stream-confi"></span><div id="figupdateconfigreq">
@@ -3438,9 +3438,9 @@ <h4 id="name-subjects">
 <p id="section-7.1.3-1">An Event Receiver can indicate to an Event Transmitter whether or not the
 receiver wants to receive events about a particular subject by "adding" or
 "removing" that subject to the Event Stream, respectively.<a href="#section-7.1.3-1" class="pilcrow">¶</a></p>
-<p id="section-7.1.3-2">If a Receiver has added a subject to a stream, the Transmitter SHOULD send any events that
-match the subject to the Reciever, as long as the Receiver has also subscribed to that
-event type, and both the stream and subject are enabled. In the case of Simple Subjects,
+<p id="section-7.1.3-2">If a Receiver adds a subject to a stream, the Transmitter SHOULD send any events
+relating to the subject, which have event_types that the Receiver has subscribed to,
+and both the stream and the subject are enabled. In the case of Simple Subjects,
 two subjects match if they are exactly identical. For Complex Subjects, two subjects
 match if, for all fields in the Complex Subject (i.e. <code>user</code>, <code>group</code>, <code>device</code>, etc.),
 at least one of the following statements is true:<a href="#section-7.1.3-2" class="pilcrow">¶</a></p>

openid-sharedsignals-framework-1_0.md

@@ -1135,7 +1135,7 @@ request MUST NOT be changed by the Transmitter.
 Transmitter-Supplied properties beside the stream_id MAY be present,
 but they MUST match the expected value. Missing Transmitter-Supplied
 properties will be ignored by the Transmitter. The `events_delivered` property,
-if present, MUST match the Transmitter's expected value _before_ any updates are applied.
+if present, MUST match the Transmitter's expected value before any updates are applied.
 
 The following is a non-normative example request to replace an Event Stream’s
 configuration:
@@ -1575,9 +1575,9 @@ An Event Receiver can indicate to an Event Transmitter whether or not the
 receiver wants to receive events about a particular subject by “adding” or
 “removing” that subject to the Event Stream, respectively.
 
-If a Receiver has added a subject to a stream, the Transmitter SHOULD send any events that
-match the subject to the Reciever, as long as the Receiver has also subscribed to that
-event type, and both the stream and subject are enabled. In the case of Simple Subjects,
+If a Receiver adds a subject to a stream, the Transmitter SHOULD send any events
+relating to the subject, which have event_types that the Receiver has subscribed to,
+and both the stream and the subject are enabled. In the case of Simple Subjects,
 two subjects match if they are exactly identical. For Complex Subjects, two subjects
 match if, for all fields in the Complex Subject (i.e. `user`, `group`, `device`, etc.),
 at least one of the following statements is true:

openid-sharedsignals-framework-1_0.txt

@@ -1350,7 +1350,7 @@ Tulshibagwale, et al.        Standards Track                   [Page 24]
    but they MUST match the expected value.  Missing Transmitter-Supplied
    properties will be ignored by the Transmitter.  The events_delivered
    property, if present, MUST match the Transmitter's expected value
-   _before_ any updates are applied.
+   before any updates are applied.
 
    The following is a non-normative example request to replace an Event
    Stream's configuration:
@@ -2054,21 +2054,21 @@ Tulshibagwale, et al.        Standards Track                   [Page 36]
    "adding" or "removing" that subject to the Event Stream,
    respectively.
 
-   If a Receiver has added a subject to a stream, the Transmitter SHOULD
-   send any events that match the subject to the Reciever, as long as
-   the Receiver has also subscribed to that event type, and both the
-   stream and subject are enabled.  In the case of Simple Subjects, two
-   subjects match if they are exactly identical.  For Complex Subjects,
-   two subjects match if, for all fields in the Complex Subject (i.e.
-   user, group, device, etc.), at least one of the following statements
-   is true:
+   If a Receiver adds a subject to a stream, the Transmitter SHOULD send
+   any events relating to the subject, which have event_types that the
+   Receiver has subscribed to, and both the stream and the subject are
+   enabled.  In the case of Simple Subjects, two subjects match if they
+   are exactly identical.  For Complex Subjects, two subjects match if,
+   for all fields in the Complex Subject (i.e. user, group, device,
+   etc.), at least one of the following statements is true:
 
    1.  Subject 1's field is not defined
 
    2.  Subject 2's field is not defined
 
 
 
+
 Tulshibagwale, et al.        Standards Track                   [Page 37]
 
                               SharedSignals                    June 2023