> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/getting-started/word-best-practices/structure-word-document.md).

# Structure a Word document

Create a stable, consistent and clean document by starting with structuring your document.

{% hint style="warning" %}
**Tip**

Create a stable, consistent and clean document by starting with structuring your document.
{% endhint %}

## Show hidden formatting

* Display spaces, line breaks, page breaks and section breaks by clicking the ¶ "Show/Hide formatting marks" symbol on the "Home" tab

## Design the appearance of the document

* From the "Insert" tab, choose the orientation of the document or section
* From the "Design" tab, choose the page background color, page borders and watermarks

## Define margins

* From the "Layout" tab, choose the margin format: default or custom

{% hint style="warning" %}
**Tip**

Adjust spacing manually using the horizontal and vertical rulers. Go to the View tab and check the "Ruler" box if they are not visible
{% endhint %}


---

# 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://university.gonexa.fr/doc/en/getting-started/word-best-practices/structure-word-document.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.