Agreed – “Automatic Type-Dependent Closure Construction” jumped right out at me as sounding unnecessarily intimidating. The community pretty consistently calls that “By-Name Parameters”; I’d recommend that the tour do so as well.
I’d also recommend retitling “Sequence Comprehensions” to “For Comprehensions” – I don’t think I’ve ever heard anyone call them “sequence comprehensions”, and the current title really isn’t correct, since
for comprehensions cover a lot more than just sequences. (In particular, doing a
for comprehension over
Option is one of the first things I usually teach, and I probably use it for
Future more than anything else.)
XML processing is the only section I’d drop outright, but I agree with @martijnhoekstra that organizing the tour into tracks might make it a bit more digestible.
Finally, a bug report while I notice it (if it’s in scope for this project): on my laptop, the current Tour’s index pane runs past the bottom of my screen – and I can’t scroll it! The result is that I can’t even see the sections at the bottom.