Bad documentation for virtualized events

I am looking at the documentation for the vclick event handler and I am confused.

• It says it simulates the "onclick" handler for mobile devices. Should it say "click" instead of "onclick"? In any case, why would I want to do that? I am using click handlers and they seem to work fine on the devices I tested them on.
• It mentions something about "missing mouse event triggers". What does that mean? Are there devices that don't trigger mouse events for taps?
• The source for the example binds an event to "vclick" that shows a message saying "vmouseup fired.", although when I try the example, it says "vclick fired.". That may simply be a typo.
• The "vclick fired." text comes up twice every time I click. At least that is what happened when I tried it in Chrome and Firefox for OS X.

I think it is unclear as to what advantages "vclick" may have over "click" or "onclick".

Start with the vclick event handler documentation and its linked example. Check the onclick versus click wording, the explanation of missing mouse event triggers, the vmouseup example text, and the duplicate firing report; done means the page accurately explains vclick's purpose and corrects confirmed errors.