> 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/05-punctuation-and-inverted-marks.md).

# 5. Punctuation Quirks & Inverted Marks

> *Why upside-down ¿ and ¡ exist, dialogue dashes, and Spanish comma customs.*

***

## The Upside-Down Punctuation Secret

In English, you can read an entire long sentence and only realize at the last word that your pitch should have gone up because you finally see the question mark.

Spanish fixes this problem with **inverted marks: ¿ and ¡**:

* *«¿Vas a venir mañana a la fiesta?»* (Are you coming to the party tomorrow?)
* *«¡Qué sorpresa verte aquí!»* (What a surprise to see you here!)

### The Em-Dash (—) for Dialogue

In English novels, speech uses quotation marks: *"Hello," he said.*\
In Spanish literature and journalism, dialogue uses long em-dashes:

* *—Hola, ¿cómo estás? —preguntó Carlos.*\
  *—Muy bien, gracias —respondió ella.*

***

### Daily Life Multi-Level Practice

* 🟢 **Level 1:** *«¿Dónde está la estación de metro más cercana?»* (Where is the nearest subway station?)
* 🟡 **Level 2:** *«¡No me digas que perdiste los boletos de avión otra vez!»* (Don't tell me you lost the flight tickets again!)
* 🔴 **Level 3:** *«—El veredicto final —murmuró el magistrado con semblante severo— resulta inapelable.»* ("The final verdict," the magistrate murmured with a severe countenance, "is non-appealable.")


---

# 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/05-punctuation-and-inverted-marks.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.
