Probably meaningless nit: On the second page of style(9) it shows the copyright coming first. Sorry I didn't notice on the one that was complained about on the mailing list.

I wonder if we should do something like this to facilitate search accessibility? This does have a regression over the draft in omitting "radio", but I can't think of any ways that aren't clunky.

Would you be willing to use this? Everywhere else in the manual for many generations SYNOPSIS means "list the options, no prose". Currently we have around 200/500 driver manuals written this way, and I gave a talk on trying to consolidate around doing it that way last year at BSDCan, and I also posted uncontested on arch@ in January. I have an open revision to update our style guides to do it this way (D54586), and some parts of the FreeBSD documentation primer suggested to do so since long before I showed up.

We should mention something about how it reports the buttons so readers can know how to use it. In hgame(4) last year I wrote "and presents them to applications over the evdev interface".

This paragraph is usually for CAVEATS.

This section gets pulled verbatim into the hardware compatibility list, I wrote about it a little in style.mdoc(5).

Traditionally no period here, because this is not a sentence.

Traditionally we use no period here, I think the linter will complain also. All the hid drivers appear to also have xrefs back and forth to hidbus(4).

i am really in favour of changing this in style(9). It doesn't make much sense to me to have this wedged inside the copyright header, especially for files with many copyright owners, and the vast majority of our tree and most of open source puts this as the first line.

this will be a more generic "radio" driver in the future, so I don't want to just call it "airplane mode key". I guess "rfkill" would be a better name here, and maybe even hrfkill would be a better name than hradio on second thought.

sure