Thanks, merged! Here's hoping for more significant contributions :-)

I am writing a generator for jQueryUI API Library for Script#. api.jqueryui.com is an excellent source for this automation. That is why I need to fix the typos first to have correct generation :) I might have some suggestions for the xml schema to simplify parsing. For example I noticed that an option has a type as an xml attribute but also can have types specified as xml nodes. What is the difference between those two? Do you have xml schema already defined in separate file?

That's a good point about the type. We've started with the attribute, then added the elements to rely less on multi-attributes like type="jQuery, String", but for single types, having an attribute keeps things a lot simpler. For our XSLT, accepting both is actually fine.

We don't have a XML schema, and I'd rather not bother creating one - maintaining the xml content and xslt is work enough...

For specific issues, feel free to create issues on this repo.