Hmm.... Are you very good at Linq and XML Schemas? Both help in understanding how this thing works.
The examples didn't seem too terribly steep to me. Here is perhaps a short primer based on my understanding and playing around with it for a bit. Please do not take this as gospel as I just started with this thing as well.
Given an XSD, elements are objects and attributes are propeties. Nested elements are nested objects which I prefer over the way the old XSD command line tool generated objects. I believe this is a closer representation of the actual XML instance
as defined by the XSD. The simplest, e.g. (Leaf Node Elements) are typed according to there XSD type.
That is as simple as I can explain what is going on. Does this hopefully clear things up for you?
PS - I had an older set of code that did use the class generated by the XSD tool and I like this so much that I converted the entire thing to use LinqToXsd instead.