www/falkon: update package description #195
Conversation
It's no longer 'new-ish'. Whilst here, rewrite things slightly.
|
We generally avoid using double spaces after a full stop. The use of a single space is standard in modern writing. "Edition" is a noun. I would replace it with the verb "editing". The word "Manager" in "SSL Manager" should be lowercase since it used generically. Bulleted lists that don't complete the sentence stem should not be punctuated. I would also remove the hyphen before "qtonly" because that is the name of the flavor. |
Partially resolve freebsd#195 (comment)
This comment was marked as resolved.
This comment was marked as resolved.
Agreed, generally; with exceptions in some FreeBSD Project contexts – and the exceptions are not yet suitably documented. My freebsd/freebsd-src@edacf4b (removal of a double space) was treated as an error, and so on. Briefly: can you think of any context where representation of a package description, making direct use of e.g. the |
Yes, it is a generic term. I'd make it singular too. "CA certificate database" sounds better. |
Singular, and lowercase c, for certificate. Resolve freebsd#195 (comment)
Probably any port maintained by danfe@. He's a fellow grammar pedant, which I appreciate, but I disagree about double spaces after full stops. It's not wrong, just a dated writing style. I used to write that way myself, to be honest, but have kicked the habit. |
I don't know why removing a double space from UPDATING would cause an error. There is a great lack of consistency with regards to double space vs. monospace after a full stop in that file, even within some of the individual entries. |
Revert to single spaces after full stops. Resolves the double spacing aspect of freebsd#195 (comment) Noting freebsd/freebsd-doc@6313bc8#r1299188132 and perceptible gaps in documentation such as the (FDP) FreeBSD Documentation Project Primer for New Contributors.
|
Merged, thanks. |
It's no longer 'new-ish'.
Whilst here, rewrite things slightly.