Typography Rules · practical reference

Capitalization and structural role

Compare headings and names by meaning and role, not only by their letter case.

Understand the principle

Unexpected capitals can reveal inconsistent treatment or pasted source text. A proper name, trademark or a different heading level may intentionally use another form. The supported checks are targeted evidence, not a general grammar or brand-normalization service.

Look in Typography. The publication concept and a plugin issue identifier are related, but are not interchangeable.

Compare the intent, not only the characters

Pattern to review
Annual Report beside Annual report
Possible editorial outcome
A deliberate convention across genuinely comparable headings.

Schematic teaching example, not a plugin screenshot or a promise of automatic correction.

Review it in Avellio 2.0

Compare equivalent structural roles and the intended locale. Check named styles and source meaning before changing case. Verify all affected names after any manual edit. 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

Capitalization logic

Check capitalization against the editorial style; preserve names and acronyms.

Read-only advice: verify meaning and locale, edit deliberately when justified, then inspect again.

When the difference can be intentional

Trademarks, acronyms, quoted material and language-specific conventions can require retained case. Identical visual appearance is not always the goal.

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

Current controls and further reading