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.
I prefer the "File>Save" convention as well. Of course I explain this
method in the Preface under a "Conventions Used in This Book" section.
In fact I explain what everything is including, bold text, notes,
cross-references, procedures, et al.
I also write a "Dialog Box Conventions" section in which I describe each
of the dialog elements that appear in the software (spin boxes. option
buttons, drop-down boxes, etc.), and I explain how to use each one. I
would have never thought to use these until I received feedback from
users who wondered why they couldn't type inside a drop-down list box,
or they didn't know that they could type a valid value in a spin box.
However, I am now starting to think that I may need to explain menu
selections in detail. I am not joking when I tell you we had a user
phone because she did not know where the "Start" button was when I
wrote, "To open the program, go to Start>Programs..."
The only problem with this is that our software uses a lot of sub-menus
before reaching a desired command. When written out, it appears "wordy"
and somewhat confusing.
If they would just read the darn Preface! (A guy can dream can't he?)