Merge pull request #39 from PatrickMcDonald/patch-1

Update link in gitready.com/advanced/2009/01/17/restoring-lost-commits.html

Author: ngulden

_posts/2009-01-17-restoring-lost-commits.textile

@@ -6,7 +6,7 @@ category: advanced
 
 So, you just did a @git reset --hard HEAD^@ and threw out your last commit. Well, it turns out you really did need those changes. You'll never be able to implement that algorithm that perfectly twice, so you need it back. Don't fear, git should still have your commit. When you do a reset, the commit you threw out goes to a "dangling" state. It's still in git's datastore, waiting for the next garbage collection to clean it up. So unless you've ran a @git gc@ since you tossed it, you should be in the clear to restore it.
 
-For these examples, I'm working with the "code for this blog":http://github.com/qrush/gitready. From the top, we just ran:
+For these examples, I'm working with the "code for this blog":http://github.com/gitready/gitready. From the top, we just ran:
 
 <pre>
 $ git show-ref -h HEAD