Update the contributing guide
This updates the build instructions and the Slack channel.
@@ -25,7 +25,7 @@ To contribute to Submariner:
1. Fork this repository
2. Make your changes in the fork
-3. Test your changes by running `make ci e2e` which deploys [Submariner in a Kind 3 cluster setup](https://github.com/submariner-io/submariner/blob/master/scripts/kind-e2e/README.md) and runs E2E tests
+3. Test your changes by running `make e2e` which deploys [Submariner in a Kind 3 cluster setup](https://github.com/submariner-io/submariner/blob/master/scripts/kind-e2e/README.md) and runs E2E tests
4. Submit a pull request (PR) to Submariner master branch
5. (Optionally) Run `make cleanup` to tear down the test clusters once you're finished.
@@ -34,13 +34,13 @@ Refer to [this link](https://help.github.com/en/articles/creating-a-pull-request
A good PR commit message clearly explains the purpose of a PR and the logic implemented.
## Reaching out
-You can reach out to Submariner folks on slack and Google Group.
+You can reach out to Submariner folks on Slack and Google Groups.
-### slack
-Join #submariner slack channel at [Rancher-users workspace](https://rancher-users.slack.com/).
+### Slack
+Join the #submariner Slack channel on [the Kubernetes workspace](https://kubernetes.slack.com/).
### Google group
-Join [Submariner's google group](https://groups.google.com/forum/#!forum/submariner-dev).
+Join [Submariner's Google group](https://groups.google.com/forum/#!forum/submariner-dev).
### Weekly Meeting
Join [Submariner's weekly meeting](https://bluejeans.com/3472508766) from 11:00-11:30AM ET ([agendas and notes](https://docs.google.com/document/d/1qnZ2LpF_rXGfnYYPNTldQ4WbeEUxwnuQD-xTC6GbZdg)).
