> For the complete documentation index, see [llms.txt](https://docs.ur.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ur.app/design/user-experience/copy-guidelines.md).

# Copy guidelines

Use account-first language everywhere your users read about UR. The tables below show the wording to use and the wording to avoid.

### Account opening and setup

| Use this              | Not this           |
| --------------------- | ------------------ |
| "Open your account"   | "Apply for a card" |
| "Get started with UR" | "Card application" |

### Feature descriptions

| Use this                                    | Not this           |
| ------------------------------------------- | ------------------ |
| "Manage your balance"                       | "Top up your card" |
| "Deposit funds to your account"             | "Card balance"     |
| "Send money to any external account"        | "Load your card"   |
| "Convert crypto directly into your account" |                    |
| "Spend your balance with a debit card"      |                    |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ur.app/design/user-experience/copy-guidelines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.