Fixing routes examples and add missing code tags

Hi,

@chrismccord before fixing more things I would like to show you how I think things should be made.

For example:

* Adding links for things like `Dict` to the documentation.
* Tag more things as `code`, like be consistent with tagging functions and module names etc.
* Be consistent with code examples do not drive users crazy ;-)

If I got the ok, I'll will continue with editing.
@tonini This one is tricky. The enclosing scope info is certainly important, but it is not technically the route itself. What I want people to focus on here is just the route, without getting lost in the rest of the stuff. For this, I would say go with the original.