Until we have a native way of handling localised documents, I think prepending the title with flags is the most practical way to do it, and a reasonable exception to this guideline.
I think this kind of thing has different opinions and preferences either way, but for this style guide we’re going with accepted industry norms. Once again, the Google and Microsoft guidelines both agree that common contractions are better to use.
That being said, I have read some posts suggest that using negative contractions (like “can’t”) might make understanding more difficult for non-English speakers. We’ll dig into this some more and, if necessary, update the style guide accordingly.
I’ve removed that example!
Yes - that’s very common (not just on Discourse), but I agree that it isn’t quite correct. Using quotation marks would be better, so I think I’ll make that explicit in the style guide.
That’s a great point - I’ll add that in to the style guide!

As much as I appreciate no longer having a ton of doc topics ascribed to me, using Discourse as the author of all the team’s doc topics feels a little cold.
Thanks for this feedback! @maiki made some good points above, and I agree with what he says there. To add on to that, I will say that one of the reasons we have switched official docs to have @Discourse as the author is to give them a greater sense of authority for readers, especially people coming to the docs for the first time. This is also the impetus behind the whole style guide in the first place.
Anyone writing documentation can definitely still inject their personality into their writing, and the discussion on individual documentation topics isn’t going anywhere, so that’s always a good place to make things more personal too.
All of this feedback is greatly appreciated