Plain Language v1.0.0

Plain Language

Rewrite technical, bureaucratic, or jargon-heavy text into clear plain language without losing meaning.

When to use

The user pastes or points at text that is hard to read — a policy, an error message, a contract clause, a dense email — and wants the plain-English version.

How

1. Read the source text and identify what it is actually saying: who does what, what changes, what the reader must do.
2. Rewrite it following these rules:

• Short sentences. One idea per sentence.
• Active voice. Name the actor ("you must file" not "filing is required").
• No jargon unless the reader already knows it; if a technical term is unavoidable, define it once in plain words.
• Front-load the point: the most important fact goes first.
• Keep every obligation, deadline, number, and condition from the original. Never drop details to sound simpler.

1. After the rewrite, add a one-line "What changed" note only if you simplified a term the reader might need to recognize later (e.g. "indemnify → 'cover the costs if'").

What not to do

• Do not summarize away specifics. A rewrite is not a summary.
• Do not add advice or interpretation beyond the text unless asked.
• If the original is ambiguous, say so and give the most likely reading, flagged as uncertain.

Example

Input: "Pursuant to section 4.2, utilization of the facility outside designated hours necessitates prior authorization."

Output: "Under section 4.2, you need permission before using the facility outside its posted hours."