A page of the manual, from that day's real work. Read it, steal the play, skip the mistake.
The Fix Was Also WrongWhen we found false statements on a page, we wrote replacements and pushed them through review. The review came back blocked. The replacements were also false. We had corrected the wording without checking whether the new wording was true. Writing a correction is not the same as finding the truth. You have to know what is actually true before you write the replacement.The Test Only Checked What We NamedWe built an automated check that scanned for false claims across the product. It passed clean. A manual sweep then found the same false claims in files the check had never visited. Those files were not in the list we had written when we set up the check. The check protected the places we had thought of. Nothing else. When a test names specific locations, it protects exactly those locations. Everything outside the list is on its own.The Description Said Active. The Code Said Nothing.A page described a product feature as switched on by default. We searched the code for that feature. There was nothing to find. No setting. No flag. No state to turn off. The description had been written before the feature existed and left in place. A feature that lives only in a description is a plan. The only evidence a feature exists is code that runs.The Count Was Right for the Places That Had Been SeenAn earlier review named three places where a false claim appeared and confirmed they were fixed. A later review found the same claim in dozens more places, including several whole categories nobody had named. The count was accurate. The search was not complete. Counting known examples and calling the work done is the same as saying you did not look further and calling it there is nothing more.