Why not just simplify?

Sometimes the words have to stay: they are on the screen, in the contract, in the law. Explain keeps them and makes them clear.

Where do the explanations appear?

In brackets right after the term, and together in a word list at the end of the result.

Can an explanation change the meaning?

Each one is checked: it may say what the term generally means, not claim anything about your situation.

Jargon translator

Keep the words. Explain the jargon.

Explain is a jargon translator that leaves your text exactly as written and adds a short plain explanation after each term your reader would not know, once, the first time it appears.

Explain the jargon

6 free pages a month. No card.

A highlighted term connects to an explanation bubble.

Made for

Technical docs read by people outside the team
Contracts and policies whose terms have to stay
Onboarding material for new colleagues

Before and after

Example: 32 → 67 words · 4 terms explained · every fact kept

Original

When SCIM provisioning is enabled, your IdP becomes the source of truth for user lifecycle. JIT provisioning must be disabled first, or duplicate accounts may be created on the next SAML assertion.

Result

When SCIM (a standard that keeps user accounts in sync between systems) provisioning is enabled, your IdP (identity provider: the service your team signs in with) becomes the source of truth for user lifecycle.

JIT provisioning (creating an account the first time someone signs in) must be disabled first, or duplicate accounts may be created on the next SAML assertion (the message that signs a user in).

Explained: SCIM
Explained: IdP
Explained: JIT provisioning
Explained: SAML assertion

How Explain works

Step 01
The reader is set
Pick who reads it; what counts as jargon depends on them.
Step 02
Passages with jargon are found
Passages every reader can follow are left alone.
Step 03
Explanations are added
Once per term, the first time it appears in the document, in the text's own language.
Step 04
Nothing else may change
The text is compared character by character; each explanation may only say what the term means, never add a claim.

Options

Reader: Pick an audience or describe your own; the level sets how much counts as jargon.

From code, terminal or agent

# REST API
curl https://readable.md/api/v1/transform \
  -H "Authorization: Bearer $READABLE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "tool": "explain", "text": "…", "audience": "newcomer" }'

# Command line
readable explain spec.md --audience newcomer

# MCP tool: explain

API, MCP and CLI docs

Questions

Why not just simplify?: Sometimes the words have to stay: they are on the screen, in the contract, in the law. Explain keeps them and makes them clear.
Where do the explanations appear?: In brackets right after the term, and together in a word list at the end of the result.
Can an explanation change the meaning?: Each one is checked: it may say what the term generally means, not claim anything about your situation.