# 7. Reviewing and Editing

This category addresses reviewing and editing processes and guidelines, and general usability. It encompasses the various levels of editing, including revising, substantive editing, copyediting, and proofreading. Additionally, it covers common grammatical and mechanical errors.

## Reading

| Technical Communication Today          | Technical Communication                        |
| -------------------------------------- | ---------------------------------------------- |
| 19. Revising and Editing for Usability | 13. Evaluating and Testing Technical Documents |

## Learning Objectives

* Describe the levels of editing and how they are applied to technical documents.
* Describe the different types of usability testing in the review process.
* Recall common proofreading practices.

### Recall key terms and facts about the reviewing and editing of information products  

Key facts about editing a document: 

1. The names of the four levels of editing  
2. How to determine the appropriate level of edit for a document 

The importance of: 

1. Document cycling 
2. Usability testing

Key facts about usability testing:  

1. The types of usability testing used in evaluating technical writing products 
2. The four questions used to help design usability tests 

The common copyediting symbols and what they mean 

### Understand the concepts and guidelines used when reviewing and editing information products  

The focus of Level 1 editing: revising and the guidelines to apply 

The focus of Level 2 editing: substantive editing and the guidelines to apply  

The focus of level 3 editing: copyediting and the guidelines to apply  

The focus of level 4 editing: proofreading and the guidelines to apply  

How different usability tests are conducted: 

1. Read-and-Locate 
2. Understandability tests 
3. Performance tests 
4. Safety tests 

The common grammatical errors found in technical documents 

The guidelines for creating and editing global technical documents (according to Leininger and Yuan) 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kelly-ohara7.gitbook.io/technical-communication-study-guide/reviewing-and-editing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.