Editorial changes (#646)

More stuff from #643. This is purely editorial IMO.

Author: ianswett

draft-ietf-moq-transport.md

@@ -842,16 +842,14 @@ to the old relay can be stopped with an UNSUBSCRIBE.
 
 Publishing through the relay starts with publisher sending ANNOUNCE
 control message with a `Track Namespace` ({{model-track}}).
-The announce enables the relay to know which publisher to forward a
-SUBSCRIBE to.
+The ANNOUNCE enables the relay to know which publisher to forward a
+SUBSCRIBE to if the track belongs to the namespace in the ANNOUNCE.
 
-Relays MUST ensure that publishers are authorized by:
-
-- Verifying that the publisher is authorized to publish the content
-  associated with the set of tracks whose Track Namespace matches the
-  announced namespace. Where the authorization and identification of
-  the publisher occurs depends on the way the relay is managed and
-  is application specific.
+Relays MUST verify that publishers are authorized to publish
+the content associated with the set of
+tracks whose Track Namespace matches the announced namespace. Where the
+authorization and identification of the publisher occurs depends on the way the
+relay is managed and is application specific.
 
 Relays respond with an ANNOUNCE_OK or ANNOUNCE_ERROR control message
 providing the result of announcement. The entity receiving the
@@ -861,7 +859,7 @@ either ANNOUNCE_OK or ANNOUNCE_ERROR.
 A Relay can receive announcements from multiple publishers for the same
 Track Namespace and it SHOULD respond with the same response to each of the
 publishers, as though it was responding to an ANNOUNCE
-from a single publisher for a given tracknamespace.
+from a single publisher for a given track namespace.
 
 When a publisher wants to stop
 new subscriptions for an announced namespace it sends an UNANNOUNCE.
@@ -881,7 +879,7 @@ publisher that has announced the subscription's namespace, unless it
 already has an active subscription for the Objects requested by the
 incoming SUBSCRIBE request from all available publishers.
 
-When a relay receives an incoming ANNOUCE for a given namespace, for
+When a relay receives an incoming ANNOUNCE for a given namespace, for
 each active upstream subscription that matches that namespace, it SHOULD send a
 SUBSCRIBE to the publisher that sent the ANNOUNCE.