> 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/text-compare/what.md).

# What?

### What is Text Compare?

Text Compare allows you to visually compare two pieces of text, regardless of their origin. You can compare content from entire Word or PDF files, selected paragraphs or manually pasted text. The tool clearly highlights all differences between the original and the modified version, indicating insertions, deletions and moved content.

You can open the comparison screen directly within ClauseBuddy, select your two text sources, and immediately see a side-by-side result. Optional settings allow for basic configuration while keeping the interface clean and minimal.

The resulting comparison can be reviewed on screen, exported to Word or PDF, or inserted back into your currently opened document in MS Word.

<figure><img src="https://2008338008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvCie6hbzZ43iIDC6fdNB%2Fuploads%2FLl5feXWgSu4huDOThuP5%2FScreenshot%202025-08-12%20at%2015.55.39.png?alt=media&amp;token=a504ee59-6ebe-49db-aa00-fc66534b25b3" 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/text-compare/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.