> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/proofreading/what.md).
# What?
### What is Proofreading?
The Proofreading feature scans your document for technical mistakes that often go unnoticed during manual review. Rather than evaluating legal content or style, it focuses on identifying objective, document-level issues that may lead to confusion, errors, or embarrassment when sharing or finalising a document.
The module combines traditional algorithms (very fast and exhaustive) with Generative AI (slower but smarter) to provide both speed and accuracy, even for very long documents.
ClauseBuddy can detect issues such as:
* Missing or unused definitions (with AI filtering to reduce false positives)
* Errors in number expansions (e.g., *5 (six)*)
* Wrong weekdays and invalid dates (e.g., *Sunday 15 September 2025*, which is actually a Monday)
* Unresolved placeholders, invalid cross-references, or hardcoded paragraph numbers
While the feature may occasionally produce false positives, it provides a fast and reliable way to catch small but important technical issues before finalising a document.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.clausebuddy.com/proofreading/what.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.