From c52bb12d0bd19e3f200249e06a17430e718a9d54 Mon Sep 17 00:00:00 2001 From: Mike Munroe Date: Sat, 7 Oct 2023 07:16:52 -0400 Subject: [PATCH] Remove extra word "to" --- pages/html/components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/html/components.md b/pages/html/components.md index 03df147..5fb24a6 100644 --- a/pages/html/components.md +++ b/pages/html/components.md @@ -50,7 +50,7 @@ This would work just fine for a list of views as each method can be called multi One caveat of defining the view this way is `title` and `body` could be called in any order. This offers flexibility, but what if you need to make sure your markup is output in a consistent order? -First, include `Phlex::DeferredRender` in your view. This changes the behavior of `template` so it does not receive a block and is yielded early. Then use public methods to save blocks, passing them to back to the `template` at render time. +First, include `Phlex::DeferredRender` in your view. This changes the behavior of `template` so it does not receive a block and is yielded early. Then use public methods to save blocks, passing them back to the `template` at render time. ```phlex example do |e|