Update README.md

README.md

@@ -46,7 +46,7 @@ With node installed you can run the `js` and `css` targets by simply issuing the
 	npm install
 	node node_modules/.bin/grunt js # or css
 
-Note that if you have the appropriate version of [grunt](https://github.com/cowboy/grunt), our build tool, installed globally you can substitute `grunt` wherever you see `node node_modules/.bin/grunt`. For the remainder of the build documentation we will prefer the more concise `grunt`.
+Note that if you have the appropriate version of [grunt](https://github.com/gruntjs/grunt), our build tool, installed globally you can substitute `grunt` wherever you see `node node_modules/.bin/grunt`. For the remainder of the build documentation we will prefer the more concise `grunt`.
 
 If you want to use the `docs` and `zip` targets you will need bash and they can be run with the following
 
@@ -151,4 +151,4 @@ Often times when working on a feature or bug fix branch it's useful to pull in t
 	git rebase upstream/master
 	## ... here you may have to resolve some conflicts ... ##
 
-You can now push to your own fork and submit the pull request. Keep in mind that it's only a good idea to do this if you _haven't_ already submitted a pull request unless you want to create a new one because your origin remote (your fork) will report a discrepancy. Again, please refer to the [chapter](http://git-scm.com/book/ch3-6.html) in Pro Git on rebasing if you're new to it.
+You can now push to your own fork and submit the pull request. Keep in mind that it's only a good idea to do this if you _haven't_ already submitted a pull request unless you want to create a new one because your origin remote (your fork) will report a discrepancy. Again, please refer to the [chapter](http://git-scm.com/book/ch3-6.html) in Pro Git on rebasing if you're new to it.