The nature of the intended audience can change dramatically the vocabulary, coverage, tone, and even the layout of documentation. Considerations include:

Level of audience experience — Documentation must walk a fine line between being easy enough for a complete novice or an irregular user (once or twice a year) to use, while not annoying your every-day-like-clockwork user. The important user categories are divided by amount of documentation use not by the amount of tag set experience or technical expertise of the user:

I do not mean that it is irrelevant what kind of technical experience the users have. XML, tag set, and programming experience will all determine the approach and vocabulary used in the documentation. The documentation users, who are they: