TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Scott asks:
How far do you go with the idea of keeping to the present tense when
editing somebody
else's documentation.
Well, first I must confess that I'm a real stickler. I figure it's one of
the things that makes me a good editor. That said, though, it *is* a
preference, so I comment on the cover page that it's more readable to use
present tense -- then I make a tense mark nest to any future tense
construction, should the writer want to take my advice. On second review,
unless the author made some of the changes, I ignore future tense
constructions and simply look for consistency.
Any opinions on when it's ok. to use "you" in documentation?
I use it whenever possible because i think, again, that it makes the
document more readable. The reader is usually also the "doer" and it saves
a mental step if the document makes that assumption.