> 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-ii-the-substantive-world-nouns-articles-and-adjectives/09-the-stressed-a-elision-rule.md).

# 9. The Tonic Stressed A- Elision Rule

> *Why you say 'el agua fría' instead of 'la agua fría', and when the rule switches back.*

***

## The Euphony Trick (Sound Harmony)

In English, you say *"an apple"* because *"a apple"* feels awkward to pronounce. Spanish does the same thing:\
When a **feminine singular noun starts with a STRESSED 'a-' or 'ha-' sound**, Spanish replaces *la* with *el* purely to prevent a vocal traffic jam:

> 🇪🇸 **El agua fría** calma la sed.\
> 🇬🇧 *"Cold water calms thirst."*

Notice: The article is **el**, but the noun is still 100% feminine! That is why the adjective is **fría** (feminine), NOT *frío*!

### Other Key Examples

* *el águila real* (the royal eagle) — adjective is feminine (*real*).
* *el hacha afilada* (the sharp axe) — adjective is feminine (*afilada*).
* *el hambre canina* (the ravenous hunger).
* *el alma pura* (the pure soul).

### When Does It Switch Back to "LA"?

1. **In the Plural:** Plurals have an 's' that breaks the vowel collision, so they return to *las*: *las aguas, las águilas, las hachas*.
2. **If an adjective sits in between:** *la hermosa águila* (the beautiful eagle), *la fría agua*.
3. **If the initial 'a' is unstressed:** *la aguja* (needle), *la arena* (sand), *la amistad* (friendship).


---

# 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-ii-the-substantive-world-nouns-articles-and-adjectives/09-the-stressed-a-elision-rule.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.
