>The RELEASE command Help documentation, specifically the Command Reference section, needs significant revision to communicate that a RELEASE command may do nothing without emitting an error condition. That is, the RELEASE command will execute but the subject of the command will NOT be released, nor will that fact be returned so that exception handling could be invoked.
>
>It needs to go into more detail as regards the fact that RELEASEing an OBJECT may NOT do anything if there is a memvar containing an object reference that itself has not been RELEASEd first. It needs to show clear examples of this situation, and how to deal with them. It also needs to introduce and define the term "dangling reference".
>
>Some of this information *is* mentioned in: Programming in Visual FoxPro--->Object Oriented Programming--->Classes in Visual FoxPro--->Writing Class Definitions Programmatically--->Object Reference Creation.
>
>It is fine to leave it there as-is, but more and better information is required where it is most likely to be found and read. The existing mention is buried very deep and in no way highlights the importance of the information it is communicating. It is very easy to overlook the paragraph altogether.

Well, maybe this is for Toledo wish list? I agree that in VFP help (and not only) there are some orphan topics (not included in index and not included in see also links). Also there are many disconnected parts of information that can only be found by searching of specific term. But what about term difference then? For example: according to me (as a foreigner) the term may be "order", but some other guy (or gal) will say it "sequence".
There is lot more to say, but I'll content myself by saying only the above comments.