Bug 1050277 - fixin' up 'postrophes, boss

Rationale for using `&#8217;` instead of UTF-8, from http://www.dwheeler.com/essays/quotes-in-html.html
>  Don’t embed the UTF-8 (or UTF-16) characters directly into the text and depend on setting the UTF-8 charset for now. For example, for right single quotation mark (including English possessives and contractions), use &#8217; and do do not use the UTF-8 encoding 11100010 10000000 10011001 (binary) aka e2 80 99 (hexadecimal) aka 342 200 231 (octal) aka 226 128 153 (decimal). UTF-8 is fantastic, but it not yet universal, and the problem is that other charsets are still in use. The UTF-8 encoding won’t work on some text browsers (e.g., lynx, and thus many blind readers that depend on text rendering). It’s possible in XML and HTML to specify that characters should be interpreted according to a particular character set (charset), but requiring a particular charset has many drawbacks. Setting the charset to utf-8 does work in many places, but only if you explicitly set the charset; failing to set the charset will cause this to fail on many systems. Fundamentally, this makes combining your material with other sources harder, because they’re likely to use other charsets. For example, Microsoft’s non-standard character sets (discussed next) interfere with it, so using the UTF-8 encoding can cause trouble when trying to combine with data from some Microsoft and MacOS tools in some circumstances. In the longer term, hopefuly everyone will switch to UTF-8 and UTF-16, and then this would a reasonable alternative. For now, don’t do it.