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: p.c. way to say "crashing" From:"Anderson, Ben" <BAnderson -at- GFBANK -dot- COM> Date:Thu, 4 Jun 1998 09:02:20 -0500
How about System Interruption...
>----------
>From: Lizak Kristin[SMTP:LizakKristin -at- JDCORP -dot- DEERE -dot- COM]
>Sent: Thursday, June 04, 1998 8:48 AM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject: p.c. way to say "crashing"
>
>I am looking for ideas. Marketing wants me to rewrite a sentence that refers
>to your software program crashing. Obviously "crashing" is not a good word,
>and they don't like "program quits responding."
>
>This is for an addendum to the Users Guide. A part of the program was fixed,
>and we are looking for a tactful (i.e. "flowery") way to refer to when their
>program fizzles out. Any suggestions would be welcome. THANKS.
>
>
>
>
