humanize

/humanize

Revise the requested prose in place so it sounds like the author and so a reader gets it on the first pass. This is an editing command, not an AI-detection claim and not a report the user has to process.

Two jobs, one pass:

1. Remove the machine register. Formulaic transitions, inflated framing, announcements that something is important, stacked hedging, generic praise.
2. Make it plainer. Replace a term with what it does. Say the thing instead of naming the method that did it. Default to the plainer wording and make each technical term earn its place.

Neither job may change what is true.

Resolve the target and the audience

• Use the file, passage, or scope in $ARGUMENTS. For all, include prose relevant to the current deliverable and exclude rendered output, dependencies, vendored material, data, and code.
• Plain is relative to a reader, so establish who is reading: the audience named in $ARGUMENTS, or the one the document itself names, or ask in one line. A specialist audience raises the bar for which terms are shared; it does not license jargon, and it never licenses a sentence that only makes sense to someone who already knows the answer.
• Read applicable project instructions and any documented voice profile (voice-profile.md, STYLE.md, or the local equivalent) before editing.
• Use American spelling unless the target or the venue says otherwise: center, normalization, hematocrit, behavior, labeled, analyze. British forms creep in from quoted sources and from earlier drafts, so check rather than assume.

Resolve the register

Register is how a sentence sounds: contractions, person and voice, how much jargon the reader shares, whether naming a method is the job or a lapse. It differs enough between a slide and a manuscript that one set of defaults cannot serve both, and the difference is not a single axis — a machine learning conference paper and a clinical physics manuscript disagree with each other about as much as either disagrees with a talk.