Test page

Test Correctify on a text full of mistakes

Correctify is installed? Here is a meeting recap with 11 mistakes, several of them hidden in a heading, bold or colored text. Select it, run the correction, then check against the answer key below the editor.

Quick recap of monday's meeting

Hi everyone,

Thanks to all of you who where able to attend. Here is a short summery of what we discused.

Key decisions

  • Budget: it's final version has been approved, but every expenses must be justified.
  • Schedule: deliveries are pushed back by two weeks, unless something unexpected happen.
  • Training on the new tool will take place on thursday October 8 at 2 pm in room B.

Please send me you're availability before friday, I will definately add it to the agenda.

Best regards,
Camille Martin
Project manager

Answer key: the 11 mistakes in the text
  1. monday'sMonday's heading
  2. where ablewere able bold
  3. summerysummary
  4. discuseddiscussed
  5. it's final versionits final version
  6. every expensesevery expense underlined
  7. unexpected happenunexpected happens italic
  8. thursdayThursday highlighted
  9. you're availabilityyour availability underlined
  10. fridayFriday
  11. definatelydefinitely

How to run the test

  1. 1

    Select the text

    Click in the editor, then Ctrl + A to take everything, or select a single paragraph to start small.

  2. 2

    Run the correction

    With the Windows app: Ctrl + Alt + C. With the Chrome or Firefox extension: right-click, then "Correct the text".

  3. 3

    Check the result

    Open the answer key below the editor and look for what is left. Also check that headings, bold and colors are still there.

What this text puts to the test

Mistakes caught inside formatting

"where able" is in bold, "monday's" is in a heading, "thursday" is highlighted. Correctify only replaces the letters that change: after the correction, the bold text should still be bold and the heading still a heading. If formatting was lost somewhere, that is what I want to hear about.

Grammar traps

Homophones ("where" or "were", "it's" or "its", "you're" or "your"), agreement ("every expense", "something happens") and missing capitals on days of the week. These are the mistakes small AI models sometimes let through. If one survives, run the test again with a stronger model in the settings.

A signature on several lines

The name and the job title are separated by simple line breaks (Shift + Enter), like most email signatures. After the correction, each line should stay in place: no merged lines, no extra blank line.

And your own text

The editor is yours: delete everything and paste one of your emails. This page sends nothing. The correction goes from your Correctify to the AI provider of your key, like everywhere else.

Not installed yet?

You need Correctify to run the test

The Windows app corrects in any software, this page included. Free, no account, installed in two minutes. On a Mac or Linux? The Chrome and Firefox extensions work too.

Download for Windows

Frequently asked questions

Nothing happens when I run the correction

First check that the text is actually selected in the editor, then that your API key is saved in the Correctify settings. Without a key, the shortcut or the right-click opens the settings instead of correcting.

Why is nothing underlined in red in the editor?

I turned off the browser spell checker in the editor. Its red squiggles would show the mistakes before the correction, and you could no longer see what Correctify found on its own.

Correctify missed a mistake, is that normal?

It can happen: the result depends on the AI model in use. Fast models are very good at spelling but sometimes miss a distant agreement. Run the test again with a stronger model, and if the mistake survives, tell me which one through the contact page.

Is formatting really kept?

With the Windows app and the Chrome and Firefox extensions, yes: Correctify compares the text before and after, and only replaces the characters that change. Headings, bold, colors and links are left alone. The editor's "Source code" button lets you check it in the HTML.