In the vast majority of cases, your target documentation page will be the documentation for a class. I have frequently spoken already of the importance of class documentation pages. A common move on your part will be to search on a class name in the documentation window. If you search on, say, NSString, the search result whose title is NSString Class Reference is the class documentation for NSString.
Let’s pause to notice the key features of a class documentation page. I’ll use UIButton as an example (Figure 8-1):
Figure 8-1. The start of a typical class documentation page
addTarget:action:forControlEvents:from the UIButton class page; that information is in the UIControl class page. You won’t find out that a UIButton has a
frameproperty from the UIButton class page; that information is in the UIView class page.