Call of Duty

Small formatting slips-underscores in prose, wrong short words, misplaced apostrophes-look like typos and distract readers. Below are tight rules, quick checks, and many copy-ready before/after examples for emails, essays, and texts.

If you need a fast check, scan the quick fixes and paste the rewrite templates into your draft.

Quick fix

Replace call_of_duty with the form appropriate to context: Call of Duty for the game title, call of duty for a general phrase, and never use underscores in normal prose. Apply the same quick checks to short words and apostrophes (your/you're, their/there/they're, its/it's, than/then).

call_of_duty → Call of Duty (title) or call of duty (general phrase); underscores belong in code or filenames.
Short-word test: expand contractions (you're → you are) to check correctness.
Apostrophe test: expand to see if it's a contraction; otherwise use the possessive form.
Before sending: run this mini-checklist - Title? Contraction? Possession? Underscore/Hyphen?

Core explanation: why underscores and wrong casing matter

Underscores like call_of_duty are a technical convention for filenames, variables, and handles. In normal prose use spaces and correct capitalization. Title case signals proper names (Call of Duty); lowercase signals a general noun or phrase (call of duty).

Ask: am I naming a product, writing a file path, or describing an obligation? That decides casing and spacing.

Filename/variable: call_of_duty.png or call_of_duty (ok in code).
Product/title: Call of Duty (capitalize main words).
Generic phrase: call of duty (as in "the call of duty").

Wrong: I played call_of_duty last night.
Right: I played Call of Duty last night.
Right: He answered the call of duty and helped the victims.

Hyphens, underscores and spacing (quick rules)

Hyphens join words that act as a single modifier before a noun (a well-known study). Underscores belong to filenames or code. In prose, avoid underscores and use hyphens only when grammar calls for them.

Compound adjective before noun: a high-quality product.
Compound after noun: the product is high quality (no hyphen).
Use underscores only in code or filenames: final_report_v2.docx is fine as a file name; avoid it in sentences.

Wrong: I submitted the final-report today.
Right: I submitted the final report today.
Wrong: Please find final_report_v2 attached.
Right: Please find the final report (v2) attached.
Wrong: She is a well known author.
Right: She is a well-known author.

Apostrophes and contractions: common traps

Apostrophes mark possession (John's book) or contractions (it's = it is/it has). They do not form plurals. Expand contractions to test: if "it is" fits, use it's; otherwise use its for possession.

it's = it is / it has. its = possessive.
Plural: cats, not cat's. Possession for plural: students' lounge.
Group possession: the team's decision = the decision of the team.

Wrong: Its been a long semester.
Right: It's been a long semester.
Wrong: I left my coat's in the office.
Right: I left my coats in the office.
Wrong: The students's project won the prize.
Right: The students' project won the prize.

Short-word confusions: your/you're, their/there/they're, than/then

Tiny words change meaning. Read aloud and replace with expanded forms: you're → you are; they're → they are; then → at that time. For their/there/they're ask: possession, place, or contraction?

You're test: expand to "you are." If it fits, use you're.
Their/there/they're: possession → their; place → there; contraction → they're.
Than vs then: than for comparison, then for sequence or time.

Wrong: Your going to love this.
Right: You're going to love this.
Wrong: I would rather go then stay.
Right: I would rather go than stay.
Wrong: Their is a typo in the summary.
Right: There is a typo in the summary.

Fix your sentence: step-by-step rewrites you can copy

Use this 4-step method: (1) spot the suspicious token; (2) pick the rule (title, possessive, contraction, filename); (3) rewrite and read aloud; (4) pick formal or casual tone.

Tip: when a product name appears, match the official capitalization.
If an underscore appears, replace with a space and use parentheses for version numbers in prose.

Wrong: I uploaded the slides called project_plan_final on the drive.
Right: Diagnosis: filename used in prose →
Rewrite: I uploaded the slides titled "Project Plan - Final" to the drive.
Wrong: Their is a mistake in the budget.
Right: Diagnosis: wrong short word →
Rewrite: There is a mistake in the budget.
Wrong: He lost it's chance at promotion.
Right: Diagnosis: incorrect contraction →
Rewrite: He lost its chance at promotion.
Wrong: Please review call_of_duty stats in the analysis.
Right: Diagnosis: underscores and title confusion →
Rewrite: Please review the Call of Duty statistics in the analysis.

Try your own sentence

Test the whole sentence, not just the phrase-context often makes the correct form clear.

Real usage and tone: ready-to-send examples (work / school / casual)

Registers demand different fixes. Below are paired examples you can paste and adapt.

Work: be precise with titles and attachments; spell out filenames only when necessary.
School: follow style guides-no underscores, correct possessives, correct plural agreement.
Casual: contractions are fine, but short-word errors still confuse readers.

Work - Wrong: Please review call_of_duty mentions in the market analysis.
Work - Right: Please review mentions of Call of Duty in the market analysis.
Work - Wrong: Your responsible for Q3 deliverables.
Work - Right: You're responsible for the Q3 deliverables.
School - Wrong: their study shows inconsistent results.
School - Right: Their study shows inconsistent results.
School - Wrong: The datas inconsistent across trials.
School - Right: The data are inconsistent across trials.
Casual - Wrong: Your the MVP tonight!
Casual - Right: You're the MVP tonight!
Casual - Wrong: We should of stayed for the encore.
Casual - Right: We should've (should have) stayed for the encore.

Examples: dense bank of wrong/right pairs to scan and copy

Copy the "right" sentence into your drafts. Each pair targets a single error so you can swap subjects and objects while keeping the fix.

Wrong: I built a mod for call_of_duty.
Right: I built a mod for Call of Duty.
Wrong: Your welcome to join the meeting.
Right: You're welcome to join the meeting.
Wrong: I left my coat's in the office.
Right: I left my coats in the office.
Wrong: Its obvious we need more data.
Right: It's obvious we need more data.
Wrong: I would rather go now then later.
Right: I would rather go now than later.
Wrong: There are many reasons, their unclear though.
Right: There are many reasons; they're unclear, though.
Work - Wrong: Attached: final_report_v3.docx
Work - Right: Attached: final report (v3).
School - Wrong: The teams strategy failed to address bias.
School - Right: The team's strategy failed to address bias.
Casual - Wrong: Cant wait to see you!
Casual - Right: Can't wait to see you!

Memory tricks and quick pre-send checklist

Run these checks before you hit send.

Expand test: replace contractions (you're → you are). If it reads sensibly, keep the contraction.
Possessive test: try the "of it" swap (the cat's whiskers → the whiskers of the cat).
Comparison vs sequence: comparing → than; ordering/timing → then.
Underscore scan: underscores in a sentence → likely filename or code. Replace with spaces and correct title case.
Plural vs possessive: plurals don't get apostrophes (two teachers, not two teacher's).

Checklist example: (1) Titles? (2) Underscores? (3) Apostrophes? (4) your/you're & their/there/they're? (5) than/then? (6) Hyphenation?

Similar mistakes worth checking (quick catches)

Beyond underscores and apostrophes, watch capitalization, commas with quotes, who/whom, and affect/effect.

Capitalization: proper nouns (Call of Duty) vs common nouns (a call of duty).
Comma with quotation marks: He said, "Let's go," not He said "Let's go".
Who vs whom: who performs the action; whom receives it. Try replacing with him/her to test.
Affect (verb) vs effect (noun): The change affected the outcome (verb); The effect was clear (noun).

Wrong: she played call_of_duty and won.
Right: She played Call of Duty and won.
Wrong: The quote said "we did it" and left out the comma.
Right: The quote said, "We did it," and left out the comma.

FAQ

Is call_of_duty ever correct in prose?

Only in technical contexts (filenames, variable names, code snippets). In normal writing use Call of Duty (title) or call of duty (general phrase).

How can I remember its vs it's?

Expand it's to "it is" in the sentence. If the expanded sentence makes sense, use it's; otherwise use its.

What's the fastest way to stop mixing up their/there/they're?

Ask: possession? → their. Place? → there. Can I expand to "they are"? → they're. Reading aloud helps.

Should I leave filenames as-is in emails?

If you must show a filename, put it in quotes or code-style text (final_report_v2.docx). In prose prefer a human-readable form (final report (v2)).

Can grammar checkers fix these automatically?

They catch many mistakes but can misjudge tone and specialized names. Use them to flag issues, then confirm the correction fits your intended meaning.

Want a quick sentence check?

Paste a sentence with underscores, contractions, or short-word confusion into a grammar checker, then apply the rewrite templates above to fit your tone.

Small edits-fixing an underscore, an apostrophe, or a short-word swap-improve clarity and credibility immediately.