> 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-v-non-finite-forms-and-verbal-periphrases/34-the-gerund-and-the-posteriority-crime.md).

# 34. The Gerund (-ando/-iendo) & The Posteriority Crime

> *Understanding the progressive aspect and avoiding the severe error of the gerund of posteriority.*

***

## The Spanish Gerund: Simultaneous Actions Only

The Spanish gerund (*hablando, comiendo, viviendo*) corresponds to the English progressive *-ing*. It has **only one legitimate job**: expressing an action that is **happening at the exact same moment** as the main verb:

> 🇪🇸 **Salió del despacho cantando una canción.**\
> 🇬🇧 *"He left the office singing a song." (Simultaneous!)*

### The Crime: The Gerund of Posteriority

In English journalism, people say: *"The car crashed into the pole, killing two passengers hours later."*\
In Spanish, the Royal Spanish Academy **strictly forbids this syntax**. The gerund CANNOT express an event that occurs subsequent to or later than the main verb:

* ❌ **Illegal:** \*«*El delincuente escapó por la azotea, siendo capturado tres horas después».*
* ✅ **Correct:** *«El delincuente escapó por la azotea y **fue capturado** tres horas después.»*


---

# 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-v-non-finite-forms-and-verbal-periphrases/34-the-gerund-and-the-posteriority-crime.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.
