Catch Mistakes Before You Hit Send

You finished the email, the Slack message, the proposal.

3 steps 2-5 minutes per check, plus the social cost of avoiding embarrassing mistakes

The Problem

You finished the email, the Slack message, the proposal. You read it once. It looks fine. You send it. Thirty seconds later you see the typo in the second sentence, the 'their' that should be 'there,' the sentence that made sense in your head but reads like word soup to everyone else. Spell check caught nothing because every word was technically spelled correctly. The mistake was in meaning, not spelling.

How Chapeta Handles This

Paste the text into Chapeta before you send it. It catches grammar errors, spelling that spell check misses (homophones, wrong-word errors), unclear phrasing, and tone mismatches. It shows you what it would change and why, so you learn the pattern instead of just accepting a correction.

How to Proofread Before Sending

3 steps to get it done

  1. 1

    Paste the text

    Copy whatever you are about to send — email, Slack message, proposal paragraph, social post — and paste it into Chapeta. No setup, no file attachment. Just paste and ask.

  2. 2

    Ask for the check

    Say 'Proofread this' for a general check, or be specific: 'Check for grammar and tone — this is going to a client' or 'Is this too long for a Slack message?' Different contexts need different kinds of review.

  3. 3

    Apply and send

    Chapeta returns corrections with brief explanations. Accept the ones that matter, ignore the ones that are just stylistic preference, and send with confidence.

Example

You type

Proofread this email before I send it to a client. Check grammar, clarity, and tone. Flag anything that could come across as unprofessional or unclear. 'Hi Tom, just following up on our call yesterday, I think the timeline we discussed makes sense but want to make sure we're aligned on the deliverables before we kick things off, specifically around the data migration piece which I think could take longer then expected if we don't scope it properly upfront. Let me know you're thoughts.'

Chapeta returns
## Issues Found

1. **Run-on sentence** — The main sentence covers three ideas without a break. Split it after 'makes sense.'

2. **'then' → 'than'** — 'longer then expected' should be 'longer than expected.' Spell check won't catch this because 'then' is a real word.

3. **'you're' → 'your'** — 'Let me know you're thoughts' should be 'your thoughts.' 'You're' means 'you are.'

4. **Tone note** — 'I think could take longer' hedges twice (think + could). For a client, pick one: either 'I think it will take longer' or 'it could take longer.' Double hedging sounds uncertain.

## Corrected Version

Hi Tom,

Just following up on our call yesterday. I think the timeline we discussed makes sense, but I want to make sure we're aligned on deliverables before we kick things off.

Specifically, the data migration piece could take longer than expected if we don't scope it properly upfront. Happy to put together a more detailed breakdown if that would help.

Let me know your thoughts.

Without Chapeta

Read it yourself and miss the errors because your brain autocorrects what you wrote. Send it. Notice the typo later. Hope nobody else noticed. They did.

Time saved 2-5 minutes per check, plus the social cost of avoiding embarrassing mistakes

FAQ

Try the Proofread Before Sending workflow in Chapeta