How to use the Style Guide Compliance Checker.
Quote the relevant style rule beside each finding. This makes the review actionable and helps distinguish a genuine violation from an editor's preference.
Make the workflow fit your task.
Supply the relevant style rules and review the draft against them one at a time. Attach each finding to an exact passage, the applicable rule and a proposed correction.
- What you provide
- Draft and supplied style guide.
- What you get
- Rule violations with suggested fixes.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Style guide: use sentence case headings. Draft heading: Getting Started With Reports.
Completed example
Suggested heading: Getting started with reports. Reason: sentence case rule.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can it distinguish a rule from an editorial preference?
Ask each finding to cite the supplied rule. Suggestions without a matching rule should be labeled optional improvements.
Why is a correctly styled name being changed?
Add official names and approved exceptions to the brief. A general capitalization rule should not override a documented exception.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑