That sounds reasonable enough to me. I don't have a strong opinion on these kinds of styling, even though I'd have probably ended up capitalizing them all myself
Well, to be clear; That's how…
I didn't realise the non-British was more prevalent. It indeed makes sense to use the non-British form then. I am opinionated about it, but I'm also just one person, so there's that :p
There's something off about this sentence 🤔. It's similar to the setting above[1], so should probably be more like "list of TLDs (top-level domains) which will be ignored by the metadata parser."
This sentence seems weird too. Maybe "Enable sending emails from your instance." or something?
This is maybe more clear/correct: "Rich media is cached without the TTL, but the rich media may have an image which can expire, like AWS-signed URL."
I see a lot has changed from two indents to one. I have never used *bsd myself. Are we sure that two indents isn't just the typical *bsd way of doing it?
I wonder how much sense it makes to capitalise package names here. Backticks generally mean code. So I think it should either be the package name like how you'd use it in a command (pacman -S postgresql), or not be between backticks. For packages I think it make sense to use backticks and the names like how you'd use in commands.