46
edits
Natecole54 (talk | contribs) m (→Bibliography: Updated the year in the "Bolter" reference to match the citation.) |
Ebyington3 (talk | contribs) (→Characteristics of Technical Communication: added citation at end of) |
||
Line 38: | Line 38: | ||
=='''Technical Communication Strategies'''== | =='''Technical Communication Strategies'''== | ||
==='''Characteristics of Technical Communication'''=== | ==='''Characteristics of Technical Communication'''=== | ||
Technical communication is meant to guide an audience and must be easily understood. Successful technical documentation is accurate, logically sound, and appropriate.{{sfn|Perelman|1998}} Communication can be said to be accurate in two different understandings: accurate in description and accurate in content. Accurate descriptions are easy to understand. Accurate content provides for the intended result. Communication delivered logically is well-organized, clear, and will be coherent for most users. Technical information that is appropriate contains elements and steps that are suitable for the intended purpose and audience.{{ | Technical communication is meant to guide an audience and must be easily understood. Successful technical documentation is accurate, logically sound, and appropriate.{{sfn|Perelman|1998}} Communication can be said to be accurate in two different understandings: accurate in description and accurate in content. Accurate descriptions are easy to understand. Accurate content provides for the intended result. Communication delivered logically is well-organized, clear, and will be coherent for most users. Technical information that is appropriate contains elements and steps that are suitable for the intended purpose and audience.{{sfn|Perelman|1998}} | ||
====Standards Compliant==== | ====Standards Compliant==== |
edits