From 499547aea3267fe958b8083c4fa4be691ac80d83 Mon Sep 17 00:00:00 2001 From: 0xdeadd Date: Fri, 8 May 2026 13:21:47 -0400 Subject: [PATCH] docs: fix typo 'includin' -> 'including' in who-owns-the-tree blog post Closes #900 --- src/blog/who-owns-the-tree.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/blog/who-owns-the-tree.md b/src/blog/who-owns-the-tree.md index e3ece626d..d222fdb35 100644 --- a/src/blog/who-owns-the-tree.md +++ b/src/blog/who-owns-the-tree.md @@ -25,7 +25,7 @@ RSC is also a _protocol_, a way to serialize rendered React output, client refs, **So, who owns the tree?** -If and when the server owns it, you need a way to drop client interactivity _into_ it, which is exactly what `'use client'` is for. Hopefully this doesn't come as a surprise. It's in the react docs and how pretty much every RSC framework model works to this day, includin Start. +If and when the server owns it, you need a way to drop client interactivity _into_ it, which is exactly what `'use client'` is for. Hopefully this doesn't come as a surprise. It's in the react docs and how pretty much every RSC framework model works to this day, including Start. However, if the _client_ owns it, you'll need a way to drop _server-rendered UI into it_. That's what Composite Components solve in TanStack Start.