docs-de-slopify

Read through the text line by line and revise manually, replacing emdashes with semicolons or commas and recasting formulaic phrases like "Here's why" or "It's not X, it's Y". Regex and scripts cannot do this reliably because context and tone judgment are required.

Common tells include emdash overuse, "Here's why" lead-ins, "It's not X, it's Y" contrast formulas, forced enthusiasm like "Let's dive in!", pseudo-profound openers like "At its core", and unnecessary hedges like "It's worth noting".

No. Automated pattern matching fails because fixing slop requires context-aware sentence recasting, tone consistency, and judgment calls about when a pattern is acceptable. Each line must be reviewed and revised manually.

One or two emdashes per document are fine, and sometimes an emdash is genuinely the right punctuation choice. The goal is eliminating overuse, not enforcing a blanket ban; technical accuracy and clarity always take priority over style rules.

Do not alter code examples, sacrifice technical accuracy for style, or strip necessary structure like headers and lists. Thorough, clear explanations are not slop; the focus is on prose patterns, not content depth.