Switch up Markdown syntax for headers [ci skip]

README.md

@@ -1,21 +1,16 @@
-Gems
-====
+# Gems
 Ruby wrapper for the RubyGems.org API.
 
-<a name="installation">Installation</a>
-------------
+## <a name="installation">Installation</a>
     gem install gems
 
-<a name="documentation">Documentation</a>
--------------
+## <a name="documentation">Documentation</a>
 [http://rdoc.info/gems/gems](http://rdoc.info/gems/gems)
 
-<a name="ci">Continuous Integration</a>
-----------------------
+## <a name="ci">Continuous Integration</a>
 [![Build Status](https://secure.travis-ci.org/rubygems/gems.png)](http://travis-ci.org/rubygems/gems)
 
-<a name="examples">Usage Examples</a>
---------------
+## <a name="examples">Usage Examples</a>
     require 'rubygems'
     require 'gems'
 
@@ -92,8 +87,7 @@ Ruby wrapper for the RubyGems.org API.
     # Defaults to the latest version if no version is specified.
     Gems.unyank 'bills', '0.0.1'
 
-<a name="contributing">Contributing</a>
-------------
+## <a name="contributing">Contributing</a>
 In the spirit of [free software](http://www.fsf.org/licensing/essays/free-sw.html), **everyone** is encouraged to help improve this project.
 
 Here are some ways *you* can contribute:
@@ -108,17 +102,15 @@ Here are some ways *you* can contribute:
 * by closing [issues](https://github.com/rubygems/gems/issues)
 * by reviewing patches
 
-<a name="issues">Submitting an Issue</a>
--------------------
+## <a name="issues">Submitting an Issue</a>
 We use the [GitHub issue tracker](https://github.com/rubygems/gems/issues) to track bugs and
 features. Before submitting a bug report or feature request, check to make sure it hasn't already
 been submitted. You can indicate support for an existing issuse by voting it up. When submitting a
 bug report, please include a [Gist](https://gist.github.com/) that includes a stack trace and any
 details that may be necessary to reproduce the bug, including your gem version, Ruby version, and
 operating system. Ideally, a bug report should include a pull request with failing specs.
 
-<a name="pulls">Submitting a Pull Request</a>
--------------------------
+## <a name="pulls">Submitting a Pull Request</a>
 1. Fork the project.
 2. Create a topic branch.
 3. Implement your feature or bug fix.
@@ -129,8 +121,7 @@ operating system. Ideally, a bug report should include a pull request with faili
 8. Commit and push your changes.
 9. Submit a pull request. Please do not include changes to the gemspec, version, or history file. (If you want to create your own version for some reason, please do so in a separate commit.)
 
-<a name="rubies">Supported Rubies</a>
-----------------
+## <a name="rubies">Supported Rubies</a>
 This library aims to support and is [tested
 against](http://travis-ci.org/rubygems/gems) the following Ruby
 implementations:
@@ -152,7 +143,6 @@ implementation, you will be personally responsible for providing patches in a
 timely fashion. If critical issues for a particular implementation exist at the
 time of a major release, support for that Ruby version may be dropped.
 
-<a name="copyright">Copyright</a>
----------
+## <a name="copyright">Copyright</a>
 Copyright (c) 2011 Erik Michaels-Ober.
 See [LICENSE](https://github.com/rubygems/gems/blob/master/LICENSE.md) for details.