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 am leaning towards generating a
> report since "run a report" sounds a little like a cliche or
> "jargony" but
> just to cover all bases, I also thought that I would put in a
> cross-reference in my index that says "Running a report" -
> see "Generating", but. . .
>
> Thoughts at all on this?
This is similar to the "appears" versus "displays" argument.
One runs a program to generate a report. The report is the final product;
it is not something to be run. Try this angle: Think of the report as a
summary. A summary is not run, it is generated.
How about "Creating a report"? That seems to cover both bases.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.