> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/styling/references-styling.md).

# References styling

{% embed url="<https://vimeo.com/459389030>" %}

## Wording for cross-references

<figure><img src="https://1353649376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaTEDNbiFdDa6DW2eNG17%2Fuploads%2Fj1aZNUedSM3yxvAzLNfm%2Fimage.png?alt=media&amp;token=c713f3ef-691b-4ab5-b6a0-ac7e6f24e7f3" alt="" width="563"><figcaption></figcaption></figure>

* **word to use for a ‘clause’** — Allows you to choose which word Clause9 uses to refer to other clauses in [cross-references](/clauses/cross-references.md).
* **referring to another document in a binder** — Allows you to configure how Clause9 refers to another subdocument in a binder.&#x20;
* **print clause title (between parentheses)** — Allows you to choose whether the clause title of the clause you are referring to should be shown (in parentheses) in a cross-reference.

## Placeholders

<figure><img src="https://1353649376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaTEDNbiFdDa6DW2eNG17%2Fuploads%2F0x1poZxkfWQGxga7aHTj%2Fimage.png?alt=media&amp;token=c3a3f93c-beb4-4fd8-8f85-5b1475290a3e" alt="" width="315"><figcaption></figcaption></figure>

Clause9 allows you to create a placeholder in your text, the formatting of which can be tailored as well. This is done by typing `@placeholder("content")`, replacing `content` by the actual text you want the placeholder to contain.

* **placeholder content** — Here you can choose whether the placeholder should just show the text of the content or whether the content should be shown between square brackets, with a ‘blob’, etc.
* **background color** — Allows you to choose the background color of the placeholder.


---

# 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.clause9.com/styling/references-styling.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.