Review comments addressed

Review comments addressed

Author: appsdesh

openid-sharedsignals-framework-1_0.md

@@ -552,12 +552,11 @@ TODO: consider adding a IANA Registry for metadata, similar to Section 7.1.1 of
 {{RFC8414}}. This would allow other specs to add to the metadata.
 
 ### Authorization scheme {#authorization-scheme}
-SSF is an HTTP based signals sharing framework. It is agnostic to the authentication and authorization schems used to secure stream configuration APIs. It does not provide any SSF specific authentication and authorization schemes but relies on the cooperating parties mutual security considerations. Authorization scheme section of the metadata, providers disovery informaton related to the transmitter's stream management APIs.
+SSF is an HTTP based signals sharing framework. It is agnostic to the authentication and authorization schemes used to secure stream configuration APIs. It does not provide any SSF specific authentication and authorization schemes but relies on the cooperating parties mutual security considerations. Authorization scheme section of the metadata, providers discovery information related to the transmitter's stream management APIs.
 
 spec_urn  
 
-> A URN for a specification for the protocol being used  REQUIRED.
-
+> REQUIRED. A URN that describes the specification of the protocol being used.
 
 The receiver will call the transmitter APIs by providing appropriate credentials as per the `spec_urn`.
 
@@ -2047,8 +2046,9 @@ The purpose is defense in depth against confusion with other JWTs, as described
 in Sections 4.5 and 4.6 of {{RFC8417}}.
 
 ### The "aud" Claim {#aud-claim}
-The "aud" claim can be a single value or an array. Values that uniquely identifies the Receiver to the
-Transmitter MAY be used, if the two parties have agreement on the format.
+The "aud" claim can be a single value (string) or an array of strings. Values that 
+uniquely identifies the Receiver to the Transmitter MAY be used, if the two parties
+have agreement on the format.
 
 More than one value can be present if the corresponding Receivers are known to
 the Transmitter to be the same entity, for example a web client and a mobile