Skip to content

docs: fix typo 'includin' -> 'including' in who-owns-the-tree blog post#901

Merged
LadyBluenotes merged 2 commits intoTanStack:mainfrom
0xdeadd:fix/typo-includin-start
May 8, 2026
Merged

docs: fix typo 'includin' -> 'including' in who-owns-the-tree blog post#901
LadyBluenotes merged 2 commits intoTanStack:mainfrom
0xdeadd:fix/typo-includin-start

Conversation

@0xdeadd
Copy link
Copy Markdown
Contributor

@0xdeadd 0xdeadd commented May 8, 2026

Summary

Fixes a typo in src/blog/who-owns-the-tree.md (line 28): "includin Start" → "including Start".

Closes #900.

Test plan

  • Single-character typo fix in markdown content; no build/runtime impact.

Summary by CodeRabbit

  • Documentation
    • Corrected a spelling error in the blog post section addressing tree ownership.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 8, 2026

Deploy Preview for tanstack ready!

Name Link
🔨 Latest commit 37f2a65
🔍 Latest deploy log https://app.netlify.com/projects/tanstack/deploys/69fe3d8c75268a000871b109
😎 Deploy Preview https://deploy-preview-901--tanstack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 44 (🔴 down 3 from production)
Accessibility: 90 (no change from production)
Best Practices: 83 (🔴 down 9 from production)
SEO: 97 (no change from production)
PWA: 70 (no change from production)
View the detailed breakdown and full score reports
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 8, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

This PR fixes a single typo in the blog post src/blog/who-owns-the-tree.md at line 28, correcting "includin Start" to "including Start" in the server-owned paragraph. No structural or logical changes are present.

Changes

Blog Content Fix

Layer / File(s) Summary
Content Correction
src/blog/who-owns-the-tree.md
Line 28 corrects the spelling error "includin Start" to "including Start" in the server-owned paragraph.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

A typo slipped in where words did flow,
A missing "g" that made things slow,
But now "includin" shines so bright—
A single "g" makes it right! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: fixing a typo in the blog post file, making it clear and specific.
Linked Issues check ✅ Passed The PR directly addresses issue #900 by correcting the typo 'includin' to 'including' in the specified file and line.
Out of Scope Changes check ✅ Passed All changes are scoped to fixing the reported typo; no out-of-scope modifications are present in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/blog/who-owns-the-tree.md`:
- Line 28: Update the documentation sentence that currently reads "react docs"
to "React docs" to use proper noun capitalization; locate the sentence
containing "'use client'" (the line starting "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.") and change only the lowercase "react" to "React".
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8dc8c7c6-b7b5-4b18-a379-69cf25680e67

📥 Commits

Reviewing files that changed from the base of the PR and between 1139c83 and 499547a.

📒 Files selected for processing (1)
  • src/blog/who-owns-the-tree.md

**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.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Capitalize “React” in docs reference.

Line 28 still has a small typo-quality issue: use “React docs” instead of “react docs” for proper noun capitalization.

🧰 Tools
🪛 LanguageTool

[style] ~28-~28: Consider an alternative for the overused word “exactly”.
Context: ...lient interactivity into it, which is exactly what 'use client' is for. Hopefully t...

(EXACTLY_PRECISELY)


[uncategorized] ~28-~28: “React” is a proper noun and needs to be capitalized.
Context: ...doesn't come as a surprise. It's in the react docs and how pretty much every RSC fram...

(A_GOOGLE)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/blog/who-owns-the-tree.md` at line 28, Update the documentation sentence
that currently reads "react docs" to "React docs" to use proper noun
capitalization; locate the sentence containing "'use client'" (the line starting
"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.") and change only the
lowercase "react" to "React".

@LadyBluenotes LadyBluenotes merged commit 1cc3b6c into TanStack:main May 8, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Typo in who-owns-the-tree blog post

2 participants