How to use the Restaurant Menu Proofreader.
Menu proofreading should check names, prices, units and consistency as well as spelling. Flag unclear allergen or dietary markings for kitchen confirmation instead of guessing from a dish name.
Make the workflow fit your task.
Compare item names, descriptions, prices, units and repeated entries across the menu. Flag conflicts with their locations and distinguish typographic fixes from facts needing kitchen or pricing approval. Do not infer allergen status from names alone.
- What you provide
- Menu text and approved dish facts.
- What you get
- Spelling, consistency and contradictory ingredient findings.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Menu lists Tomato soup — USD 6 and tomato Soup — USD 7 elsewhere. No portion difference stated.
Completed example
Text inconsistency: Tomato soup versus tomato Soup. Price conflict: USD 6 versus USD 7. Needed confirmation: whether the entries describe the same portion and which price is current. Suggested capitalization if they are the same item: Tomato soup. Price remains unresolved pending owner confirmation.
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.
Should two similar menu entries be standardized automatically?
First confirm whether they represent different portions, preparations or service periods. Similar wording does not prove duplication.
Why did proofreading leave a conflicting price unresolved?
The correct amount requires an authoritative source. Report both values and ask the responsible owner to confirm.
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 ↑