Work on documents with AI

Write, proofread, and edit documents with GPT-5 and Claude

Edit anything with AI, and review each change inline.

The AI document editor

A fully integrated AI agent

Revise can see and edit everything you can, in the same interface.

In the investor update sent on May 3, the company said the pilot program would begin in July and remain limited to three cities through the end of the quarter. But a later section describes customer feedback from the pilot as if the rollout had already expanded nationwide in June, creating a timeline that could hold

The report also says subscription revenue fell 12 percent because pricing stayed flat, then later credits strong revenue growth to a price increase that supposedly took effect during the same period. An editor reviewing the draft would immediately flag that mismatch, since both explanations cannot be true without more context about when the change happened and which customer segment it affected.

I'll review this for inconsistencies

Reviewing your report...

Use the smartest AI models

Choose between the latest models from OpenAI, Anthropic, and xAI.

Work on existing documents

Import your Word documents and Google Docs

Proofread, revise, and perfect your existing documents.

Extract content from any PDF

Convert PDFs into rich text documents using multi-modal LLMs.

MIT Guide to Lock Picking

Ted the Tool

September 1, 1991

Distribution

Permission to reproduce this document on a non-profit basis is granted provided that this copyright and distribution notice is included in full. The information in this booklet is provided for educational purposes only.

August 1991 revision.

Chapter 1

It's Easy

The big secret of lock picking is that it's easy. Anyone can learn how to pick locks.

The theory of lock picking is the theory of exploiting mechanical defects. There are a few basic concepts and definitions but the bulk of the material consists of tricks for opening locks with particular defects or characteristics. The organization of this manual reflects this structure. The first few chapters present the vocabulary and basic information about locks and lock picking. There is no way to learn lock picking without practicing, so one chapter presents a set of carefully chosen exercises that will help you learn the skills of lock picking. The document ends with a catalog of the mechanical traits and defects found in locks and the techniques used to recognize and exploit them. The first appendix describes how to make lock picking tools. The other appendix presents some of the legal issues of lock picking.

The exercises are important. The only way to learn how to recognize and exploit the defects in a lock is to practice. This means practicing many times on the same lock as well as practicing on many different locks. Anyone can learn how to open desk and filing cabinet locks, but the ability to open most locks in under thirty seconds is a skill that requires practice.

Make it your own

A word processor that gets to know you

Revise learns and remembers your preferences the more you use it.

Use my pronouns: they/them.

I like direct feedback, not fluffy praise.

Default to US spelling.

Short paragraphs help me skim.

My audience is first-time founders.

Avoid exclamation points.

Always format my papers in APA 7

I am interviewing for climate-tech roles.

Use the Oxford comma.

Keep summaries to 5 bullets max.

Call me Chris, not Christopher

Examples should feel practical, not academic.

I write in a warm, precise tone.

Mention accessibility when it matters.

I usually want a concise first draft.

Prefer examples that include the schema diff, rollback plan, on-call escalation path, and the user-visible failure mode.

Keep email drafts under 120 words.

I like calm, confident wording.

If you make a performance claim, cite the benchmark setup, workload shape, sample size, and baseline you compared against.

Default to concrete API contracts with request and response payloads, pagination rules, and idempotency semantics instead of analogies.

Please don't call me a power user.

I prefer metric units.

I am applying to product design roles.

Call out any breaking API change, data backfill, index migration, or client version gate before you recommend shipping it.

Keep introductions short.

I like examples from education and healthcare.

Avoid corporate jargon.

I prefer plain English over buzzwords.

Use title case only for slide titles.

I am dyslexic, so clarity beats cleverness.

I trust p95s, error budgets, queue depth, and incident counts more than adjectives like robust, seamless, or enterprise-grade.

Write requirements as numbered acceptance criteria with edge cases, retry behavior, and explicit non-goals, not a narrative paragraph.

I work best with one recommendation at a time.

Include p95 latency budgets, concurrency assumptions, queue depth limits, and throughput targets so the recommendation is operationally credible.

Assume a US enterprise environment with SSO, SCIM, audit logs, retention policy, and SOC 2 or HIPAA review questions.

I prefer em dashes sparingly.

Keep code comments short, literal, and close to the invariant they protect; do not narrate obvious control flow.

I like interview answers to sound conversational.

If there is a tradeoff, tell me directly in terms of consistency, blast radius, migration cost, and developer ergonomics.

Save your prompts

Fine-tune your favorite prompts, then use them with a single click.

Try Revise with one of these prompts

Proofread a document...Change writing tone...Simplify text...Translate a document...Summarize a document...Paraphrase text...