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

# Tables

Currently table formatting controls the layout of the [grid](/adding-questions-and-content/question-reference/grid-choice.md) questions. 

### Spacing

Using the **Row gap** and **Column gap** in the **Table** menu, you can control the spacing around cells. You can also change the padding within the cell using the **Cell** menu. 

### Styling first row or column differently than the rest of the table

In order to make the grid more legible, you might want to style the first row and the first column differently. This will allow you to emphasize the question and answer labels. 

{% hint style="info" %}
You can style the radio buttons using the [**Checkmarks** ](/styling/customizing-appearance/checkmarks.md)menu.
{% 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://docs.formsort.com/styling/customizing-appearance/tables.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.