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: Use of the word "doubt" From:Dave C <davec2468 -at- yahoo -dot- com> To:Tech Writing <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 4 Aug 2014 09:24:45 -0700
Maybe:
“Run the NIBP accuracy test once a year or whenever you have reason to suspect the measured value may not be valid.”
If you are leaving it up to the operator to decide when to run the test other than annually, I don’t think you can make the instruction any more specific than to leave it up to their experience of measured values.
If that’s what the customer wants, that is what I would say.
Cheers,
Dave
-=-=-=-
On 4 Aug 2014, at 8:40 AM, M -dot- Vina-Baltsas -at- mindray -dot- com wrote:
> Any suggestions on how to reword this sentence? I'm not comfortable with
> the use of "doubt" but am not coming up with anything that seems much
> better. I 'd also like to eliminate the use of "you" as it's not used in
> the manual.
>
> "The NIBP accuracy test is required at least once a year or when you doubt
> the measured NIBP."
>
>
> The NIBP accuracy test is required at least once a year or whenever the
> NIBP measurement is in question.
>
> or
>
> ...whenever the NIBP measurement seems out of range or inaccurate.
>
> Thanks,
>
>
> ________________________________________________________________
>
> Michelle Viña-Baltsas
>
>
> STRICTLY PRIVATE & CONFIDENTIAL.This email may contain confidential and
> proprietary material for the sole use of the intended recipient. Any
> review or distribution by others is strictly prohibited. If you are not
> the intended recipient please contact the sender and delete all copies.
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as davec2468 -at- yahoo -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
>
> Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
