Dictionary API brings together definitions, pronunciations, word forms, terminology questions, and editorial source material. From a Dictionary API lookup, Strawberry can produce an editorial note that distinguishes the source definition, pronunciation, or inflection from the wording your audience should actually see.
A word lookup can settle a factual detail, but it does not decide the right language for a product or audience. It works across the selected Dictionary API tab and the relevant documents, messages, tickets, or reference pages you have open alongside it.
01
Start with an evidence record someone else can follow.
A Dictionary API response is useful to the person checking a word, but an editor or developer needs the selected sense, source context, and unresolved usage question written down before they can act. Strawberry can turn the selected Dictionary API entry, style guidance, and live draft into an editorial note that separates the source meaning from the wording still to approve.
02
Put the surrounding context beside the item under review.
A Dictionary API response cannot tell an editor which sense belongs in the live draft.
That decision may depend on the style guide, the audience, and the terminology already approved elsewhere. Strawberry can place the definition, pronunciation, word form, and editorial context in a review map without treating a suggested wording as final copy.
03
Make the handoff actionable without making it automatic.
A Dictionary API handoff should identify the selected sense, pronunciation, and word form checked, the audience-facing terminology still for editorial approval, and the source entry and style guidance that support it. Strawberry can draft that note so the team spends less time reconstructing the language context and more time making the right call.
04
Make sourced language evidence easy for an editor to assess.
A recurring terminology check can prepare a private exception list for selected documentation pages without changing copy.
No. Strawberry helps with browser-based work in the Dictionary API tab where you are signed in.
Keep terminology edits and publication decisions under editorial review after the cited definition, audience, and downstream documentation have been checked.
Yes. It can turn the selected Dictionary API response, endpoint parameters, and downstream copy or code context into a source-linked review brief.
Yes. Run the Wednesday terminology pass to prepare a private brief of conflicting definitions and unresolved language for an editor to assess.
Dictionary API Strawberry