Fix links to git/git

Author: ugultopu

index.html

@@ -90,7 +90,7 @@
 				Apart from lacking the convenience of a web interface, this process also puts considerable demands on the code contributions: the mails are expected to be plain text only (no HTML!), for example, and the diffs embedded in the mails must apply cleanly (no whitespace changes!), among other things.
 			</p><p>
 				A few tutorials out there try to help with this process (e.g. <a href="https://github.com/git-for-windows/git/blob/master/CONTRIBUTING.md">Git for Windows' detailed instructions how to contribute patches to the Git project</a>, or Git's <a href="https://git-scm.com/docs/MyFirstContribution">MyFirstContribution tutorial</a>).
-				GitGitGadget tries a different approach: allow contributing patches to the Git project itself by opening a Pull Request either at <a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a> or directly at <a href="https://github.com/gitgitgadget/git">https://github.com/git/git</a> and let GitGitGadget prepare and send the corresponding mails.
+				GitGitGadget tries a different approach: allow contributing patches to the Git project itself by opening a Pull Request either at <a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a> or directly at <a href="https://github.com/git/git">https://github.com/git/git</a> and let GitGitGadget prepare and send the corresponding mails.
 			</p>
 		</div>
 
@@ -99,7 +99,7 @@ <h2>How can you use GitGitGadget?</h2>
 			<p>
 				So you cloned <a href="https://github.com/git/git">https://github.com/git/git</a> and implemented a bug fix or a new feature?
 				And you already pushed it to your own fork?
-				Good, now is the time to direct your web browser to <a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a> (or to <a href="https://github.com/gitgitgadget/git">https://github.com/git/git</a> ) and to open a Pull Request.
+				Good, now is the time to direct your web browser to <a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a> (or to <a href="https://github.com/git/git">https://github.com/git/git</a> ) and to open a Pull Request.
 				Please make sure to use a descriptive Pull Request title and description; GitGitGadget will use these as the subject and body of the cover letter (check out the <a href="https://git-scm.com/docs/MyFirstContribution">MyFirstContribution</a> tutorial if you are not familiar with this terminology).
 				You can CC potential reviewers by adding a footer to the PR description with the following syntax:
 			</p><p>
@@ -132,7 +132,7 @@ <h2>What happens after GitGitGadget sent the mails?</h2>
 		<h2>Should I use GitGitGadget on GitGitGadget's Git fork or on Git's GitHub mirror?</h2>
 		<div class="block">
 			<p>
-				GitGitGadget works on both GitGitGadget's Git fork (<a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a>) and Git's GitHub mirror (<a href="https://github.com/gitgitgadget/git">https://github.com/git/git</a>).
+				GitGitGadget works on both GitGitGadget's Git fork (<a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a>) and Git's GitHub mirror (<a href="https://github.com/git/git">https://github.com/git/git</a>).
 				However, some functionality is only available when opening a PR on GitGitGadget's Git fork.
 			</p>
 			<div class="tg-wrap"><table class="tg">