diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index bab8294..f6c2fd4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -4,29 +4,29 @@ One of the easiest ways to contribute is to participate in discussions and discu
 
 
 ## General feedback and discussions?
-Please start a discussion on the [core repo issue tracker](https://github.com/thinktecture/Thinktecture.IdentityServer.v3/issues).
+Please start a discussion on the [core repo issue tracker](https://github.com/IdentityServer/IdentityServer3/issues).
 
 
 ## Bugs and feature requests?
 Please log a new issue in the appropriate GitHub repo:
 
-* [Core](https://github.com/thinktecture/Thinktecture.IdentityServer.v3)
-* [WS-Federation plugin](https://github.com/thinktecture/Thinktecture.IdentityServer.v3.WsFederation)
-* [EntityFramework support](https://github.com/thinktecture/Thinktecture.IdentityServer.v3.EntityFramework)
-* [ASP. NET Identity support](https://github.com/thinktecture/Thinktecture.IdentityServer.v3.AspNetIdentity)
-* [MembershipReboot support](https://github.com/thinktecture/Thinktecture.IdentityServer.v3.MembershipReboot)
-* [AccessToken validation](https://github.com/thinktecture/Thinktecture.IdentityServer.v3.AccessTokenValidation)
-* [Samples](https://github.com/thinktecture/Thinktecture.IdentityServer.v3.Samples)
+* [Core](https://github.com/IdentityServer/IdentityServer3)
+* [WS-Federation plugin](https://github.com/IdentityServer/IdentityServer3.WsFederation)
+* [EntityFramework support](https://github.com/IdentityServer/IdentityServer3.EntityFramework)
+* [ASP. NET Identity support](https://github.com/IdentityServer/IdentityServer3.AspNetIdentity)
+* [MembershipReboot support](https://github.com/IdentityServer/IdentityServer3.MembershipReboot)
+* [AccessToken validation](https://github.com/IdentityServer/IdentityServer3.AccessTokenValidation)
+* [Samples](https://github.com/IdentityServer/IdentityServer3.Samples)
 
 ## Other discussions
-https://gitter.im/thinktecture/Thinktecture.IdentityServer.v3
+https://gitter.im/IdentityServer/IdentityServer3
 
 ## Filing issues
 The best way to get your bug fixed is to be as detailed as you can be about the problem.
 Providing a minimal project with steps to reproduce the problem is ideal.
 Here are questions you can answer before you file a bug to make sure you're not missing any important information.
 
-1. Did you read the [documentation](https://github.com/thinktecture/Thinktecture.IdentityServer.v3/wiki)?
+1. Did you read the [documentation](https://identityserver.github.io/Documentation)?
 2. Did you include the snippet of broken code in the issue?
 3. What are the *EXACT* steps to reproduce this problem?
 
@@ -39,7 +39,12 @@ Make sure you can build the code. Familiarize yourself with the project workflow
 
 We only accept PRs to the dev branch.
 
-Before submitting a feature or substantial code contribution please discuss it with the team and ensure it follows the product roadmap. You might also read these two blogs posts on contributing code: [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza and [Don't "Push" Your Pull Requests](http://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik. Note that only contributions that meet a high bar for both quality and design/roadmap appropriateness will be merged into the source.
+Before submitting a feature or substantial code contribution please discuss it with the team and ensure it follows the product roadmap. Here's a list of blog posts that are worth reading before doing a pull request:
+
+* [Open Source Contribution Etiquette](http://tirania.org/blog/archive/2010/Dec-31.html) by Miguel de Icaza
+* [Don't "Push" Your Pull Requests](http://www.igvita.com/2011/12/19/dont-push-your-pull-requests/) by Ilya Grigorik.
+* [10 tips for better Pull Requests](http://blog.ploeh.dk/2015/01/15/10-tips-for-better-pull-requests/) by Mark Seemann
+* [How to write the perfect pull request](https://github.com/blog/1943-how-to-write-the-perfect-pull-request) by GitHub
 
 Here's a few things you should always do when making changes to the code base: