INSERT creates rows, UPDATE changes matching rows and DELETE removes them. A WHERE condition is the boundary of a write. Inspect the same condition in a SELECT before running an unfamiliar update, and keep a transaction available when you need to inspect the result before committing.
RETURNING exposes the rows a write affected. It can return keys, changed values or expressions without a second query. An UPDATE that matched no rows isn't a database error; decide whether that result meets the application's expectation.
Do not replace a partial update with a table-wide rewrite. The fixture includes canceled and shipped orders alongside open work. A broad condition can silently change history. These exercises check the final table state as well as the returned values, so changing the intended row plus unrelated rows won't pass.
Increment only the named account; assigning 5 discards its existing balance.