> For the complete documentation index, see [llms.txt](https://datalab-docs.datacamp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://datalab-docs.datacamp.com/work/text-cell.md). # Text cell Use the text cell to add text to your notebook. The text cell uses Markdown syntax, which means that you can use certain formatting queues like `**` and `_` to make text bold, italics, or to add headings and lists to your text. See [here](https://www.datacamp.com/cheat-sheet/markdown-cheat-sheet-23) for a DataCamp cheat sheet with basic syntax. The text cell can be in two modes: editing mode or viewing mode. ### Editing mode Use this mode write your markdown cell. A toolbar appears that you can use to easily format text, as well as add hyperlinks and images. You can also just paste an image from your local filesystem or your clipboard into a text cell; the image will be uploaded to your workbook and included with the correct Markdown syntax.

### Viewing mode This is the 'rendered' version of your markdown code: headings show up as larger titles, text formatted as bold will actually be bold, and links and images will be displayed. People with viewing access to your workbook will always see your text cells in viewing mode (since they can not edit them).

### Switching modes To switch from viewing mode to editing mode, you can do one of the following: * Double click on the text cell * Click "Edit" in the cell menu * Hit `Enter` when the cell is active. To switch from editing mode to viewing mode, you can do one of the following: * Click "View" in the cell menu * Hit `Ctrl` + `Enter` when the cell is active. ### --- # 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://datalab-docs.datacamp.com/work/text-cell.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.