> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/screens/screen-layout-setup/layout-text-format.md).

# Layout Text Format

**Format**

**Description**

Enter the key description that will be displayed on the command key. You must have a description to display the key.

**Font**

Enable the font pattern you want to use for this command key. To know about the fonts available, please refer to the POS screen designer available from the Posera web site.

**Wrap text**

Enable this to use the two lines available for the key. Use a space character to separate the first to the second line description.

{% hint style="info" %}
NOTE :A maximum of 20 characters can be displayed on a command key.
{% endhint %}

**Alignment**

**Bottom align**

Enable this to display the key description from the bottom side of the key.

{% hint style="info" %}
NOTE: If disabled, center alignment is used.
{% endhint %}

**Left align**

Enable this to display the key description from the left side of the key.

{% hint style="info" %}
NOTE: If disabled, center alignment is used.
{% endhint %}

**Top align**

Enable this to display the key description from the topside of the key.

{% hint style="info" %}
NOTE: If disabled, center alignment is used.
{% 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.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/screens/screen-layout-setup/layout-text-format.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.