5 exercises — choose the right word when several seem correct: bug vs defect, feature vs functionality, fix vs resolve, update vs upgrade, deprecate vs remove.
Why precision matters in IT English
bug / defect / issue / error — same problem, different formality and precision
feature / functionality / capability — scoped vs. broad vs. organisational
fix / resolve / address / patch — how thoroughly you solved the problem
update / upgrade / patch — magnitude of the change
deprecated / removed / disabled — where in the retirement lifecycle
0 / 5 completed
1 / 5
A team writes a bug report. Which term is most appropriate in a formal QA report submitted to a client? "We identified three ___ in the payment module."
Bug vs. Defect vs. Issue vs. Error — subtle but real differences:
Bug: Informal term for an unintended flaw in code. "We found a bug in the login flow." Universally understood, slightly informal.
Defect: The formal QA/testing term. A defect is a deviation from the requirement. Used in test reports, client contracts, and SLA documents. "3 critical defects were identified during UAT."
Issue: Deliberately vague — can mean a bug, a limitation, a configuation problem, or a disagreement. GitHub calls everything an "issue" for this reason. In formal writing, prefer something more specific.
Error: Technical — the incorrect output produced by the system. A 500 error, a validation error, a parsing error. "The function returns an error if the input is null." Also used for human mistakes: "human error".
In a client-facing QA report: defect is the standard formal term. In Jira/GitHub: issue or bug. In code: error.
2 / 5
A product manager is writing a specification document. Which sentence uses the most precise vocabulary?
Feature vs. Functionality vs. Capability:
Feature: A specific, named unit of product value that a user can interact with. "The export feature", "the dark mode feature", "the search feature." Features are scoped, deliverable, and user-visible. Best in product specs and user stories.
Functionality: The general ability of a system to perform a set of actions. Broader than a feature — "the system's search functionality" (all the things search can do). Slightly more technical. Often overused, making sentences vague: "provide the functionality to" can usually be replaced with a cleaner verb.
Capability: Even broader — organisational or system-level. "The platform has real-time collaboration capabilities." Often used in RFPs, enterprise sales, and high-level architecture docs. More formal than "feature".
Best practice: Use "feature" for a specific user-visible deliverable. Use "functionality" when you mean a whole area of behaviour. Avoid mixing all three in the same sentence — it sounds padded. Option B is simplest and clearest.
3 / 5
In a pull request description, a developer writes: "This PR ___ the race condition in the session handler." Which verb choice sounds most professional and precise?
Fix vs. Resolve vs. Address vs. Patch — register and precision differences:
Fix: The most common term. Direct, informal, widely used. "I fixed the bug." Fine in Slack and most PRs, but slightly too casual for incident reports or client communication.
Resolve: Implies a proper, complete solution after investigation. "The incident was resolved at 14:35 UTC." Standard in post-mortems, SLA communications, and incident tickets. More formal than "fix".
Address: Deliberately careful — means "deal with / take action on" without guaranteeing complete elimination. "This PR addresses the race condition" = we tackled it, but use "resolve" once it is definitively fixed. Common when there may be remaining edge cases.
Patch: Suggests a targeted, sometimes temporary fix — often a workaround rather than a root-cause solution. "We patched the vulnerability" (security). "hotfix" or "patch release". Use when the fix is specifically surgical/minimal.
For a PR dealing with a race condition properly: resolves is the best choice — it signals thorough work.
4 / 5
A release note says: "Node.js 22.0.0 is now available. This is a major ___ from version 20." Which word completes the sentence correctly?
Update vs. Upgrade vs. Patch vs. Release:
Update: Generic term — any change applied to software. Can be small or large. "You have 3 updates available." Neutral, broad, informal. Often used for minor/patch-level changes.
Upgrade: A move to a significantly newer or higher version — usually implies a deliberate migration, potential breaking changes, effort required. "We need to upgrade from Python 3.9 to 3.12." A major version bump is an upgrade.
Patch: A small, targeted fix — specifically the third number in semantic versioning (MAJOR.MINOR.PATCH). "We released a patch for the XSS vulnerability." Also used for operating system security patches.
Release: The act of publishing any version to users. "The new release includes…" — general, covers all types.
Semantic versioning guide: 22.0.0 → 20.x.x is a major upgrade (breaking changes possible). 22.0.0 → 22.1.0 is a minor update. 22.0.0 → 22.0.1 is a patch.
5 / 5
A platform team announcement says: "The v1 API will be deprecated in Q2 and removed in Q4." What is the difference between deprecated and removed?
Deprecate vs. Remove vs. Sunset vs. Disable — a critical sequence:
Deprecated: Still functional — but officially marked as "use this at your own risk, we may remove it." A deprecation notice means: "we recommend you migrate, we will no longer add features, and we plan to remove this." A grace period follows so clients can migrate. The API still works during Q2–Q3.
Removed / Sunset: Actually gone — calling the endpoint returns 404 / 410 Gone. This is the end of the grace period.
Disabled: Turned off but not deleted — often used for feature flags, configuration toggles, or temporarily suspended access.
The standard sequence: Ship → Maintain → Deprecate (announce retirement) → Sunset/Remove → (optionally) Delete source code.
In real life: "The v1 API is deprecated as of March 2026" means it still works but clients should migrate. "The v1 API has been removed" means it will return an error. Clients need to know this difference to prioritise their migration work.