Ideally, the person designing the API would write the API specification in skeleton source files, with only declarations and doc comments, filling in the implementation only to satisfy the written API contract. The purpose of an API writer is to relieve the designer from some of this work. In this case, the API designer would write the initial doc comments using sparse language, and then the writer would review the comments, refine the content, and add tags.
For example, under pre-CSS HTML, a heading element defined with red text would be written as:
Please set a username for yourself.
People will see it as Author Name with your public word lists.
However, we would like to give a visual indication that a QLineEdit is read-only by making it appear gray:
Terms of Service ● © 2016 Modern Language Association of America