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.
Subject:Re: appears vs is displayed From:"Robin M. Allen" <robin -dot- m -dot- allen -at- WORLDNET -dot- ATT -dot- NET> Date:Wed, 26 Mar 1997 09:45:48 -0600
Brad Barnes wrote:
> Consider a minimalist approach:
> 1. Click Add.
> 2. From the Add Patient window, choose blobbity-blah-blah.
> By simple inference, the reader knows that there must be an Add Patient
> window on the screen after they have clicked Add. Furthermore, the above
> approach helps *orient* the reader without being overly wordy or redundant.
> Brad Barnes
> Technical Writer
> Resumix Inc
> kiwi -at- best -dot- com
> brad -at- resumix -dot- com
> At 08:26 AM 3/25/97 -0600, you wrote:
> >Hi ya'll:
> >I'm in the middle of a raging debate among several tech writers about
> >the use of "appears" vs "is displayed," e.g.:
> >"Click Add and the Add Patient window is displayed."
> >"Click Add and the Add Patient window appears."
> >Even though it uses the passive voice, I personally prefer "is
> >displayed." To me, "appears" sounds like it happens through magic. Any
> TECHWR-L (Technical Communication) List Information: To send a message
> to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
> to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
> Search the archives at http://www.documentation.com/ or search and
> browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
I often use this approach, but on occassion, it doesn't work. For
example, if it's important to describe a part of the screen when it is
displayed, it's easier and cleaner to give the feedback on the line
after the action. Rather than before the next command.
robin -dot- m -dot- allen -at- worldnet -dot- att -dot- net