Update Readme to display well on Github

[rdancer]

Hi, Michel

You said yesterday you would be interested in what was the Markdown code that didn't parse. It is really minor. You can see the example at the top of Readme.md in this commit; if you search for the string "like this", you will see it.

You said that you didn't want to rename the files, so I've reverted that.

Kind regards
Jan

---

When a code span contains backticks, GitHub Flavoured Markdown would not parse it properly unless the surrounding backticks are doubled, or even tripled. Example:

Bad :   (1) ` `a` `     (2) ` ``b'' `
Good:   (1) `` `a` ``   (2) ``` ``b'' '''

[michelf]

This looks like a quirk in their implementation of Markdown. Pretty much all Markdown implementations do the correct thing here: http://johnmacfarlane.net/babelmark2/?normalize=1&text=%60+%60%60foo%60%60+%60

I'll wait to see what happens with the issue I just filled before I decide what to do with this.