Currently there is a bent towards joinedupwords, but garbage_collector, c-api, and gh-(faq|labels) are exceptions. I'd suggest preferring some form of spacing character for filenames of more than two words, and potentially for filenames of two words.

Let's use a hyphen, because you can use alt+arrow key (on Mac, ctrl+arrow on Windows?) to jump between words. Underscore is treated as a letter.

Implemented all your other changes (I went with a slightly different title for a few files).

Thanks so much, much appreciated! 🎉

What filenames would you suggest?

This is what I would suggest, following the discussion above (you could add ref aliases for the new names, but leave the existing ones obv). The main intent is to more helpfully describe the document's contents, clearly disambiguate it from others and ensure it is a good match for the document title, to aid navigating to/linking the correct one in the source.

Currently there is a bent towards joinedupwords, but garbage_collector, c-api, and gh-(faq|labels) are exceptions. I'd suggest preferring some form of spacing character for filenames of more than two words, and potentially for filenames of two words.

Definitely agreed (was going to go with -), that's a significant part of what I was thinking as it greatly improves readability.

Let's use a hyphen, because you can use alt+arrow key (on Mac, ctrl+arrow on Windows?) to jump between words. Underscore is treated as a letter.

My plans as well 👍

Clearly I messed something up when pushing after doing the filter-repo steps, I thought I'd rebased on upstream properly to retain the history. GitHub won't let me re-open the PR, so opening a new one.

A