Ordinary spaces and trailing whitespace
Recognize accidental separators without destroying intentionally structured text.
Understand the principle
Word spacing belongs to the publication’s text and composition system. Extra ordinary spaces can create irregular holes; a leftover separator at a boundary can be editing debris. The example uses visible explanations rather than a captured plugin screen.
Look in Typography. The publication concept and a plugin issue identifier are related, but are not interchangeable.
Compare the intent, not only the characters
Annual report · [paragraph end]
Annual report [paragraph end] · if the extra spaces were accidental
Schematic teaching example, not a plugin screenshot or a promise of automatic correction.
Review it in Avellio 2.0
Show nonprinting characters in InDesign and inspect the exact range. Separate prose cleanup from literal source code, indentation and tabular alignment. After a deliberate edit, inspect the paragraph again and read the resulting line endings. Read Found and Suggested when offered, or Review in context. Check Text locale; the recommendation itself changes no text. After an intentional manual edit, inspect again.
Use the selected finding’s actual evidence and offered actions. If no suitable supported action exists, make a justified manual decision in InDesign or retain the occurrence. After an edit, inspect again and check nearby composition.
Read the plugin recommendation
Use one space between words; confirm that the extra spacing is not intentional.
Only a run of two or more ordinary spaces qualifies. Tabs and nonbreaking spaces are not normalized by this recommendation.
Read-only advice: verify meaning and locale, edit deliberately when justified, then inspect again.
Review the line ending before removing spaces; they may affect alignment.
Read-only advice: verify meaning and locale, edit deliberately when justified, then inspect again.
When the difference can be intentional
Code, aligned plain text and retained source examples may intentionally contain repeated or boundary whitespace.
What should I verify after deciding?
Preserve meaning and the intended design. If you edited the document, obtain fresh results for the intended scope and policy. If you kept the occurrence, record a supported review decision when useful. A smaller filtered count is not proof of a repair.
Use it in a real workflow
Proof a client document
Find overlooked spacing and editorial inconsistencies without treating every mark as an instruction to change the copy.
Follow the workflow →Combine Preflight, GREP and Avellio
Give each tool a clear job: technical output checks, exact text searches and contextual composition evidence.
Follow the workflow →Deliver a clean document with useful evidence
Finish the inspection, remove the active visualization and save a report that matches the final document.
Follow the workflow →