Throughout the FHIRcast spec, we use markdown to denote specific terms that exist within the exchanged messages. For example: "hub.channel.type" is a specific json element and specific formatting is applied to this term.  This specific term is used in the plural, here:  https://fhircast.hl7.org/specification/Feb2020Ballot/#subscription-confirmation To clearly indicate the the json element does not include a trailing 's', the formatting is awkward.  Clearly communicating the correct json element name is more important than nice formatting. A middle ground of rewording the sentence to avoid the awkward formatting, while also continuing to clearly communication the appropriate json element name is to update the language from: >For  hub.channel.type}}s of both {{webhook  and  websocket , this subscription confirmation step informs the subscriber of the details of Hub's recently created subscription. to: >For ` hub.channel.type`   values  of `webhook` and `websocket`, this subscription confirmation step informs the subscriber of the details of Hub's recently created subscription. Will update the spec as described, above.