Stay organized with collections
Save and categorize content based on your preferences.
Congratulations! You've completed the pre-class portion of Technical Writing
Two, which covered the following intermediate principles of technical writing:
Consider writing the caption before creating the
illustration.
Constrain the amount of information in a single drawing.
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.
Construct detailed prompts by defining a role for the LLM, a
target audience, a document type, and a specific goal.
Revise documents by prompting an LLM to reorganize content,
copy edit for errors, and identify stylistic or logical
issues.
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 for
details.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-05 UTC."],[[["\u003cp\u003eTechnical Writing Two emphasizes intermediate technical writing skills such as adopting style guides, understanding audience needs, and effective document structuring.\u003c/p\u003e\n"],["\u003cp\u003eThis course covers techniques for clear and concise writing, including outlining, using task-based headings, progressive disclosure of information, and creating effective visuals with captions.\u003c/p\u003e\n"],["\u003cp\u003eIt also guides on writing understandable code samples with relevant comments and providing diverse documentation for different user types.\u003c/p\u003e\n"],["\u003cp\u003eThe course involves a pre-class portion which you have completed and an optional in-class component for practical application of learned principles.\u003c/p\u003e\n"],["\u003cp\u003eIndividuals can participate in the in-class portion either within their organization or through free public courses if unavailable internally.\u003c/p\u003e\n"]]],["Technical Writing Two covers intermediate technical writing lessons, including adopting a style guide, understanding your audience, and using peer editors. Key actions involve outlining or free-form writing followed by organization, introducing document scope, using task-based headings, and progressively disclosing information. It emphasizes writing concise, clear code comments, providing examples and anti-examples, continuous revision, catering to different user categories, and comparing with familiar concepts. It also stresses tutorial structure and illustrative clarity.\n"],null,["\u003cbr /\u003e\n\n| **Estimated Time:** 1 minute\n\nCongratulations! You've completed the pre-class portion of Technical Writing\nTwo, which covered the following intermediate principles of technical writing:\n\n| Section | Lesson |\n|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [Self-editing](/tech-writing/two/editing) |\n| [Self-editing](/tech-writing/two/editing) | Adopt a style guide. |\n| [Self-editing](/tech-writing/two/editing) | Think like your audience. |\n| [Self-editing](/tech-writing/two/editing) | Read documents out loud to yourself. |\n| [Organizing large docs](/tech-writing/two/large-docs) |\n| [Organizing large docs](/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. |\n| [Organizing large docs](/tech-writing/two/large-docs) | Outline first. Alternatively, write free form and then reorganize. |\n| [Organizing large docs](/tech-writing/two/large-docs) | Introduce a large document by explaining what it covers. |\n| [Organizing large docs](/tech-writing/two/large-docs) | Choose headings that describe the task your reader is working on. |\n| [Illustrating](/tech-writing/two/illustrations) |\n| [Illustrating](/tech-writing/two/illustrations) | Consider writing the caption *before* creating the illustration. |\n| [Illustrating](/tech-writing/two/illustrations) | Constrain the amount of information in a single drawing. |\n| [Illustrating](/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. |\n| [Creating sample code](/tech-writing/two/sample-code) |\n| [Creating sample code](/tech-writing/two/sample-code) | Create sample code that is accurate, clear, short, easy to understand, and well-commented. |\n| [Creating sample code](/tech-writing/two/sample-code) | Consider providing not only examples but also anti-examples. |\n| [Creating sample code](/tech-writing/two/sample-code) | In tutorials, provide code samples that demonstrate a range of complexity. |\n| [Using LLMs in tech writing](/tech-writing/two/llms) |\n| [Using LLMs in tech writing](/tech-writing/two/llms) | Construct detailed prompts by defining a role for the LLM, a target audience, a document type, and a specific goal. |\n| [Using LLMs in tech writing](/tech-writing/two/llms) | Revise documents by prompting an LLM to reorganize content, copy edit for errors, and identify stylistic or logical issues. |\n| [Using LLMs in tech writing](/tech-writing/two/llms) | Generate concise summaries by identifying the summary's purpose, target audience, and style. |\n\nThe *in-class component* of Technical Writing Two helps you practice\nintermediate technical writing principles.\n\nIf your organization offers the instructor-led portion of Technical Writing Two,\nyou're now ready for that class. If your organization doesn't offer the\ninstructor-led portion of Technical Writing Two, note that Google occasionally\noffers the course. See the [Announcements page](/tech-writing/announcements) for\ndetails."]]