Re: [PATCH v5 2/4] docs: improve formatting in git-send-email documentation

>>> -When `--compose` is used, git send-email will use the From, To, Cc, Bcc,
>>> -Subject, Reply-To, and In-Reply-To headers specified in the message. If
>>> -the body of the message (what you type after the headers and a blank
>>> -line) only contains blank (or Git: prefixed) lines, the summary won't be
>>> +When `--compose` is used, `git send-email` will use the 'From', 'To', 'Cc',
>>> +'Bcc', 'Subject', 'Reply-To', and 'In-Reply-To' headers specified in the
>>> +message. If the body of the message (what you type after the headers and a
>>> +blank line) only contains blank (or Git: prefixed) lines, the summary won't be
>> 
>> Shouldn't 'Git:' in "or Git: prefixed" be marked-up somehow as well?
>> 
>> As these mail header names are all literal parts, shouldn't ehy be
>> marked up like `To`, `Cc`, etc.?
>
> I think its ok to let these remain in '', and deviate from the rules a bit.
> If backticks are used, it will be a mess when rendered on the website.

>>> -    by 'c_rehash', or a single file containing one or more PEM format
>>> -    certificates concatenated together: see verify(1) -CAfile and
>>> -    -CApath for more information on these). Set it to an empty string
>>> +    by `c_rehash`, or a single file containing one or more PEM format
>>> +    certificates concatenated together). Set it to an empty string
>> 
>> What is this change about?  grammatical errors?  non existent links?
>> cpan links?  It does not look any of these.
>
> Non existing links. Checkout the website.