# Cycle 41

## Video Modeling Sounds and Words: 41.1 — 41.4

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

## 41.1 New Sound

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

#### Purpose and Procedure

In this task, students will learn the sound /sh/ as in *shy*.

#### Important Reminders

Even though this sound is made of two characters that usually represent two sounds, we want students to recognize it as a single unit, which is why the characters are visibly connected.

As with the other digraph that you’ve taught (*th*), your finger should stay over the dot beneath the sound the whole time that you say the sound, rather than moving from beneath the *s* to beneath the *h*.

{% embed url="<https://youtu.be/NFaP-qpQjGk>" %}

## 41.3 The Slow-Fast Game

#### Purpose and Procedure

This is the first task that uses the /ŋ/ sound before a *k* (in the word *Frank*).

When *n* comes before *k*, we pronounce /ŋ/ and then /k/. This is different from when *n* comes before *g*. In that case, we only pronounce /ŋ/ with no /g/ afterward. (Exceptions can occur when more sounds follow the *g*, like in the word *finger*.)

#### Important Reminders

Remember, to make the /ŋ/ sound, prepare to make the sound /g/, but instead of popping the tongue down, hold it in place, and make a voiced, continuous sound.

## 41.4 Word Reading

#### Purpose and Procedure

The final part of this task returns to reading words with no symbols beneath the sounds, but this time students don’t say the word simultaneously with you before they attempt it on their own.

Ensure that the students touch beneath each sound as they say the sounds, exactly as they would if there were dots beneath each sound.


---

# 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-41.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.
