use straight textual mentions of the referenced RFCs in the abstract to satisfy idnits

draft-dkg-dprive-demux-dns-http.md

@@ -66,11 +66,11 @@ port can be useful for obscuring the presence of DNS queries from a
 network observer, which makes it relevant for DNS privacy. 
 
 Widespread adoption of the described approach could constrain
-evolution of the stream-based variants of both DNS ({{RFC1035}}) and
-HTTP/1.x ({{RFC7230}}) by ossifying existing distinguishing bit
-patterns in early octets sent by the client.  However, this draft
-explicitly rules out multiplexing in this form with HTTP/2, so it
-should place no constraints on it or any higher version of HTTP.
+evolution of the stream-based variants of both DNS (RFC1035) and
+HTTP/1.x (RFC7230) by ossifying existing distinct bit patterns found
+in early octets sent by the client.  However, this draft explicitly
+rules out multiplexing in this form with HTTP/2, so it should place no
+constraints on the evolution of HTTP/2 or any higher version of HTTP.
 
 --- middle