> 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/custom-styling/body-text-pane.md).

# Body text pane

In this pane, you can define which MS Word styles should be assigned to body paragraphs (whether bulleted or not). 

This pane contains three different sub-panes (*Below headings*, *Outside any heading* and *In table)* that all work identically. 

* The *Below headings* sub-pane covers the general styles that will be used for body paragraphs, if no special setting applies. Such special setting would apply when a body paragraph is situated below a heading level that has its own deviating body styles (as indicated in the Headings pane), or when the body paragraph would be situated outside any heading, or in a table. 
* The *Outside any heading* sub-pane covers body paragraphs that are not situated below any heading or title, i.e. body paragraphs that are situated at the top level (or below some other body level that is not situated below some heading or title).
* The *In table* sub-pane covers body paragraphs situated within a table.

For each of the levels, you can optionally specify that bulleted paragraphs should be assigned a different MS Word style, by clicking on "..." at the right side and choosing "Bullet-style name".  If no such different style is chosen, then both bulleted and non-bulleted body paragraphs will be assigned the same MS Word style.

<figure><img src="/files/kAu5D68M0RZhUBFsaGQk" alt=""><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/quality-library/how/in-depth/custom-styling/body-text-pane.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.