Reading two drafts side by side is how small edits slip through

You know the feeling. Someone sends back a revised contract, or a second draft of an article, and you are supposed to spot what changed. You open both versions, scroll, squint, and compare paragraph by paragraph. Twenty minutes later you are fairly sure nothing important changed, which is not the same as knowing. The tool that answers this properly is older than most of the web. The Unix diff command dates to 1974, and git diff is the same idea applied to code: find the longest sequence of lines both versions share, and report everything else as an addition or a removal. You do not need a terminal or a repository to use that idea, though. A browser-based text diff checker does the same comparison on pasted text. Here is how to read one. Paste the original in the left box and the revised version in the right, then compare. Lines that only exist in the original show in red. Lines that only exist in the revision show in green. Everything else stays plain, which means your eyes go straight to the edits instead of re-reading the whole document. The part most people miss is the word level. A changed line is not always a rewritten line. If one number in a contract changed from 5 to 6, the whole line looks different at a glance, but only one word actually moved. A good checker highlights that exact word inside the changed pair, so a one-word edit costs you one second instead of one re-read. Two options are worth knowing about. Ignore whitespace treats lines as equal when they differ only in indentation or trailing spaces, which is what you want after code was reformatted or text was copied between tools that disagree about tabs. Ignore case does the same for capitalisation, handy when comparing SQL or config keys that someone uppercased. Both hide noise; neither hides a real edit. A practical example makes it concrete. Take a short club notice. The original says the club meets Friday at 5 pm. The revision says 6 pm and adds a line that sign-up closes on March 1. A diff of those two versions shows exactly one changed pair and one added line, and the summary reads one line added, one line removed, three unchanged. That summary is the whole point: it tells you the size of the change before you read a single line of it. If you want to try it on your own drafts, this free text diff checker runs the whole comparison in your browser, with the word-level highlights and a downloadable unified diff you can paste into a review or ticket: https://www.theutilityhub.online/tools/text-diff-checker Nothing is uploaded, so contracts and drafts stay on your machine. That matters more than it sounds: the documents you most want to compare are usually the ones you least want to send to a server. Next time someone sends you "just a few small tweaks", do not take their word for it. Run the diff. It takes ten seconds, and it is the difference between fairly sure and knowing.