> 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/quality-library/how/in-depth/searching-clauses/inspecting-clauses.md).
# Inspecting clauses
Once you've found a good clause, you can inspect its legal metadata and compare it to other clauses inside your document. You can do so by hitting the **...** button in the top right corner of the clause.
This popup menu will show you the following:
* The **internal number** of the clause (e.g., #1272443). This number may come across as very nerdy, but it's sometimes very handy when communicating with colleagues — e.g., when a senior partner would email a junior associate telling to *"use clause #8875124"*. The junior can then simply paste these numbers in the keyword search bar, and will immediately find that particular clause.
* The date & time when this clause was **last changed** by someone.
* Any legal **comment** (typically case law or doctrine references) assigned to the clause.
Note that the clause's legal description will be shown *above* the clause.
## Comparing clauses
You can compare the content of a selected clause with whatever text you happen to have currently selected inside the MS Word document. You can do so by clicking on the *Compare* button.
Don't forget to click on this button again to show its normal contents!
## Editing clauses
If you want to edit the contents of a clause (and are authorised to do so), click on the *Edit clause* button.The clause will then be opened in the clause editor.
If the clause was created in Clause9 (and is therefore too complex to edit inside MS Word), you will be invited to edit the clause inside Clause9, i.e. in your browser (if you have the required access rights).
---
# 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/quality-library/how/in-depth/searching-clauses/inspecting-clauses.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.
