Stop claiming support for 2.6

I don't even have a Python 2.6 interpreter.
fix a doctest for Python 2

For some reason, raw strings on Python 2 don't prevent \u escapes from
being interpreted in some cases. This may be an unfortunate interaction
between the r'' syntax and "from __future__ import unicode_literals".

This makes things awkward when you're trying to give an example *about*
\u escapes.
fix some trailing spaces, update changelog
Write an example differently because of Read The Docs

Yuck. Read The Docs runs on Python 2, and it interacts badly with
docstrings when "from __future__ import unicode_literals" is on.

It was already hard to document things *about* Unicode without using
Python 3 syntax. But when I use the Python 3 syntax, RTD makes it say
the wrong thing.

I'm working around this for now, but I really hope that Read The Docs
offers a Python 3 option sometime.
unindent docstrings outside of doctests
Oh cool. readthedocs *does* support Python 3.
start updating the README
Update the README to match other docs
fix thing that looked like an HTML tag
try renaming CHANGELOG.txt to CHANGELOG.md
okay, markdown, this is supposed to be a literal
dropped support for 2.6
fix &amp; example to make sense when rendered as markdown

Before it looked like `"&amp;" will become "&", for example, not "&"` which doesn't make sense
Merge pull request #25 from jaredly/patch-1

fix &amp; example to make sense when rendered as markdown