AI Editor is RixDocs' proofing pass: it reads your text, flags grammar, spelling and clarity issues, and proposes fixes block by block. Unlike a red-underline spellchecker, it explains and rewrites — and unlike an auto-fix tool, it changes nothing until you approve it.
Run a proofing pass
- Click into the paragraph you want checked, or select a range of blocks.
- Open the AI Editor from the Review tab, or use the AI composer at the bottom.
- Ask for proofing — for example: proofread this paragraph for grammar and clarity.
- AI returns its findings and a proposed rewrite for the selected block.
- Accept the fix, refine it with a follow-up instruction, or dismiss it.
The block-level scope is the key design decision. A suggestion touches the paragraph you aimed at — not the document — so proofing a 40-page report is a controlled loop of small, reviewable steps rather than one terrifying global replace.
What it catches
Typical proofing findings:
- Grammar — agreement, tense consistency, missing articles.
- Spelling — including homophone errors a dictionary checker misses ("principle" for "principal").
- Clarity — tangled sentences, passive-voice buildup, ambiguity.
- Consistency — the same term spelled two ways, hyphenation drift.
For a final polish, run the pass section by section: intro, then each chapter, then the conclusion. Focused selections get sharper suggestions than a vague "check everything" prompt.
The provider behind the pass
AI Editor runs on whatever engine you configured in Settings:
| Setup | What proofing costs |
|---|---|
| Built-in Rix AI | Plan credits per action |
| BYO key (OpenAI, Claude, Gemini, DeepSeek, OpenRouter) | Your provider's pricing; no Rixoffice credits |
| Ollama local model | Nothing — fully offline |
If you have not configured a provider yet, the AI provider setup guide walks through all three paths. Privacy-conscious teams can run the entire proofing workflow on a local Ollama model with no network at all.
Pair AI proofing with human review
AI proofing slots into the standard review machinery rather than replacing it:
- Run the AI pass first, clean the obvious issues, then send the document for human comments and track-changes review — reviewers spend attention on substance, not typos.
- AI suggestions are edits; if you want them reviewable by others, apply them with Track Changes on so co-authors see what the machine touched.
- Keep the human in the loop on anything judgment-heavy — tone, claims, legal wording. AI proofing is a first-line filter, not a sign-off.
A note on style instructions
The composer accepts style steering: "proofread and make it more formal", "fix grammar but keep my voice", "tighten without losing details". Being specific about what to preserve is the difference between useful rewrites and generic prose.
What to explore next
- AI Translate to take the polished text into other languages.
- AI credits explained for how actions are metered.
- Track Changes to keep AI edits visible to collaborators.