don't see a problem with that. That is what it is there for -- reference
also feel free to provide any ideas on what you would like to see. Current things I am toying with as far as the documentation is as follows:
* obviously the name and description of a given function or whatever
* possibly a link that opens in code view the location of that function in the source file
* example output and/or usage
some of what I mentioned above may not make it into the first release, as it would take some coding to accomplish, but I am sure I can do it...