Original text:
Authentication credential: set of information associated with an entity, including that entity's public key and parameters associated with the public key.  Examples of authentication <del> credentials are CBOR Web Tokens (CWTs) and CWT Claims Sets (CCSs) </del>  RFC8392, X.509 certificates RFC7925 and C509 certificates I- D.ietf-cose-cbor-encoded-cert.  Further details about authentication credentials are provided in sec-pub-key-format. "subjectPublicKeyAlgorithm" element, respectively. If authentication credentials are CBOR Web Tokens (CWTs) or CWT <del> Claims Sets (CCSs) RFC8392, the public key algorithm is fully described by a COSE key type and its "kty" and "crv" parameters. </del>  Authentication credentials are used to derive pairwise keys (see key- derivation-pairwise) and are included in the external additional For example, an X.509 certificate is provided as its direct binary serialization.  If C509 certificates or CWTs are used as authentication credentials, each is provided as the binary <del> serialization of a (possibly tagged) CBOR array.  If CCSs are used as authentication credentials, each is provided as the binary serialization of a CBOR map. </del>  If authentication credentials are CWTs, then the untagged CWT associated with an entity is stored in the Security Context and used

Reviewer comments:
So far, it was used 1x in abbreviated form, and 2x as "CWT Claims Sets (CCS)". The abbreviation was problematic the way it was used while being a reference into RFC8392, it was not defined there. I'm not 100% happy with dropping the term "CCS" because it having an abbreviation is a good pointer for users to see that this is an established, good and compact thing to use (right?), but I'd rather spare readers the confusion of clicking through to 8392 and not finding the letters "CCS". I'd be happy with any better handling of the possible confusion, this is just the best I'm coming up with.

Revised text:
Authentication credential: set of information associated with an entity, including that entity's public key and parameters associated with the public key.  Examples of authentication  <ins> credentials are CBOR Web Tokens (CWTs) and CWT Claims Sets </ins> RFC8392, X.509 certificates RFC7925 and C509 certificates I- D.ietf-cose-cbor-encoded-cert.  Further details about authentication credentials are provided in sec-pub-key-format. "subjectPublicKeyAlgorithm" element, respectively. If authentication credentials are CBOR Web Tokens (CWTs) or CWT  <ins> Claims Sets RFC8392, the public key algorithm is fully described by a COSE key type and its "kty" and "crv" parameters. </ins> Authentication credentials are used to derive pairwise keys (see key- derivation-pairwise) and are included in the external additional For example, an X.509 certificate is provided as its direct binary serialization.  If C509 certificates or CWTs are used as authentication credentials, each is provided as the binary  <ins> serialization of a (possibly tagged) CBOR array.  If CWT Claims Sets are used as authentication credentials, each is provided as the binary serialization of a CBOR map. </ins> If authentication credentials are CWTs, then the untagged CWT associated with an entity is stored in the Security Context and used