Eight worked examples

1. Preflight passes, but the page still looks weak

The output profile reports no blocking condition. A body paragraph still ends in a tiny fragment and another column has a distracting whitespace corridor. Inspect White Space, locate the actual lines and consider the paragraph role before changing anything.

If an eligible solver proposal is offered, compare the target measure and surrounding reflow. The useful finish is a better page with fresh evidence, not just a higher score. Follow the composition route.

2. The team wants every three-dot sequence changed

First decide whether the rule also applies to code, quoted archival material and deliberate leaders. If the exact expression and replacement are genuinely approved for a controlled scope, use a tested GREP query. Otherwise review individual occurrences in context.

Avellio’s Three-dot ellipsis can help locate supported findings. Do not infer a universal automatic text-cleanup command from the presence of the rule. Finish by checking copy and line endings.

3. A report mixes 1,200.50 and 1 200,50

Confirm whether these represent the same value and which convention the report intends to use. Inspect Typography under the actual policy, consult the source owner and review comparable examples.

A date such as 03/04/2026 adds a factual ambiguity that no separator replacement can resolve by itself. Compare the locale context and retain the original meaning.

4. The hero image is missing

Start with the Links/Preflight evidence, restore the intended asset and check its appearance. Avellio’s typography results do not validate the correct photograph or crop. Finish with the relevant output checks and a clean proof.

5. Imported text contains many overrides

Identify the intended styles and deliberate emphasis before resetting anything. Use Style catalog and supported override evidence. For one eligible exact property, Preview reset makes a live document change that you finish with Apply or Revert.

A selected finding does not authorize clearing every override or merging style definitions. Follow the formatting route and inspect reflow after any retained change.

6. A name appears in two spellings

Ask the responsible editor and verify an authoritative source. Once the correct spelling and contexts are known, Find/Change can help locate occurrences. Similar strings can still refer to different people or quoted sources.

The useful finish is approved content, not a clean typographic counter. Avellio and Preflight do not establish the fact.

7. Overset has two very different possible remedies

One proposal may adjust supported paragraph typography. Another eligible proposal may expand the terminal frame’s bottom edge while preserving paragraph typography. Read the strategy before previewing.

Review details is panel-only for typographic alternatives; Preview in layout can be a live frame-fit change. Check page boundaries and nearby objects, finish Apply/Revert, inspect again and verify native overset. Follow the frame-fit route.

8. A publication report says FINAL, but one chapter was closed

Reconcile the report with the intended chapter list. The Book route queues eligible chapters already open in InDesign; a closed chapter is not silently inspected.

FINAL records completed collection, not complete editorial acceptance. Resolve missing/partial evidence and warnings before claiming the publication was covered. Follow the publication route.

Sources and current boundaries

Avellio guidance describes build 2.0.5 source review within the 2.0.0 documentation collection. Read the current delivery boundaries and compatibility evidence. This comparison does not claim fresh native-host acceptance.