# Summary of Technical Writing One pre-class

<br />

> [!NOTE]
> **Estimated Time:** 2 minutes

Congratulations! You've completed the pre-class portion of Technical Writing
One, which covered the following fundamental principles of technical writing:

| Section | Lesson |
|---|---|
| [Words](https://developers.google.com/tech-writing/one/words) |
| [Words](https://developers.google.com/tech-writing/one/words) | Define new or unfamiliar terms. |
| [Words](https://developers.google.com/tech-writing/one/words) | Use terms consistently. |
| [Words](https://developers.google.com/tech-writing/one/words) | Avoid ambiguous pronouns. |
| [Active voice](https://developers.google.com/tech-writing/one/active-voice) |
| [Active voice](https://developers.google.com/tech-writing/one/active-voice) | Prefer active voice to passive voice. |
| [Clear sentences](https://developers.google.com/tech-writing/one/clear-sentences) |
| [Clear sentences](https://developers.google.com/tech-writing/one/clear-sentences) | Pick specific verbs over vague ones. |
| [Clear sentences](https://developers.google.com/tech-writing/one/clear-sentences) | Reduce *there is* and *there are*. |
| [Short sentences](https://developers.google.com/tech-writing/one/short-sentences) |
| [Short sentences](https://developers.google.com/tech-writing/one/short-sentences) | Focus each sentence on a single idea. |
| [Short sentences](https://developers.google.com/tech-writing/one/short-sentences) | Convert some long sentences to lists. |
| [Short sentences](https://developers.google.com/tech-writing/one/short-sentences) | Eliminate unneeded words. |
| [Lists and tables](https://developers.google.com/tech-writing/one/lists-and-tables) |
| [Lists and tables](https://developers.google.com/tech-writing/one/lists-and-tables) | Use a numbered list when ordering is important and a bulleted list when ordering is irrelevant. |
| [Lists and tables](https://developers.google.com/tech-writing/one/lists-and-tables) | Keep list items parallel. |
| [Lists and tables](https://developers.google.com/tech-writing/one/lists-and-tables) | Start numbered list items with imperative words. |
| [Paragraphs](https://developers.google.com/tech-writing/one/paragraphs) |
| [Paragraphs](https://developers.google.com/tech-writing/one/paragraphs) | Establish a paragraph's central point in the first sentence. |
| [Paragraphs](https://developers.google.com/tech-writing/one/paragraphs) | Focus each paragraph on a single topic. |
| [Audience](https://developers.google.com/tech-writing/one/audience) |
| [Audience](https://developers.google.com/tech-writing/one/audience) | Determine what your audience needs to learn. |
| [Audience](https://developers.google.com/tech-writing/one/audience) | Fit documentation to your audience. |
| [Documents](https://developers.google.com/tech-writing/one/documents) |
| [Documents](https://developers.google.com/tech-writing/one/documents) | Begin a document by stating its scope, audience, and key points. |
| [Documents](https://developers.google.com/tech-writing/one/documents) | Aim the document at your audience. |
| [Punctuation](https://developers.google.com/tech-writing/one/documents) |
| [Punctuation](https://developers.google.com/tech-writing/one/documents) | Use commas to force short pauses within a sentence or to separate items in a list. |
| [Punctuation](https://developers.google.com/tech-writing/one/documents) | Use a period to separate distinct thoughts; use a semicolon to unite highly related thoughts. |
| [Punctuation](https://developers.google.com/tech-writing/one/documents) | Use a colon instead of a period in a sentence that introduces a list. |

If your organization offers the instructor-led portion of Technical Writing One,
you're now ready for that class. If your organization doesn't offer the
instructor-led portion of Technical Writing One, note that Google occasionally
offers the course. See the [Announcements page](https://developers.google.com/tech-writing/announcements) for
details.