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: Clarity or Talking Down? From:"Parks, Beverly" <ParksB -at- EMH1 -dot- HQISEC -dot- ARMY -dot- MIL> Date:Wed, 28 May 1997 09:06:47 -0700
I think that you are correct and justified in using the word "type" to
indicate when a command is supposed to be typed.
Here's an idea that may help your position. Browse through some of the
manufacturer's user guides for the programming applications that the
programmers use. I bet that you will find those manuals--written
specifically for programmers--also use "type" as you describe.
In a quick search around my office, I found that usage in the user
guides for Borland Delphi, MS Visual Basic, and MS SQL Server.