Fix some broken links

Closes #4 - Remove link for modern day ruby warrior
Closes #7 - Fix dead internal link on security
Closes #9 - Remove modern day ruby warrior from resources
Closes #14 - Fix link to rubygems mirror repo
Closes #5 - Fix broken links from rubyforge on make your own gem page

contributing.md

@@ -305,11 +305,15 @@ A souped-up implementation of search on RubyGems.org, using Solr. Still not
   </a>
 </p>
 
+<<<<<<< HEAD
 <<<<<<< HEAD
 ### [RubyGems Mirror](https://github.com/rubygems/rubygems-mirror/wiki/Mirroring-2.0)
 =======
 <a class="project__name" href="https://github.com/rubygems/rubygems-mirror/wiki/Mirroring-2.0">RubyGems Mirror</a>
 >>>>>>> Add redesign styles for guides
+=======
+<a class="project__name" href="https://github.com/rubygems/rubygems-mirror">RubyGems Mirror</a>
+>>>>>>> Fix some broken links
 
 The current state of mirroring RubyGems is frankly embarrassing. We need
 RubyGems to be highly available all over the world, no more excuses! Discussion

make-your-own-gem.md

@@ -97,7 +97,7 @@ information you see on a gem page
 
 > The description member can be much longer than you see in this example. If it
 > matches `/^== [A-Z]/` then the description will be run through
-> [RDoc's markup formatter](http://rdoc.rubyforge.org/RDoc/Markup.html) for display on
+> [RDoc's markup formatter](https://github.com/rdoc/rdoc) for display on
 > the RubyGems web site. Be aware though that other consumers of the data might not
 > understand this markup.
 
@@ -276,9 +276,10 @@ for gems, explained in [this guide](/patterns).
 
 If you've added more files to your gem, make sure to remember to add them to
 your gemspec's `files` array before publishing a new gem! For this reason (among others),
-many developers automate this with [Hoe](http://seattlerb.rubyforge.org/hoe/),
+many developers automate this with
+[Hoe](https://github.com/seattlerb/hoe),
 [Jeweler](https://github.com/technicalpickles/jeweler),
-[Rake](http://rake.rubyforge.org/classes/Rake/GemPackageTask.html),
+[Rake](https://github.com/jimweirich/rake),
 [Bundler](http://railscasts.com/episodes/245-new-gem-with-bundler), or
 [just a dynamic gemspec
 ](https://github.com/wycats/newgem-template/blob/master/newgem.gemspec).

resources.md

@@ -21,7 +21,6 @@ Tutorials
 ---------
 
 * [Making Ruby Gems](http://timelessrepo.com/making-ruby-gems)
-* [Gem Sawyer, Modern Day Ruby Warrior](http://rubylearning.com/blog/2010/10/06/gem-sawyer-modern-day-ruby-warrior/)
 * [Gemcutter & Jeweler](http://railscasts.com/episodes/183-gemcutter-jeweler)
 * [MicroGems: five minute RubyGems](http://jeffkreeftmeijer.com/2011/microgems-five-minute-rubygems/) - Gems so small that you can store them in a gist.
 * [Let's Write a Gem: Part 1](http://rakeroutes.com/blog/lets-write-a-gem-part-one/) and [Part 2](http://rakeroutes.com/blog/lets-write-a-gem-part-two/)

security.md

@@ -38,7 +38,7 @@ command optionally lets you set a security policy, and you can verify the
 signing key for a gem before you install it.
 
 However, this method of securing gems is not widely used. It requires a number
-of [manual steps on the part of the developer](#building_gems), and there is no
+of [manual steps on the part of the developer](#building-gems), and there is no
 well-established chain of trust for gem signing keys.  Discussion of new
 signing models such as X509 and OpenPGP is going on in the [rubygems-trust
 wiki](https://github.com/rubygems-trust/rubygems.org/wiki/_pages), the

what-is-a-gem.md

@@ -102,5 +102,4 @@ Credits
 
 This guide was adapted from [Gonçalo
 Silva](https://twitter.com/#!/goncalossilva)'s original tutorial on
-docs.rubygems.org and from [Gem Sawyer, Modern Day Ruby
-Warrior](http://rubylearning.com/blog/2010/10/06/gem-sawyer-modern-day-ruby-warrior/).
+docs.rubygems.org and from Gem Sawyer, Modern Day Ruby Warrior.