how do you handle documentation that is wrong or out of date

Outdated docs are a hazard (they cause wrong fixes and field errors) — how you handle them shows responsibility. Your approach: 1) DON'T just ignore it — a wrong doc is worse than no doc because it's trusted. 2) FLAG it clearly (mark as deprecated/needs update) so nobody follows it in the meantime. 3) CORRECT it — get the right info (from the expert, the data, or engineering), verify it, and update the doc. 4) TRACE impact — did anyone else use the wrong version? Notify them. 5) Fix the root cause of why it went stale (version control, review process) so it doesn't recur (Lesson 4 CAPA thinking). The one-line frame: 'I treat outdated documentation as a live hazard — I flag it so nobody trusts it, then I correct it and fix why it went stale.' It shows you value documentation as a safety/quality asset, which is exactly the GPS standard.