Hmmm... looks like there may have been a caching problem on our content server. I'll chat with the web folks and see what the deal is. Sorry about that, guys.