Mention teams not individuals.

Tom Coleman · Tom Coleman · commit 3e51cbea2703 · 2016-03-02T11:34:56.000+11:00
diff --git a/Contributing.md b/Contributing.md
@@ -246,10 +246,11 @@ these guidelines:
 
 Meteor now has groups defined to cover different areas of the codebase. If you need help getting acceptance on certain pull requests with an area of focus listed below, you can address the appropriate people in the pull request:
 
-* Meteor Data Team - This includes DDP, tracker, mongo, accounts, etc. You can mention @stubailo in the PR.
-* Blaze - This includes Spacebars, Blaze, etc. You can mention @urigo or @yyx990803 in the PR.
-* Build tools - This includes modules, build tool changes, etc. You can memtion @avital or @benjamn in the PR.
-* Mobile integration - This includes Cordova, React Native, etc. You can mention @martijnwalraven in the PR.
+* Meteor Data Team - This includes DDP, tracker, mongo, accounts, etc. You can mention @data in the PR.
+* Blaze - This includes Spacebars, Blaze, etc. You can mention @view-layer in the PR.
+* Build tools - This includes modules, build tool changes, etc. You can memtion @platform in the PR.
+* Mobile integration - This includes Cordova, React Native, etc. You can mention @mobile in the PR.
+* Documentation - This includes the Guide, the Docs, and any supporting material. You can mention @guide in the PR.
 
 Including the people above is no guarantee that you will get a response, or ultimately that your pull request will be accepted. This section exists to give some minor guidance on internal Meteor Development Group team structures.
 
