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:Number List with Only One Item? From:"Jason Willebeek-LeMair" <jlemair -at- cisco -dot- com> To:"'Hager, Harry (US - East Brunswick)'" <hhager -at- dc -dot- com>, "'TECHWR-L'" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 15 May 2000 09:48:07 -0500
I would leverage a bit of Monty Python in this case:
1. From the abc menu in the def window, select xyz.
The progam opens the xyz window.
2. THERE IS NO STEP TWO!
(Capitalized on purpose to indicate shouting)
Jason
-----Original Message-----
From: Hager, Harry (US - East Brunswick) [mailto:hhager -at- dc -dot- com]
Listers,
I have question about Numbered lists.
I use numbered lists to identify the sequence of steps in a user procedure.
Nothing new here.
The new element is that when the procedure consists of only a single step, I
also use a numbered list.
For example:
To display the xyz window:
1. From the abc menu in the def window, select xyz.
The progam opens the xyz window.
Another example:
To download the results of your query to Excel:
1. Click the Download Query Results to Excel button in the abc window.
The program exports the results of your query to Microsoft Excel and xxx.
Why do I do this? When a reader looks, browses, or reads my documentation
they can immediately determine which information is a procedure. Every time
a reader sees a numbered list in my documentation, they know it's a
procedure.
