minor edits from AD review

Author: mcr

draft-ietf-opsawg-pcaplinktype.md

@@ -2,7 +2,7 @@
 stand_alone: true
 ipr: trust200902
 docname: draft-ietf-opsawg-pcaplinktype-latest
-cat: info
+cat: std
 stream: IETF
 pi:
   symrefs: 'yes'
@@ -664,8 +664,9 @@ informative:
 
 --- abstract
 
-This document describes a set of PCAP-related LinkType values and
+This document describes a set of Packet CAPture (PCAP)-related LinkType values and
 creates an IANA registry for those values.
+These values are used by the PCAP and PCAP-Now-Generic specifications.
 
 --- middle
 
@@ -716,7 +717,7 @@ The policy allocation for the LinkType values is as follows:
 * Values from 0 to 65000 are allocated following a First-Come
   First-Served policy (Section 4.4 of [RFC8126]). Values in the ranges
   0-10, 50-51, and 98-301 are already assigned; values in the ranges
-  11-49 and 52-97 MUST NOT be assigned.
+  11-49 and 52-97 are reserved and must not be assigned.
 
 * Values from 65001 to 65535 are reserved for Experimental Use ({{Section 4.2 of !RFC8126}}).
 
@@ -727,7 +728,7 @@ case here, the reference should be set to
 The initial contents of the table are based upon the link-layer header
 type list maintained by libpcap, and published on {{TCPDUMP}}.
 
-Note that historically, values were assigned incrementally following First Come First Served (FCFS) policy.
+Note that historically, values were assigned incrementally following First Come First Served (FCFS) policy with Expert Review.
 A preference was made to have a public specification, but with no mandate to enforce this.
 Some historical values may have less specification than desired.
 
@@ -754,7 +755,7 @@ This is the initial table for the registry:
 When processing a request for an allocation, the Designated Experts will encourage the requester to provide a specification at a stable URL.
 There is no requirement for a specification, but often review of the specification allows the Designated Expert to determine if the allocation actually is a duplicate of another specification.
 
-When the contents of the link type can contain an IPv4 or IPv6 header, then the octets between the beginning of the link type and the IP header needs to be clear.
+When the contents of the link type can contain an IPv4 or IPv6 header, then the octets between the beginning of the link type and the IP header needs to be clearly specified.
 
 Specifications that are not publicly available, but which may be obtained via liaison agreements (such as to ITU-T, 3GPP, IEEE, etc.) are acceptable particularly if the specification document will be public eventually, but are discouraged.
 For other documents, the Designated Expert will need use their judgement, or consult the OPSAWG or an Area Director.