Blankspace taming

[craftninja]

Corrected some markdown table issues and a typo. No data change!

[craftninja]

I'd be glad to add the olde PR links to already merged peeps' data rows if that is helpful, either in this or another (new) PR.

UPDATE: looks like @sagirk is working on that in #342

[Trott]

Not opposed to this, but for the record, blank spaces were added to make the table readable as raw text (at least with wrapping disabled and, of course, with a monospace typeface), although obviously that tends to deteriorate over time. I'd slightly prefer the spaces to be added back in a way that aligns the table again, but this is fine too.

[Trott]

LGTM despite my (mild) preference for the spaces/aligning stuff. Needs merge conflicts resolved, and that's probably going to happen a lot with this one, so I wouldn't mind it if we make a point to land it soon. It's not like spaces aren't easy to add back in if anyone finds them crucial somehow.

[Trott]

(This also points to the probability that a markdown table might not be the best format, but I'm not sure I have a better one to suggest, at least not within the context of our pull request-based workflow.)

[craftninja]

@Trott I was referencing the previous years for guidance, and also mild preference for less blankspace... with the thought that maybe this makes it easier for people to keep columns aligned? I'll keep addressing merge conflicts / column misalignments in the interim ✨

[SofiEstevez]

@mhdawson @Bamieh tagging you to approve and merge this :)

[mhdawson]

I think it needs a rebase after the previous items that have landed

[craftninja]

@mhdawson Updated!