Technical Writing

Every type of writing has a goal.

• TRUE

• FALSE

Tags

CCSS.L.8.6

CCSS.L.9-10.6

CCSS.W.7.2D

CCSS.W.8.2D

CCSS.W.9-10.2D

Technical writing is intended to communicate to a specific ______________, for a specific ______________.

• audience, purpose

• product, report

• report, message

Tags

CCSS.RI.7.5

CCSS.RI.8.3

CCSS.RI.8.5

CCSS.RI.9-10.3

CCSS.RI.9-10.5

Concise, clear and _________ are the key components of an effective technical writing.

• understandable

• complex

• complicated

Tags

CCSS.RI.11-12.5

CCSS.RI.8.3

CCSS.RI.8.5

CCSS.RI.9-10.3

CCSS.RI.9-10.5

Limit paragraph, words and sentence length

• clarity

• conciseness

• accuracy

Tags

CCSS.RI.7.7

CCSS.RI.8.7

CCSS.RI.9-10.7

CCSS.RL.8.7

CCSS.RL.9-10.7

The importance of correct grammar and mechanics

• conciseness

• accuracy

• organization

Tags

CCSS.RI.11-12.8

CCSS.RI.8.7

CCSS.RI.9-10.7

CCSS.RL.8.7

CCSS.RL.9-10.7

Avoiding vague, obscure and/or connotative words

• accuracy

• conciseness

• clarity

Tags

CCSS.RI.7.7

CCSS.RI.8.7

CCSS.RI.9-10.7

CCSS.RL.8.7

CCSS.RL.9-10.7

Limit and/or define use of abbreviations, acronyms, and jargon

• ethics

• conciseness

• accuracy

• clarity

• organization

Tags

CCSS.RI.8.7

CCSS.RI.9-10.7

CCSS.RL.11-12.8

CCSS.RL.8.7

CCSS.RL.9-10.7

The information provided must be what the users are looking for.

• clear

• accurate

• relevant

• complete

Tags

CCSS.RI.8.7

CCSS.RI.9-10.7

CCSS.RL.11-12.8

CCSS.RL.8.7

CCSS.RL.9-10.7

The grammatical structure of your technical document should be free from any kind of ambiguities.

• clear

• accurate

• complete

• correct

Tags

CCSS.L.3.1A

CCSS.L.6.1A

CCSS.L.6.1C

CCSS.L.6.1D

Readers use these documents to learn how to perform certain tasks or gain technical information, so they should be easy to follow and organized in a way that’s easy to refer back to as questions come up.

• cause and effect

• division

• Problem-solution

Tags

CCSS.RI.11-12.5

CCSS.RI.6.5

CCSS.RI.7.5

CCSS.RI.8.5

CCSS.RI.9-10.5