active voice instead of passive voice in documentation
status
todo
type
task
description Use the active voice ("Type ... to start Linuxconf") rather than passive ("Linuxconf can be started by typing ...") whenever possible. Active voice makes for more lively, interesting reading. It is more compelling than passive voice and helps to reduce word count.
This does not mean that the passive voice is forbidden. There are situations when using the passive voice is appropriate, such as release notes, technical notes, and similar material. human iduberprojekt-307priority0idb2236f68-38ef-48b7-89ce-762f48d060e9