> 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/document-cleanup/what.md).

# What?

**Document Cleanup** helps you technically tidy and standardize your document.\
This feature allows you to apply multiple cleanup actions at the same time, reducing the need to perform each task manually.

You can use Document Cleanup for a variety of maintenance operations. Examples include adjusting the author information for Track Changes, applying document protection, removing consecutive spaces and addressing other common issues.\
Each operation can be enabled or disabled individually, giving you full control over what gets changed.

Document Cleanup is intended to support routine preparation or finalization of documents.\
\
By applying a consistent set of cleanup actions, you can ensure that your document follows the required technical standards before sharing, reviewing, or archiving it.

<figure><img src="https://2099470129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZy5Ct2oSKmmXnCxUY8qC%2Fuploads%2F8iPpfzwSZAySEAAwKGq2%2FScreenshot%202025-11-17%20at%2015.19.28.png?alt=media&amp;token=943cfc5c-50cc-41b9-8e0e-09d7a51449e2" alt="" width="563"><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.clausebuddy.com/document-cleanup/what.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
