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:"Kulis, Carene" <Carene -dot- Kulis -at- USA -dot- XEROX -dot- COM> Date:Thu, 4 Jun 1998 07:15:20 PDT
From the Microsoft Manual of Styles for Technical Publications (2nd Edition)
Crash
Do not use in end-user documentation; use fail for disks or stop responding
for programs. In programmer documentation it may be the best word in certain
circumstances, but it is computer jargon.
Carene Kulis
<mailto:Carene -dot- kulis -at- mc -dot- usa -dot- xerox -dot- com> Carene -dot- kulis -at- mc -dot- usa -dot- xerox -dot- com
(716)-423-4973
-----Original Message-----
From: Lizak Kristin [mailto:LizakKristin -at- JDCORP -dot- DEERE -dot- COM]
Sent: Thursday, June 04, 1998 9:49 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.
