> 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/tables-and-table-headers-in-word.md). # Manage tables and table headers in Word To repeat table headers, select the table row or rows that make up the header you want to repeat ## Repeat table headers * To repeat table headers, select the table row or rows that make up the header you want to repeat * Right-click > Table Properties, then under Options, check "Repeat as header row at the top of each page". Click OK ## Show gridlines * Show gridlines to see the boundaries of tables that have no visible borders * Click your table, then click the "Table Layout" tab * Click "View Gridlines" to turn it on * Gridlines are visible in the areas of the table without borders {% hint style="warning" %} **Tip** Unlike borders, gridlines only appear on screen and are never printed {% 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/tables-and-table-headers-in-word.md?ask=&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.