> 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/smart-templates/faq/why-does-the-interactive-preview-sometimes-fail-to-show-numbering-correctly.md).

# Why does the interactive preview sometimes fail to show numbering correctly?

If you use conditional logic in your Smart Template to drop a clause in or out of a document, you may have noticed that the interactive preview doesn't automatically adjust the numbering to account for this clause being dropped. Here's an example. 

<figure><img src="https://3419152551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYGsvJviMTNnfjOWV7Kpb%2Fuploads%2FBg0fzhCvY3vAZA9x752c%2Fimage.png?alt=media&amp;token=1c012e01-101f-4c88-8025-338fc4439a48" alt="" width="375"><figcaption><p>Paragraph 3 should receive number 2. Instead, it makes the jump from 1 to 3. </p></figcaption></figure>

If you use Microsoft Word's automatic numbering feature, the issue is cosmetic rather than functional. Currently, there is a known issue with Microsoft Word that affects how numbering is displayed in the interactive preview.

Our team has been in communication with Microsoft support to resolve this matter.

It is important to note that when the document is exported to either Docx or PDF format, the numbering should be displayed as intended.&#x20;

<figure><img src="https://3419152551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYGsvJviMTNnfjOWV7Kpb%2Fuploads%2Fb2jVpzVSAmc3uSMXVGhD%2Fimage.png?alt=media&amp;token=43fc3e76-edd0-4f98-a30a-af515442c65f" alt="" width="375"><figcaption><p>This is the same document as shown above after being exported. </p></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/smart-templates/faq/why-does-the-interactive-preview-sometimes-fail-to-show-numbering-correctly.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.