How should documentation be updated when code changes?

• A. Do nothing
• B. Update related docs, diagrams, and API references to reflect changes, and maintain versioned documentation
• C. Remove all earlier docs
• D. Only update README

Answer: (B)

Documentation should stay in sync with code changes. When you modify code, update everything that describes how to use or interact with it—API references, diagrams, usage examples, and developer guides—so they reflect the new behavior and interfaces. Keeping documentation versioned ties each set of docs to a specific release, helping users know which changes apply to which version and providing a clear upgrade path. This approach keeps the information accurate, searchable, and trustworthy for both users and contributors. Doing nothing leaves docs stale and misleading; removing older docs eliminates useful context; updating only the README misses many API and architectural details that users rely on.