Manual breaks and empty paragraphs
Determine the structural purpose before deleting a character.
Understand the principle
A soft return, paragraph boundary and page/column/frame break have different effects. Empty paragraphs can be fragile substitutes for spacing, but they can also belong to intentional structured material. The finding identifies a construct to review.
Look in Typography. The publication concept and a plugin issue identifier are related, but are not interchangeable.
Compare the intent, not only the characters
A heading uses a deliberate forced line break.
The break remains if it expresses the intended heading design.
Schematic teaching example, not a plugin screenshot or a promise of automatic correction.
Review it in Avellio 2.0
Show nonprinting characters and inspect both sides of the boundary. Compare the paragraph style, intended flow and page design. If an edit is justified, check pagination and adjacent paragraphs after recomposition. 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
Review the manual line break before removing it; it may be intentional.
Read-only advice: verify meaning and locale, edit deliberately when justified, then inspect again.
Review paragraph spacing before removing an empty paragraph.
Read-only advice: verify meaning and locale, edit deliberately when justified, then inspect again.
Review the intended page, column or frame flow before changing this break.
Read-only advice: verify meaning and locale, edit deliberately when justified, then inspect again.
When the difference can be intentional
Titles, poetry, addresses, forms and chapter starts can legitimately use manual structure. Reducing a counter by deleting all breaks can damage the design.
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
Combine Preflight, GREP and Avellio
Give each tool a clear job: technical output checks, exact text searches and contextual composition evidence.
Follow the workflow →Handle overset and frame fit
Understand whether a proposed correction changes paragraph composition or the terminal frame boundary.
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 →