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.
Re: on "CAN", was Old thread, hopefully new spin on "allow" v. "enable.
Subject:Re: on "CAN", was Old thread, hopefully new spin on "allow" v. "enable. From:iain -at- hairydog -dot- co -dot- uk (Iain Harrison) To:techwr-l -at- lists -dot- raycomm -dot- com Date:Sat, 11 Mar 2000 13:38 +0000 (GMT Standard Time)
> The second set have different meanings to the reading. I'm having
> expressing the difference understandably in written format,
The difference seems simple:
The first set informs you that you are able to perform the tasks.
The second set tells you to perform the tasks.
My re-write of example 1 would be:
"Change the circuit being tested without exiting and reentering
the BlahTest module."
But a better "can-free" alternative would be "You do not have to exit and
reenter the BlahTest mode to change the circuit being tested."
Personally, I don't see what is wrong with "can"
iain -at- hairydog -dot- co -dot- uk
iainh -at- cix -dot- co -dot- uk