Behind the many staff-training, user-feedback, and design-review proposals described in "Improving the usability of programming publications" (Bethke, 1981), lies a basic commitment to perceived ease of use. In this commentary I argue that this ease-of-use approach to documentation adequacy is valuable because it is intrinsically more sophisticated than its alternatives.