Understanding findings: evidence, intent, and false positives
The full operational, safety, workflow, reporting, locale, and issue reference.
Avellio findings are evidence, not commands. Use the same five questions for every issue:
- What exactly did Avellio detect?
- Why can the pattern be risky?
- Does the surrounding copy or layout show intentional use?
- Is the proposed action Safe, Review, Manual Only, or Blocked?
- What should the document look like after the decision?
The cards below demonstrate that reasoning for common findings.
Double spaces — a usually clear text defect
Avellio sees: two or more normal spaces in a prose context.
Why it matters: repeated spaces create irregular word spacing and are especially visible in justified copy.
Example: The annual report → The annual report
Action: FIX a clear normal-space run can enter Safe Clean.
Review when: the text is plain-text alignment, source code, a form, or another intentionally spaced structure.
Done when: the sentence has one intended separator and the new audit no longer reports the occurrence.
Number–unit spacing — protect the pair
Avellio sees: a recognized number and unit separated by a normal space.
Why it matters: the value and unit can split across lines.
Example: 12 kg → 12 kg
Action: FIX an exact recognized pair can receive a non-breaking space through Safe Clean.
Review when: the token is an identifier, mathematical expression, code, unusual unit, or protected narrow-space convention.
Done when: the value remains typographically correct and cannot separate from its unit.
Numeric range dash — meaning before appearance
Avellio sees: a hyphen-minus between clear numeric range endpoints.
Why it matters: editorial typography normally distinguishes a range from a hyphenated word or minus sign.
Example: 2024-2026 → 2024–2026
Action: FIX a guarded numeric or page range can enter Safe Clean.
Review when: the text is a negative number, ISBN, URL, email, filesystem path, identifier, phone number, or expression.
Done when: the dash communicates the intended relationship without changing the data.
Straight and locale-specific quotes — direction matters
Avellio sees: ASCII quotes or quotation marks that do not match the resolved locale.
Why it matters: professional typography distinguishes opening, closing, apostrophe, and nested quote forms.
Example: an apostrophe inside don't can be locally unambiguous; a double quote at the edge of a nested quotation may not be.
Action: REVIEW exact apostrophes or one-character quote replacements can enter Review Queue. Complete quote pairing remains manual.
Review when: the text includes measurements, code, nested quotations, mixed languages, primes, or deliberately straight marks.
Done when: opening and closing direction, nesting, and locale convention are correct across the complete quotation.
Punctuation spacing — locale can reverse the answer
Avellio sees: space before punctuation or no space after punctuation where prose normally expects one.
Why it matters: spacing errors interrupt reading and can indicate pasted or concatenated text.
Action: FIX clear Western-prose space-before cases can enter Safe Clean. REVIEW a precise missing space after punctuation can enter Review Queue.
Review when: French punctuation, decimal values, URLs, email addresses, abbreviations, initials, filenames, or code are involved.
Done when: the spacing follows the resolved language convention and the token still has its original meaning.
Empty paragraphs and manual indents — fix the structure, not only the symptom
Avellio sees: hard returns, spaces, or tabs used as layout controls.
Why it matters: manual spacing is fragile when copy reflows or styles change.
Action: REVIEW these findings are item-by-item Review Queue candidates, not Safe Clean batch actions.
Review when: blank paragraphs intentionally separate special content, tabs align tabular material, or spaces are part of a fixed-format source.
Done when: intentional layout uses Paragraph Space Before/After, first-line indent, or configured tabs wherever practical.
Soft returns and layout breaks — composition can be intentional
Avellio sees: forced line, column, frame, or page break characters.
Why it matters: manual breaks can become incorrect after edits and can hide structural problems.
Action: REVIEW soft returns can be inspected individually. CAUTION column, frame, and page breaks are Manual Only.
Review when: a title, poem, address, controlled headline, or planned page transition depends on the break.
Done when: the break remains only because it expresses an intentional composition decision.
Widows, orphans, and short final lines — solve the page, not the counter
Avellio sees: isolated lines or paragraph endings below the configured character or width threshold.
Why it matters: weak endings interrupt rhythm and can create distracting white space.
Action: REVIEW edit copy, adjust Keep Options, composition, measure, or spacing. These are not automatic text fixes.
Review when: the paragraph is a caption, list item, dialogue, narrow column, display text, or intentionally short statement.
Done when: the page reads and balances naturally, even if an accepted exception remains in the report.
Rivers and rag quality — visual evidence requires visual review
Avellio sees: aligned word spaces in justified text or abrupt adjacent line-length changes in ragged text.
Why it matters: both patterns can pull attention away from the content.
Action: REVIEW change copy, measure, justification, hyphenation, or tracking carefully in InDesign.
Review when: the sample is short, the layout is highly expressive, the frame is unusually narrow, or the reported geometry is visually harmless.
Done when: the complete text block looks stable at reading size, not merely when the issue count reaches zero.
Rogue font — exact range versus intentional emphasis
Avellio sees: locally applied font information that differs from the paragraph style.
Why it matters: unnamed font overrides weaken global style control and can cause brand or production inconsistency.
Action: REVIEW an exact range-level font override can be offered as a Style Cleanup reset to the paragraph style.
Review when: a symbol font, fallback glyph, logo treatment, mathematical character, or deliberate typographic contrast is involved.
Done when: intentional variation is represented by a named character style or documented exception, and accidental variation is removed.
Tracking, leading, and spacing drift — confirm the canonical style
Avellio sees: local tracking, leading, paragraph spacing, or indentation that differs from the applied style or established pattern.
Why it matters: repeated local adjustments make the document difficult to maintain and can hide a style-definition problem.
Action: REVIEW exact supported properties can be reset individually to the paragraph style. Broad or uncertain cases remain manual.
Review when: optical headline adjustment, fitting, tabular alignment, or a deliberate local composition exception is present.
Done when: the canonical style expresses the shared rule and only defensible local exceptions remain.
Style drift — repair the design system deliberately
Avellio sees: one named style appearing in several visual variants.
Why it matters: the same style name no longer guarantees the same appearance or role.
Action: REVIEW Style Drift is preview/manual-only. Avellio does not choose which variant should become canonical.
Review when: the style intentionally supports more than one context or inherited legacy content has not yet been migrated.
Done when: the team chooses a canonical rule, updates style definitions or creates meaningful variants, and removes unexplained local drift.
Dates, numbers, currencies, and abbreviations — protect meaning
Avellio sees: inconsistent or locale-sensitive semantic patterns.
Why it matters: inconsistency reduces trust and, in data-heavy documents, can change interpretation.
Action: REVIEW Avellio provides evidence, locale hints, and examples. Automatic conversion remains preview-only.
Review when: source data uses a contractual format, several markets are represented, accounting rules apply, or the pattern is an identifier rather than prose.
Done when: the editorial convention is explicit, values retain their meaning, and the same rule is used throughout the intended scope.
Release sourceThis page was generated from the Markdown companion of the verified distribution PDF.