product-example 2 linked patterns checked
Microsoft Support: Accept or reject tracked changes in Word
Documents reviewing tracked changes one by one, moving to previous or next change, accepting, rejecting, accepting or rejecting a single change, and accepting or rejecting all changes.
Read with a purpose
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Change review | Choose change review when users are inspecting proposed edits, diffs, suggestions, tracked changes, or review comments before accepting, rejecting, applying, or requesting changes. | Selecting a change reveals the base content, proposed content, author, context, and exact scope affected by a decision. | Microsoft Word documents moving through tracked changes and accepting or rejecting individual or all changes. |
| Editable AI output | Choose editable AI output when the primary object is generated output after creation and users need to revise, review, save, copy, or apply that output. | The generated draft, user edits, tracked changes, source mappings, citations, review status, and final output state are modeled as distinct data rather than one mutable text blob. | Supports accept and reject actions for visible tracked edits. |
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: Microsoft Support. Last checked: .