diff --git a/draft-dkg-dprive-demux-dns-http.md b/draft-dkg-dprive-demux-dns-http.md
index df95d076b5e4cdc1f5be2e7f62b4b5e21c823366..aea34c6cd1301d0ad4948104cc8f187f552ec255 100644
--- a/draft-dkg-dprive-demux-dns-http.md
+++ b/draft-dkg-dprive-demux-dns-http.md
@@ -395,11 +395,10 @@ In streaming DNS, octets 8 through 11 represent answer counts and
 authority counts in normal DNS queries, or Prerequisite and Update
 counts in DNS UPDATE.  Standard DNS queries will set them both 0.  DNS
 UPDATE queries are likely to include some records in these sections,
-so they won't be all zero, but as long as no more than 255
-Prerequisite records and no more than 255 Update records are sent, at
-least one octet will have value 0 (the high octet of the count of a
-field where there are fewer than 255 records).  But No HTTP client
-sends a zero-valued octet in these positions.
+so they won't be all zero, but as long as no more than 2570
+Prerequisite records and no more than 2570 Update records are sent, at
+least one octet will have value less than 0x0A.  But No HTTP client
+sends an octet less tan 0x0A in these positions.
 
 octets 12 and 13
 ----------------
@@ -409,7 +408,8 @@ RRs.  When a DNS query is sent with EDNS(0), the OPT RR is accounted
 for here.  So this is often either 0x0000 or 0x0001.  In a secure DNS
 UPDATE {{RFC3007}}, the SIG(0) or TSIG record is also found in this
 section, which could increase the values of these octets to 0x0002.
-No HTTP client will send these low values at these positions.
+No HTTP client will send octets with these low values at these
+positions.
 
 Combinations of octets
 ======================