145
edits
Natecole54 (talk | contribs) (→Pedagogical Approaches: Added "Renguette" to "Hovde" sfn to link correctly to the bibliography reference.) |
Natecole54 (talk | contribs) (→Characteristics of Technical Communication: Removed "very" before "easily understood" for clarity purposes.) |
||
Line 9: | Line 9: | ||
=== Characteristics of Technical Communication === | === Characteristics of Technical Communication === | ||
Because technical communication is intended to guide an audience, it must be assembled in such a way that it is | Because technical communication is intended to guide an audience, it must be assembled in such a way that it is 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 that is delivered logically is well-organized and clear and can be approached in a manner that 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 Documents == | == Technical Documents == |
edits