(Of course, I don't write fancy macros, so I wasn't taking advantage of Racket. For 99% of the macros I write syntax-rules is good enough.)
A few other things I prefer the SRFI way, for example, Racket's comprehensions seem awkward compared to SRFI-42 (in particular Racket decided to call the main comprehension for*/list, leaving prettier and shorter names to less useful variants such as the exotic parallel-by-default for/list, or the execute-for-side-effects and parallel-by-default for); but all in all I agree that Racket is pretty sweet. If ever own a computer with more than 2GB of ram I'll definitely give it another shot.
Having the documentation be parsed by the same infrastructure that understands the programs that you're annotating really goes a long way toward making the documentation cross-referenceable and easy for developers to work with.
I just wish there were an established way of documenting Packages (the PLaneT replacement).
The racket docs (http://docs.racket-lang.org/) have a list of tutorials at the top. There's a visual art/programming tutorial for those new to lisp (http://docs.racket-lang.org/quick/) and a webapp one (http://docs.racket-lang.org/continue/) that demonstrates Racket's built-in web framework.