You delete the wrong sentence and notice immediately. On another day, you discover that a section changed hours ago while several people were editing. These are different recovery problems, even though both begin with the wish to get something back.
Start with the smallest clear correction
Undo is useful for reversing a recent action when you understand what it will affect. Check the result instead of repeatedly pressing it until the screen looks familiar. A sequence of reversals can remove work you wanted to keep.
If the change is older or its origin is unclear, inspect the document’s available history. Do this before making a broad restoration that could affect other people’s contributions.
Inspect an earlier state before restoring it
Google’s version history documentation explains viewing, restoring, and copying earlier versions in its editors. Viewing earlier versions requires permission to edit the file. The page also describes naming versions so they remain easier to identify.
A restore and a copy are different choices. If you only need to examine an old paragraph, a separate copy may make comparison easier without immediately replacing the shared document’s current state. Check the controls and available options in the product you are using.
Coordinate when the file is shared
Explain the intended correction to collaborators before a broad restoration. Record which section is missing and which later work should remain. If possible, recover the needed passage while keeping unrelated changes intact, then review the result together.
Our guide to choosing document permissions helps with the surrounding workflow. Recovery is easier when people know who can edit and how substantial changes are discussed. The goal is the correct current document, not merely the oldest version you can find.