Documenting program flow

Subject: Documenting program flow
From: Chris Morton <salt -dot- morton -at- gmail -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 9 Jan 2015 13:20:23 -0800




These are not commands, per se. What are they called in documenting program
flow control... *operatives*?


> Chris
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word |


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

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @


Previous by Author: Re: Instructional design vs. machinist uptake
Next by Author: Reality check: "mS" time increment?
Previous by Thread: RE: Interactive PDFs from Word -- best solution to a painful process?
Next by Thread: Re: Documenting program flow

What this post helpful? Share it with friends and colleagues:

Sponsored Ads