docs: update location of expressjs.com repo

closes #2995
expressjs · May 13, 2016 · 3d56e73 · 3d56e73
1 parent 12bc16e
commit 3d56e73
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/Collaborator-Guide.md b/Collaborator-Guide.md
@@ -1,7 +1,7 @@
 
 ## Website Issues
 
-Issues for the expressjs.com website go here https://github.com/strongloop/expressjs.com
+Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
 
 ## PRs and Code contributions
 
@@ -16,8 +16,8 @@ Issues for the expressjs.com website go here https://github.com/strongloop/expre
 
 ## Steps for contributing
 
-* [Create an issue](https://github.com/strongloop/express/issues/new) for the bug you want to fix or the feature that you want to add.
-* Create your own [fork](https://github.com/strongloop/express) on github, then checkout your fork.
+* [Create an issue](https://github.com/expressjs/express/issues/new) for the bug you want to fix or the feature that you want to add.
+* Create your own [fork](https://github.com/expressjs/express) on github, then checkout your fork.
 * Write your code in your local copy. It's good practice to create a branch for each new issue you work on, although not compulsory.
 * To run the test suite, first install the dependencies by running `npm install`, then run `npm test`.
 * If the tests pass, you can commit your changes to your fork and then create a pull request from there. Make sure to reference your issue from the pull request comments by including the issue number e.g. #123.