deploy: b257377

handbook/streams.html

@@ -177,7 +177,7 @@ <h2 id="progressively-enhance-when-necessary"><a class="anchor" href="#progressi
 <p>The same is especially true for WebSocket updates. On poor connections, or if there are server issues, your WebSocket may well get disconnected. If the application is designed to work without it, it’ll be more resilient.</p>
 <h2 id="but-what-about-running-javascript%3F"><a class="anchor" href="#but-what-about-running-javascript%3F">﹟</a> But What About Running JavaScript?</h2>
 <p>Turbo Streams consciously restricts you to seven actions: append, prepend, (insert) before, (insert) after, replace, update, and remove. If you want to trigger additional behavior when these actions are carried out, you should attach behavior using <a href="https://stimulus.hotwired.dev">Stimulus</a> controllers. This restriction allows Turbo Streams to focus on the essential task of delivering HTML over the wire, leaving additional logic to live in dedicated JavaScript files.</p>
-<p>Embracing these constraints will keep you from turning individual responses in a jumble of behaviors that cannot be reused and which make the app hard to follow. The key benefit from Turbo Streams is the ability to reuse templates for initial rendering of a page through all subsequent updates.</p>
+<p>Embracing these constraints will keep you from turning individual responses into a jumble of behaviors that cannot be reused and which make the app hard to follow. The key benefit from Turbo Streams is the ability to reuse templates for initial rendering of a page through all subsequent updates.</p>
 <h2 id="custom-actions"><a class="anchor" href="#custom-actions">﹟</a> Custom Actions</h2>
 <p>By default, Turbo Streams support <a href="/reference/streams#the-seven-actions">seven values for its <code>action</code> attribute</a>. If your application needs to support other behaviors, you can override the <code>event.detail.render</code> function.</p>
 <p>For example, if you’d like to expand upon the seven actions to support <code>&lt;turbo-stream&gt;</code> elements with <code>[action=&quot;alert&quot;]</code> or <code>[action=&quot;log&quot;]</code>, you could declare a <code>turbo:before-stream-render</code> listener to provide custom behavior:</p>