Miguel David

57%
Flag icon
The core idea here is that you should break your writing into bite-sized pieces, often called topics, none of which overlap in content. Doing so means that if things change—and things always change—you only have to update the documentation in one place. Many topics are short, whereas others are quite long. What topics should be is relatively complete in their discussion of a particular subject.
Modern Technical Writing: An Introduction to Software Documentation
Rate this book
Clear rating
Open Preview