Follow standard style in readme

[LinusU]

See expressjs/expressjs.com#719

[LinusU]

@crandmck Should I merge these or should someone else look at them? :)

[crandmck]

Changes LGTM, so you can merge as far as I'm concerned. :-)

[LinusU]

Great :)

[LinusU]

Hmm, actually I don't seem to have write permissions on this repository... I do t know I'm supposed to though :)

Could you merge it for me?

[crandmck]

Lol, I don't have rights either... @dougwilson shouldn't TC members be able to merge PRs?

[dougwilson]

So this is a module from @troygoode who moved it into the expressjs organization some time ago. We have never really sat down to decide what it means to move an external project into the expressjs organization before, and of course, how any new rules would apply retroactively. I would probably not want to do anything immediately right now, at least without even hearing from @troygoode on the subject :)

@troygoode what do you think about this all? So far this module has been autonomous within the expressjs organization. We're probably going to have a discussion on this in the coming weeks and would love it if you could participate :) The best date / time would just be the next TC meeting, which is Jan 11 at 23:30 UTC.

[crandmck]

Yes, discussing in the TC makes sense. Thanks for clarification @dougwilson.

BTW, since a lot of folks are out due to the holidays (and based on your comment above), I'm assuming that there won't be a TC meeting today (which there normally would be on the biweekly schedule). I'll add a short note in the discussions repo just to be explicit.

[troygoode]

Hi @dougwilson I'm happy to participate in the upcoming TC and more than willing to make adjustments that bring cors further into the expressjs standard. Looking at this PR now.

[troygoode]

@LinusU @dougwilson I've merged this one and also updated the repo's settings to give the express-tc team Admin access (patterned after the settings in expressjs/express)

[LinusU]

Thank you ❤