It's WordPress - capital P, dang it.

WordPress, like GitHub, is a camel-cased name that deserves to be
written properly. Props to @jeremyvisser for pointing this out.

Closes #1384

site/docs/migrations.md

@@ -49,10 +49,10 @@ Where IMPORTER is the name of the specific importer.
 
 ## WordPress
 
-### Wordpress export files
+### WordPress export files
 
 If hpricot is not already installed, you will need to run `gem install hpricot`.
-Next, export your blog using the Wordpress export utility. Assuming that the
+Next, export your blog using the WordPress export utility. Assuming that the
 exported file is saved as `wordpress.xml`, here is the command you need to run:
 
 {% highlight bash %}
@@ -61,13 +61,16 @@ $ ruby -rubygems -e 'require "jekyll/jekyll-import/wordpressdotcom";
 {% endhighlight %}
 
 <div class="note">
-  <h5>ProTip™: Wordpress.com Export Tool</h5>
+  <h5>ProTip™: WordPress.com Export Tool</h5>
-  <p markdown="1">If you are migrating from a Wordpress.com account, you can access the export tool at the following URL: `https://YOUR-USER-NAME.wordpress.com/wp-admin/export.php`.</p>
+  <p markdown="1">If you are migrating from a WordPress.com account, you can
+  access the export tool at the following URL:
+  `https://YOUR-USER-NAME.wordpress.com/wp-admin/export.php`.</p>
 </div>
 
-### Using Wordpress MySQL server connection
+### Using WordPress MySQL server connection
 
-If you want to import using a direct connection to the Wordpress MySQL server, here's how:
+If you want to import using a direct connection to the WordPress MySQL server,
+here's how:
 
 {% highlight bash %}
 $ ruby -rubygems -e 'require "jekyll/jekyll-import/wordpress";
@@ -85,23 +88,23 @@ $ ruby -rubygems -e 'require "jekyll/jekyll-import/wordpress";
     JekyllImport::WordPress.process("database", "user", "pass", "127.0.0.1")'
 {% endhighlight %}
 
-### Further Wordpress migration alternatives
+### Further WordPress migration alternatives
 
 While the above methods work, they do not import much of the metadata that is
-usually stored in Wordpress posts and pages. If you need to export things like
+usually stored in WordPress posts and pages. If you need to export things like
 pages, tags, custom fields, image attachments and so on, the following resources
 might be useful to you:
 
 - [Exitwp](https://github.com/thomasf/exitwp) is a configurable tool written in
-  Python for migrating one or more Wordpress blogs into Jekyll (Markdown) format
+  Python for migrating one or more WordPress blogs into Jekyll (Markdown) format
   while keeping as much metadata as possible. Exitwp also downloads attachments
   and pages.
 - [A great
   article](http://vitobotta.com/how-to-migrate-from-wordpress-to-jekyll/) with a
-  step-by-step guide for migrating a Wordpress blog to Jekyll while keeping most
+  step-by-step guide for migrating a WordPress blog to Jekyll while keeping most
   of the structure and metadata.
 - [wpXml2Jekyll](https://github.com/theaob/wpXml2Jekyll) is an executable
-  windows application for creating Markdown posts from your Wordpress XML file.
+  windows application for creating Markdown posts from your WordPress XML file.
 
 ## Drupal
 

site/docs/resources.md

@@ -30,9 +30,9 @@ Jekyll’s growing use is producing a wide variety of tutorials, frameworks, ext
 #### Other hacks
 
 - [Integrating Twitter with Jekyll](http://www.justkez.com/integrating-twitter-with-jekyll/)
-  > “Having migrated Justkez.com to be based on Jekyll, I was pondering how I might include my recent twitterings on the front page of the site. In the Wordpress world, this would have been done via a plugin which may or may not have hung the loading of the page, might have employed caching, but would certainly have had some overheads. … Not in Jekyll.”
+  > “Having migrated Justkez.com to be based on Jekyll, I was pondering how I might include my recent twitterings on the front page of the site. In the WordPress world, this would have been done via a plugin which may or may not have hung the loading of the page, might have employed caching, but would certainly have had some overheads. … Not in Jekyll.”
 - [‘My Jekyll Fork’, by Mike West](http://mikewest.org/2009/11/my-jekyll-fork)
-  > “Jekyll is a well-architected throwback to a time before Wordpress, when men were men, and HTML was static. I like the ideas it espouses, and have made a few improvements to it’s core. Here, I’ll point out some highlights of my fork in the hopes that they see usage beyond this site.”
+  > “Jekyll is a well-architected throwback to a time before WordPress, when men were men, and HTML was static. I like the ideas it espouses, and have made a few improvements to it’s core. Here, I’ll point out some highlights of my fork in the hopes that they see usage beyond this site.”
 - [‘About this Website’, by Carter Allen](http://cartera.me/2010/08/12/about-this-website/)
   > “Jekyll is everything that I ever wanted in a blogging engine. Really. It isn’t perfect, but what’s excellent about it is that if there’s something wrong, I know exactly how it works and how to fix it. It runs on the your machine only, and is essentially an added”build" step between you and the browser. I coded this entire site in TextMate using standard HTML5 and CSS3, and then at the end I added just a few little variables to the markup. Presto-chango, my site is built and I am at peace with the world.”
 - [Generating a Tag Cloud in Jekyll](http://www.justkez.com/generating-a-tag-cloud-in-jekyll/)