What version are you running?
2.0.x
This is the master bug for cases where the Markdown escaping is broken.
The intention is for our Markdown escaping to perfectly represent provided text (from pre-2.0 review requests, or from non-Markdown commit messages) without any artifacts (such as stray "\" symbols).
This doesn't always work perfectly due to the manner in which we're escaping. This is because, currently, we need to be compatible with Python Markdown rendering and JavaScript Marked rendering. The plan is to switch exclusively to Python Markdown rendering, which will allow us to better handle intelligent escaping, fixing most problems.
If you have a case where your text is not escaped and rendered properly, please post it here as a comment.