Term lists into a glossary

Definitions with a source.
Internal usage stays internal.

Turn term lists, training material, and project documents into a glossary: definitions, where each term applies, and how look-alike concepts differ. No invented definitions or industry standards; unsourced entries are listed for verification and internal usage is labelled as internal.

Sourced definitionsInternal labelledLook-alikes compared
01

Paste term list

0 / 12,000 charactersMinimum 80

Content is used only for this AI request and is not intentionally stored by this site.

02

Review the glossary

Your result will appear here

We write each definition, mark where it applies and whether it is internal only, add comparisons for confused terms, and list every entry with no source.

SAMPLE OUTPUT

Here is exactly what you receive.

This is the complete output for the source text in the demo above: a completeness score, itemised revision notes, entries marked incomplete or unsourced and why, and the structured glossary. It is a demonstration, not a customer case.

SAMPLE

Glossary result (sample)

Completeness score88/100
+50
01

Mark “pretty much the same thing” as incomplete

No definition of SLO was given. The original wording is kept and the entry is marked incomplete rather than fused into a polished explanation.

02

Separate the internal target from the external promise

99.95% is an internal target and 99.9% is an external commitment. They are labelled separately so the internal figure is never quoted as a promise.

03

Move unsourced figures to the verification list

Neither availability figure has a measurement method, period, or source. Both move to the list instead of standing as fact in the body text.

Structured glossary
# Glossary (draft)

## SLA
- Definition: the service availability level promised externally. The source gives the figure 99.9%.
- Applies to: not stated in the source — to verify
- Source: to verify (none given)

## SLO
- Definition: the source says “pretty much the same thing” and gives no definition; this entry is incomplete
- Internal usage: the 99.95% figure is an internal target, not an external commitment
- Distinction from SLA: to verify (the source does not state one)

## Incident
- Definition: any case where the service is unavailable (as stated in the source)
- To verify: whether partial degradation counts

## Canary release
- Definition: a release that goes to part of the traffic first (as stated in the source)
- To verify: traffic proportion, ramp schedule, and rollback conditions

## Items to verify
- Sources for the SLA and SLO definitions and how they differ
- How 99.9% and 99.95% are measured and over what period
- Whether “incident” includes partial degradation
- The ramp rules for canary releases

WHAT DRAFTING DOES

A glossary removes ambiguity. It does not manufacture authority.

01

Definitions stop where the source stops

A half-written definition stays half-written and is marked incomplete, rather than being rounded out into something that sounds sourced.

02

Usage stays separate from definition

The same word means different things in different contexts. Where it applies is more useful than one broad definition.

03

Look-alikes belong side by side

Definitions alone do not remove confusion. Putting the two terms next to each other and stating the difference does.

WHY IT IS WORTH DOING

A wrong definition in a glossary gets quoted as the standard forever.

01

An invented definition is the hardest to correct

Once it is in the glossary it becomes team consensus. Every document copies it and nobody checks the original source again.

02

Internal usage passed off as standard misleads newcomers

Write “this is how the industry does it” and new colleagues take that into external conversations, then discover the other side uses a different meaning entirely.

03

Without comparisons, confusion survives

Two terms both defined but never distinguished still leave the reader unsure which one to use.

Note: common practice for glossaries is one entry per term with a definition, the contexts where it applies, and related concepts, plus explicit distinctions for terms that get confused. Industries and organisations may define the same term differently. This site drafts documents only; it quotes no external standard text and does not adjudicate between conflicting definitions.

DRAFTING DEMO

The same term list, organised.

Before

SLA is the service availability we promise, usually 99.9%. SLO is pretty much the same thing; internally we aim for 99.95%. An incident is any case where the service is unavailable. A canary release means releasing to part of the traffic first. Everyone please remember these.

Drafted
# Glossary (draft)

## SLA
- Definition: the service availability level promised externally. The source gives the figure 99.9%.
- Applies to: not stated in the source — to verify
- Source: to verify (none given)

## SLO
- Definition: the source says “pretty much the same thing” and gives no definition; this entry is incomplete
- Internal usage: the 99.95% figure is an internal target, not an external commitment
- Distinction from SLA: to verify (the source does not state one)

## Incident
- Definition: any case where the service is unavailable (as stated in the source)
- To verify: whether partial degradation counts

## Canary release
- Definition: a release that goes to part of the traffic first (as stated in the source)
- To verify: traffic proportion, ramp schedule, and rollback conditions

## Items to verify
- Sources for the SLA and SLO definitions and how they differ
- How 99.9% and 99.95% are measured and over what period
- Whether “incident” includes partial degradation
- The ramp rules for canary releases

Demo sample: “pretty much the same thing” is marked as an incomplete definition, the internal target is separated from the external commitment, and unsourced figures move to the verification list. Paste your list to get your version (sign-in required; one credit per run).

WHY YOU CAN TRUST IT

We put “no invented definitions” into our product principles.

Definitions are never completed

A half-given definition stays half-given and is marked incomplete, instead of being rounded into a polished sentence with no source behind it.

Internal usage is labelled

A meaning that only holds inside one team or company is written as internal, never as an industry standard or general practice.

Unsourced entries get listed

Definitions, figures, and standard references with no source go straight to the verification list rather than being written from impression.

Content is not stored

Submitted text is used for this single AI request and is not intentionally persisted. See the Privacy Policy.

FAQ

Ask these before you pay.

Will you complete a definition that is only half written?

No. A partial definition is kept as written and marked incomplete, then listed for verification. Completing the sentence makes it look sourced when it is not.

Can an internal definition be written as an industry standard?

No. A meaning that only holds inside the team is labelled as internal usage so it is never taken as a general standard outside.

What if one term has several definitions?

We keep what the source gives without merging them, flag the conflict for verification, and leave the choice to you. Adjudicating between definitions is not something we can do.

What does one draft cost?

One credit per run, usually done in seconds, returning the glossary, revision notes, and items to verify.

Do credits expire?

No. Credits never expire — whatever you do not use carries over to the next cycle instead of resetting.

Is there batch processing or an API?

Not yet. Each run processes one document and consumes one credit; there is no bulk upload or API today. Email us with your use case and we will assess it.

Is my content stored?

Not intentionally. Text is used for this single AI request only. See the Privacy Policy.

What content fits?

Term lists for onboarding, cross-team alignment of meanings, glossary appendices in project docs, terminology alignment between product and engineering — any list that needs to become a real glossary.

SIMPLE PRICING

Prove the value before you upgrade.

Starter

$9/ month

For an occasional publishing cadence, with a focused monthly credit allocation.

  • 50 optimization credits per monthly renewal
  • Complete GEO analysis
  • Chinese and English output
  • Markdown export

Pro

Recommended$29/ month

For frequent publishers who iterate on content continuously.

  • 250 optimization credits per monthly renewal
  • Complete GEO analysis
  • Chinese and English output
  • Markdown export

Advanced

$79/ month

Our largest monthly credit allocation, for the heaviest continuous usage.

  • 1,000 optimization credits per monthly renewal
  • Complete GEO analysis
  • Chinese and English output
  • Markdown export
Loading localized prices

Credits never expire: unused credits carry over instead of resetting. Credits apply to this site only and are not shared with other sites.

Prices shown are USD baselines; final currency, taxes, and discounts are determined by Paddle for the checkout location.