Where to put the SourceForge library...

The instructions state to...

Place the downloaded directory 'excanvas_r3' inside the 'beautytips/other_libs' directory.

However, the SourceForge download consists only of files found within a ZIP file. Honestly, I think I can manage, but this kind of documentation (which is often found in open-source documentation) is very frustrating and only leads to more complications down the road if someone needs to reach out for technical assistance / insight as it leads ticket submitters to providing false information.

So is there any way this documentation can be refined to be more concise? For example, the instructions assume that a *directory* is downloaded but judging from what I found http://code.google.com/p/explorercanvas/downloads/list, it's actually a single ZIP file containing multiple files AND directories... So should we then assume that ONLY the files within the ZIP's root level be placed inside a directory WE create and named "excanvas_r3" inside the beuatytips/other_libs location or does this actually mean that the SourceForge download no longer has exists? While I understand that download locations change without notice, it might be worth considering using a more automated approach of installing this extra library while providing a static library file along with the beautytips download as fallback. For example, provide a default library file with the beautytips download but code an admin configuration page to allow users to enter in a URL of the excanvas download location whereby the page then (after clicking "Save" or whatever) downloads the library, decompresses it, and stores it in the standard libraries location if and only if it's able to (otherwise, it uses the fallback version)... Doing this would provide a means of acquiring an up-to-date version but also provide a fallback in the event that library file can't be found.

While I'm on it, shouldn't all libraries be in the standard Drupal library location? Maybe this has been fixed in the dev version? If that's the case, then shouldn't this be reflected in the README.txt?

(Not trying to be annoying or disrespectful... Just trying to provide insight into the perspective of someone who hasn't used your module yet.)