docs: fixed typo (#271)

cies · web-flow · commit 49930255c855 · 2023-04-10T06:18:54.000+01:00
diff --git a/docs/0.4.x/en-US/capsules/intro.md b/docs/0.4.x/en-US/capsules/intro.md
@@ -2,7 +2,7 @@
 
 Capsules are one of the most powerful features of Perseus, and, if you learn to use them, you can build some phenomenal apps extremely efficiently, taking maximum advantage of Perseus' advanced state platform.
 
-Remember how **template + page = state**? Well, similarly **capsule + state = widget**. *Widgets* are very similar to other pages, except they don't have `<head>`s, and they don't take up the whole page. Rather, they're embedded by other pages as, well, widgets. As widgets are to pages, capsules are to templates: a single capsule can generate many widgets, and has full access to the Perseus state platform.
+Remember how **template + state = page**? Well, similarly **capsule + state = widget**. *Widgets* are very similar to other pages, except they don't have `<head>`s, and they don't take up the whole page. Rather, they're embedded by other pages as, well, widgets. As widgets are to pages, capsules are to templates: a single capsule can generate many widgets, and has full access to the Perseus state platform.
 
 The reason capsules are useful is because they can be cached very aggressively: when Perseus loads a new page, it won't re-request capsules it already has, meaning apps that make heavy use of capsules can cut the amount of data transmitted over the network substantially! 
 
