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: When to use the word "button" -- ? From:Gene Kim-Eng <techwr -at- genek -dot- com> To:Craig Cardimon <craig -dot- cardimon -at- gmail -dot- com> Date:Wed, 24 Oct 2012 08:27:46 -0700
I haven't used "button" for a long time. I've seen focus groups where test
subjects confronted with "button" in the instructions for a HW-SW system
tended to looked first for a physical button on the HW.
I do still see "button" used in API docs. In fact, just recently I saw an
API doc that referred to "radio buttons," which is a reference I had not
seen for years.
Gene Kim-Eng
On Wed, Oct 24, 2012 at 8:13 AM, Craig Cardimon <craig -dot- cardimon -at- gmail -dot- com>wrote:
> I am staring at Apply, Continue, Cancel, and Save buttons, wondering if I
> should say:
>
> "Click the Continue button to proceed."
>
> Or just:
>
> "Click Continue to proceed."
>
> Opinions?
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Writer Tip: You have more time to author content with Doc-To-Help, because your project can be up and running in 3 steps.
See the “Getting Started with Doc-To-Help” blog post. http://bit.ly/doc-to-help-3-steps
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
