The missing detail is what the detector’s percentage actually measures. A probability assigned to the whole document and an estimate of how much text was flagged are different outputs. Turnitin, for example, reports the share of qualifying prose it identifies as likely AI-generated. That is not the probability that the author used AI. Without knowing which kind of score you received, it’s hard to interpret what changed between your drafts.
That puts a layer between “what is it looking for?” and the number on the screen: how it combines its judgments into a result. Consider a hypothetical detector that labels individual passages and then reports the fraction flagged. Several passages could sit just below its decision threshold. Small edits could push them just above it, producing a noticeable jump in the displayed percentage even though the underlying judgments barely changed. In that setup, a large score change would not require a large change in predictability.
There’s a related detail worth checking for a troubleshooting note: which text actually counts. Turnitin’s documentation distinguishes long-form prose from material such as code, bullet points, and other unconventional text, which it does not reliably detect. I wouldn’t assume your detector uses that same restriction, but I would look for its equivalent. If your note mixes explanations with commands, headings, and log output, you need to establish whether the result describes the whole note or only selected portions.
For your particular comparison, I’d ask whether the same passages were evaluated in both versions. That’s a different question from whether the wording became more ordinary. If you changed a fragment into a complete sentence, for example, could that have changed what the tool included? That’s a hypothesis to check against its documentation and passage highlights, not an explanation I’d assign to your result without seeing them.
I’d make a narrower claim than @smartrunner453 about overlapping results, too. For your purposes, failure to separate the original notes from matched generated notes would be a strong reason not to trust it on that task. I wouldn’t extend that to every possible use based on that sample. More importantly, I wouldn’t call the displayed percentage a confidence interval unless the tool actually supplies an interval and explains its calculation.
Before spending time identifying supposedly suspicious phrases, I’d want three labels pinned down: what text was evaluated, what was classified, and what the final number means. Otherwise, you could end up explaining a change in the reporting calculation as though it revealed something about your writing.