Remove leading / from route configuration

Let's remove the leading '/' from the custom routes configuration.  This has screwed me up a couple times now.  When I build a resource, I don't use the /, then when I add a custom route I do need it.  So it just feels inconsistent in its current form.  There's no ambiguity - we know that all routes we're defining start at the root (or whatever prefix we're at).
