Perhaps helping users get set-up should be the first thing you address.
Also, you start off by saying the examples should work well in ghci but then show examples that are not run in ghci.
I fear your experience is blinding you to the numerous little things that trip up newcomers.
You might also state upfront what you assume the reader already knows. Such as the existence, and use, of ghci.
If you are mentioning ghci at the start then maybe show the examples as run in ghci. Or, if you prefer files, then explain how to run a file from the command line.
Yeah, the statement at the top that "you can run most of these examples in ghci" really tripped me up. On one hand, it gave me the clue that the haskell REPL is called "ghci", so I just went to my ubuntu box and typed "ghci" and got told I needed to install "ghc", which I did and was on my way. On the other hand, the examples weren't actually able to be run in ghci. :/
1. paste all (well most, I haven't verified it to say all) of the functions in "anyfile.hs"
2. cd to the same directory as anyfile.hs in terminal
3. open ghci
4. :load anyfile.hs
5. Play with the functions!
Also you should make sure that those who hit the cpp problem don't get overwhelmed. I've actually spent some time this week working out a patch that will make the cpp problem tst hit OS X IMPOSSIBLE to have in the future. Did require learning some autoconf thogh :-)
