Logic in the code != documented functionality

Hi,

I thought the name of the project and the brief documentation made the functionality seem pretty straightforward. In reading the code closely, it seems that there are a few features I wouldn't have guessed from the description:

1. If a given role has "view own ____ content", then edit and delete are forcibly denied. However, under all circumstances, edit and delete (understandably) force read as granted.
... Does this mean that if you want someone to be able to read, edit, and delete their own ___ content, you should DISABLE "view own _____", but enable "edit own ____" and "delete own _____"?
2. For a GIVEN ROLE, if "view own ____ content" is enabled, "* any ____ content" is ignored. This means that if you want a given role to be able to edit any content of a given content type, you should DISABLE "view own _____", but ENABLE "view any _____", and "edit any ________".

Are the above assumptions correct? Were those intended? If so, can they be documented better, including what the intended purpose is?

Thanks,
Al