Solved UTF-8 issues (Cannot make out the difference, but I suspect this was copy pasted from the internets; as I had to type it make the "invalid byte sequence in US-ASCII" error go away)
Fixed:

1. Yet another UTF-8 issue
2. Minor edits to the schedule announcement blog posts