# Summary of Technical Writing Two

<br />

> [!NOTE]
> **Estimated Time:** 1 minute

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

| Section | Lesson |
|---|---|
| [Self-editing](https://developers.google.com/tech-writing/two/editing) |
| [Self-editing](https://developers.google.com/tech-writing/two/editing) | Adopt a style guide. |
| [Self-editing](https://developers.google.com/tech-writing/two/editing) | Think like your audience. |
| [Self-editing](https://developers.google.com/tech-writing/two/editing) | Read documents out loud to yourself. |
| [Organizing large docs](https://developers.google.com/tech-writing/two/large-docs) |
| [Organizing large docs](https://developers.google.com/tech-writing/two/large-docs) | Determine whether to organize a large amount of information into a single long document or a collection of shorter documents. |
| [Organizing large docs](https://developers.google.com/tech-writing/two/large-docs) | Outline first. Alternatively, write free form and then reorganize. |
| [Organizing large docs](https://developers.google.com/tech-writing/two/large-docs) | Introduce a large document by explaining what it covers. |
| [Organizing large docs](https://developers.google.com/tech-writing/two/large-docs) | Choose headings that describe the task your reader is working on. |
| [Illustrating](https://developers.google.com/tech-writing/two/illustrations) |
| [Illustrating](https://developers.google.com/tech-writing/two/illustrations) | Consider writing the caption *before* creating the illustration. |
| [Illustrating](https://developers.google.com/tech-writing/two/illustrations) | Constrain the amount of information in a single drawing. |
| [Illustrating](https://developers.google.com/tech-writing/two/illustrations) | Focus the reader's attention on the relevant part of a picture or diagram by describing the takeaway in the caption or by adding a visual cue to the picture. |
| [Creating sample code](https://developers.google.com/tech-writing/two/sample-code) |
| [Creating sample code](https://developers.google.com/tech-writing/two/sample-code) | Create sample code that is accurate, clear, short, easy to understand, and well-commented. |
| [Creating sample code](https://developers.google.com/tech-writing/two/sample-code) | Consider providing not only examples but also anti-examples. |
| [Creating sample code](https://developers.google.com/tech-writing/two/sample-code) | In tutorials, provide code samples that demonstrate a range of complexity. |
| [Using LLMs in tech writing](https://developers.google.com/tech-writing/two/llms) |
| [Using LLMs in tech writing](https://developers.google.com/tech-writing/two/llms) | Construct detailed prompts by defining a role for the LLM, a target audience, a document type, and a specific goal. |
| [Using LLMs in tech writing](https://developers.google.com/tech-writing/two/llms) | Revise documents by prompting an LLM to reorganize content, copy edit for errors, and identify stylistic or logical issues. |
| [Using LLMs in tech writing](https://developers.google.com/tech-writing/two/llms) | Generate concise summaries by identifying the summary's purpose, target audience, and style. |

The *in-class component* of Technical Writing Two helps you practice
intermediate technical writing principles.

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