> 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/why.md). # Why? ### Why use Document Cleanup? Document Cleanup helps you resolve technical issues within a single document without changing its writing style or content. It focuses on structural and metadata-related corrections that would otherwise need to be done manually one by one.\ You can use it to update headers or footers, replace placeholders, manage Track Changes, clean up spacing or empty paragraphs, remove metadata, or apply protection—all in one pass. Because it performs mechanical corrections only, Document Cleanup is most useful when you need to prepare or standardize a document technically, but not when context-sensitive editing or content adjustments are required. #### ✅ When you should use it: **• To prepare a document for distribution or sharing**\ Removing metadata, accepting or rejecting all Track Changes, and cleaning up empty elements ensures the document is technically clean. **• To update recurring document elements quickly**\ Replacing headers, footers, or placeholders across the entire file saves time compared to searching manually. **• To clean up structural artifacts**\ Fixing issues like consecutive spaces, empty paragraphs, or manually inserted paragraph numbers helps keep the document tidy and consistent. **• To normalise Track Changes information**\ Accepting or rejecting all changes at once, or swapping the Track Changes author, is useful before review or hand-off. **• To apply document protection**\ Adding protection helps secure the file before sharing it externally. **• To combine documents efficiently**\ Appending or prepending a document can streamline workflows that rely on merging content. *** #### ❌ When you shouldn’t use it: **• If the document needs content-level or stylistic editing**\ Document Cleanup does not modify text, style, formatting, layout, or structure beyond removing empty or unnecessary elements. **• If edits require judgement or context**\ It can’t make decisions about meaning, phrasing, formatting choices, or sensitive content. **• If only a single minor change is required**\ Running the full cleanup workflow may be unnecessary when a manual adjustment is quicker. --- # 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/why.md?ask=&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.