# Cycle 21

## Video Modeling Sounds and Words: 21.1 — 21.5

{% embed url="<https://youtu.be/5z_s-n60svI>" %}

## 21.1 New Sound

{% embed url="<https://youtu.be/QyQzgevxPsQ>" %}

#### Purpose and Procedure

In this task, students will learn the sound /th/ as in *father*. This sound should be voiced. Do not say the unvoiced /th/ as in *think*.

This is the first digraph (one sound written with two letters) taught in this curriculum, but do not talk about individual letters when introducing this sound. We want students to recognize it as a single unit, which is why the characters are visibly connected. Now is not the time to talk about *t* or *h* or even to say the word *letter.*&#x20;

Your finger should stay over the dot beneath the sound the whole time that you say the sound, rather than moving from beneath the *t* to beneath the *h*.

{% embed url="<https://youtu.be/4qdGQoTDkjg>" %}

## 21.5 Word Reading

#### Purpose and Procedure

This task introduces the fact that *the* can be pronounced in two acceptable ways: /thē/ and /thǝ/.

‍*Fist* and *raft* are the first words that students will read with four distinct sounds. They also have the first consonant blends that students will read. You may need to model the sounds more times than you usually do and let the student have more tries than they usually need.

## 21.7 Writing

#### Purpose and Procedure

This task introduces students to writing their first digraph (one sound written with two letters).

Even though the *t* and the *h* are tied together in this specialized font, you should write them as separate characters, just as the red lines indicate.


---

# Agent Instructions: 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:

```
GET https://curriculum.tryonce.com/cycle-21.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
