> 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/definitions/how/in-depth.md).

# In depth

{% embed url="<https://www.youtube.com/watch?v=s9SOY7Yz5f4>" %}

The *Definitions* feature presents a clean overview of all the definitions and capitalised terms in your document. This can help you to:

* Immediately jump to the relevant definition of a certain term, which can speed up the drafting process in a long document.
* Check whether there are definitions that are not actually used within the document (aka *"ghost definitions"*).
* Check whether there are capitalised terms that are missing a definition.

## **Definition List**

<figure><img src="https://files.helpdocs.io/f86qgdbm02/articles/gv02og4pah/1701636586909/image.png" alt="" width="375"><figcaption></figcaption></figure>

This list shows all the definitions that are found within any of the definition lists of the document (whether in a bulleted list, or numbered list, or table cells).

When a definition is not actually used outside within the document, an exclamation mark is shown (as is the case with the *Source Code* in the screenshot above).

You can click on a row in the table to immediately jump to the definition.

## **Inline definitions**

"Inline" definitions are terms that are defined within the paragraph in which that term is first used, instead of being defined in a dedicated definitions list. Such inline definitions are sometimes also called *interpretative* clauses or *definitional* clauses.

Some examples are given in the screenshot below:

<figure><img src="https://files.helpdocs.io/f86qgdbm02/articles/gv02og4pah/1701636887282/image.png" alt="" width="375"><figcaption></figcaption></figure>

Similar to the *Definition List*, you can click on a row to immediately jump to the paragraph in which the inline definition is found.

Also similar to the *Definition List,* when an inline definition is not actually used outside within the document, an exclamation mark is shown.

## **Capitalised Terms**

The *Capitalised Terms* panel provides an overview of all the capitalised words (or word groups) that were used at least twice in the document.

When you click on a certain term, you get an exhaustive overview of all the paragraphs in which that term is used. Yu can click one of those paragraphs to immediately jump to the relevant location in your MS Word document.

If a definition is missing for a capitalised term, then this term will be flagged with a warning symbol.

<figure><img src="https://files.helpdocs.io/f86qgdbm02/articles/gv02og4pah/1701636989966/image.png" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
While mistakes may also happen in the Definition List and Inline Definitions, the likelihood of errors is significantly higher with the Capitalised Terms panel. To ensure that your document is analysed in seconds (instead of minutes), ClauseBuddy uses a special type of fast artificial intelligence (AI). This AI will make mistakes, e.g. flagging names of persons/cities as well as common words that humans would not qualify as defined terms.
{% endhint %}

## **Refreshing contents**

When you insert or remove paragraphs, the "jump to paragraph" feature may get confused, jumping to a paragraph above or below the original paragraph.

When this happen, you must press the *Refresh* button in the top right corner, to instruct ClauseBuddy to re-analyse your document.

<figure><img src="/files/0LUKcGOd2dsmLYJNJAqd" alt="" width="375"><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 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/definitions/how/in-depth.md?ask=<question>&goal=<endgoal>
```

`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.