> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form/form-subcomponent-display-text.md).
# Form Subcomponent: Display Text
The Display Text subcomponent can only be used within the [Form component.](/components/component-library/modular-checkout-components/component-checkout-form.md) The Display Text component allows you to include header, and text within the Form. It is a rich text field which supports links, lists, and text styling.
The text input supports the the use of **{{totalCost}}** and **{{termEndDate}}** [Variables for Limio Components](/components/component-library/list-of-variables-that-can-be-used-in-limio-components.md)
### Props
| Prop Name | Label | Type | Default Value | Description |
| -------------- | ----------- | ------ | ----------------------------------------------------------------- | -------------------------------------------------- |
| text | Text | string | You will be charged {{totalCost}} per month until {{termEndDate}} | This is the copy which will appear on the page |
| col | Column Size | number | 12 | Size of the columns |
| fieldClassName | Class Name | string | "" | The CSS class name for styling the field component |
---
# 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.limio.com/components/component-library/modular-checkout-components/modular-checkout-subcomponents-in-form/form-subcomponent-display-text.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.
%20(1).png?alt=media)