diff --git a/_source/reference/events.md b/_source/reference/events.md index 369da5c..5ff0c53 100644 --- a/_source/reference/events.md +++ b/_source/reference/events.md @@ -34,7 +34,7 @@ Turbo emits events that allow you to track the navigation lifecycle and respond * `turbo:load` fires once after the initial page load, and again after every Turbo visit. Access visit timing metrics with the `event.detail.timing` object. -* `turbo:before-frame-render` fires before rendering the `` element. Access the new `` element with `event.detail.newFrame`. Rendering can be canceled and continued with `event.detail.resume` (see [Pausing Rendering](/handbook/frame#pausing-rendering)). Customize how Turbo Drive renders the response by overriding the `event.detail.render` function (see [Custom Rendering](/handbook/frames#custom-rendering)). +* `turbo:before-frame-render` fires before rendering the `` element. Access the new `` element with `event.detail.newFrame`. Rendering can be canceled and continued with `event.detail.resume` (see [Pausing Rendering](/handbook/frames#pausing-rendering)). Customize how Turbo Drive renders the response by overriding the `event.detail.render` function (see [Custom Rendering](/handbook/frames#custom-rendering)). * `turbo:frame-render` fires right after a `` element renders its view. The specific `` element is the event target. Access the `FetchResponse` object with `event.detail.fetchResponse` property.