fix lint nits

Author: englishm

draft-ietf-moq-transport.md

@@ -1417,8 +1417,8 @@ There are two types of Fetch messages:
 Standalone Fetch (0x1) : A Fetch of Objects performed independently of any Subscribe.
 
 Joining Fetch (0x2) : A Fetch joined together with a Subscribe. A Joining Fetch
-shares the same Subscribe ID as an already-sent Subscribe. A publisher receiving a Joining 
-Fetch should use properties of the associated Subscribe to determine the Track Namespace, 
+shares the same Subscribe ID as an already-sent Subscribe. A publisher receiving a Joining
+Fetch should use properties of the associated Subscribe to determine the Track Namespace,
 Track, StartGroup, StartObject, EndGroup, and EndObject for the Joining Fetch such that it is
 contiguous with the associated Subscribe and begins Previous Group Count prior.
 
@@ -1466,8 +1466,8 @@ Fields common to all Fetch Types:
 is a variable length integer that MUST be unique and monotonically increasing
 within  a session. For a Standalone Fetch a new Subscribe ID MUST be used. For
 a Joining Fetch, the Subscribe ID MUST correspond to a Subscribe which has already
-been sent. If a publisher receives a Joining Fetch with a Subscribe ID that does 
-not correspond to an existing Subscribe, it MUST close the session with an 
+been sent. If a publisher receives a Joining Fetch with a Subscribe ID that does
+not correspond to an existing Subscribe, it MUST close the session with an
 Invalid Subscribe ID error.
 
 * Subscriber Priority: Specifies the priority of a fetch request relative to