> For the complete documentation index, see [llms.txt](https://sp.jerrygems.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sp.jerrygems.tech/volume-i-sound-speech-and-the-written-word/04-the-diacritical-accent-master-table.md).

# 4. The Diacritical Accent Master Table

> *How to distinguish twin words like 'el' vs. 'él', 'tu' vs. 'tú', and question words.*

***

## Twinning Words (Tilde Diacrítica)

When two words sound identical, Spanish uses a written accent mark to tell you what part of speech it is:

| Form WITHOUT Accent                    | Form WITH Accent                                  | How to Remember the Difference                                |
| -------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------- |
| **el** = the (*el libro*)              | **él** = he / him (*él lo sabe*)                  | The accent gives "él" legs to stand as a person (he)!         |
| **tu** = your (*tu coche*)             | **tú** = you (*tú eres inteligente*)              | The accent marks "tú" as the active human you are addressing! |
| **mi** = my (*mi amigo*)               | **mí** = me (*es para mí*)                        | After prepositions (para mí, a mí), give "mí" an accent.      |
| **si** = if (*si puedes...*)           | **sí** = yes / oneself (*dice que sí*)            | Saying YES gets a bold exclamation mark in your mind!         |
| **te** = you object (*te veo*)         | **té** = hot tea drink (*una taza de té*)         | Put an accent mark on the hot cup of tea!                     |
| **se** = pronoun (*se lava*)           | **sé** = "I know" or "Be!" (*yo sé todo*)         | From verbs *saber* or *ser* gets an accent.                   |
| **de** = of / from (*de Madrid*)       | **dé** = give subjunctive (*espero que me dé...*) | From the verb *dar* gets an accent.                           |
| **mas** = but (*quiso hablar, mas...*) | **más** = more (*quiero más dinero*)              | MORE quantity needs MORE ink (the tilde)!                     |
| **aun** = even / including (*aun así*) | **aún** = still / yet (*aún no llega*)            | If you can replace it with "todavía", put an accent on aún!   |

### The Question Words Rule

Whenever *qué, quién, cómo, dónde, cuándo, cuál, cuánto* are used in questions or exclamations (direct OR indirect), they **ALWAYS take an accent**:

* *«¿**Dónde** estás?»* (Where are you?)
* *«No sé **dónde** vives.»* (I don't know where you live — indirect question!).
* Compare with: *«La casa **donde** nací»* (The house where I was born — relative pronoun, no accent!).


---

# 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://sp.jerrygems.tech/volume-i-sound-speech-and-the-written-word/04-the-diacritical-accent-master-table.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.
