This adds a line in the do's and don'ts about requesting a CVE.

Damn you, Slack.

Credit to @jmartin-r7 for the verbiage.

Updated vuln disclosure, removed deprecated instructions, added links to more recent examples

Also includes very small changes to improve punctuation consistency
within CONTRIBUTING.md

See #6052.

In the main, though, the edits are good. Just disagree with a couple.

[See #5028]

Grammar and style.

I'm not sure most people would get it.

It's not about getting kicked in the face by Patrick Swayze (RIP).
It's actually about being nice.

https://www.youtube.com/watch?v=l0aPIXy6PHM

* Specifically disclaim scripts
* Prefer end note links
* Pre-fill the issue submission form (check it out:
  http://r-7.co/MSF-BUGSv1 )

Also updated the wiki with an example message to allay any confusion
about avoiding the default merge message.

http://r-7.co/MSF-Landing-PRs

Also fix an italics where it should have been bold.

Fix a sentence.

Redmine is on its way out. See here: 

https://github.com/rapid7/metasploit-framework/wiki/Decommissioning-Redmine

This is a work in progress because the code base is old and the style
varies wildly, however .rubocop.yml can (and should) be tweaked over
time to change standards as we see fit.  As it stands right now there
are few (if any) modules that pass Rubocop.

changed link from https://dev.metasploit.com/documents/api/ to https://dev.metasploit.com/api/

I've seen a couple PRs targeting the wrong branch. Many projects have a
workflow where PRs should hit `develop` or `release` or something, but
Metasploit-Framework wants PRs targeted against `master`.

Also, warn against fixing too much in one PR since those kinds of PRs
are a) harder to validate and b) might be all wrong anyway. We don't
want people committing a bunch of work when the fundamental approach
isn't going to fly.