Currently, terminology is being used in ways that conflict.

• edit check = feedback on content authored in the current edit session
• edit suggestion = feedback on content loaded from the published article

vs

• edit check = high-priority feedback (i.e. reporting issues that would likely lead to reversion)
• edit suggestion = lower-priority feedback

This reflects multiple underlying intents about configuration:

• For content authored in the current edit session, default to low verbosity so as not to overwhelm the editor. This means reporting only high-priority issues
• For content loaded from the published article, by default set verbosity to zero. This means not reporting on any issues at all.
• In either case, enable a way to increase verbosity. This means reporting on issues not reported by default.

Done

• Agree on a standard definition of edit check and edit suggestion
• Define other terms needed for the discussion of configuration intents