Regarding the hate-in with Data::Dumper, of which I've not found issue, my suggestion would be to simply add text as follows (or something to this effect):
If you find the format of Data::Dumper to be too difficult, try installing and using Data::Dump, YAML, JSON, Data::DumpXML, among other possibilities, instead. They all fill the same need, with varying output.
In my mind, it's more important to get them debugging than it is which tool they're using. Offer choices, but get the concepts across. Preferably with something they can start using immediately, and let them advance into other options.
In that way, I'd suggest that you point out when a tool you're suggesting to use may need installation, such as YAPE::Regex::Explain in #8.
Also, for #3, eliminate the word "colon" from the text, merely suggest "delimiters". Then you can give examples, "such as colons." Personally, I prefer square bracket delimiters () - even if there are brackets in the text I'm printing, I usually find that I'm not confused, whereas trying to follow colons can give me eye-strain. Thus, I think that'd make another good example. (Well, I think it makes a better example, but I'm not writing this checklist ;-) )