How to use the Jargon Checker.
A term may be appropriate for experts and confusing for newcomers. Define the audience first, then explain unfamiliar terms at their first useful occurrence.
Make the workflow fit your task.
Identify the reader's likely knowledge and mark terms that block understanding. Keep precise technical language where necessary, adding a plain explanation at the first useful occurrence rather than replacing every term.
- What you provide
- Specialist prose and reader profile.
- What you get
- Unexplained jargon marked with definitions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Explain to a new customer: Configure the webhook and inspect the payload.
Completed example
Set up the webhook, an automatic message sent between services, then check the payload: the data included in that message.
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 specialist terms disappear from expert documentation?
No. Explain only what the intended reader needs. Established terms can make expert documentation shorter and more precise.
What if the plain-language replacement is inaccurate?
Keep the original term and add a brief definition or example. A familiar but imprecise synonym may create more confusion.
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 ↑