From dc9f59b9be98cb4588fa2b32149747e0b76ca352 Mon Sep 17 00:00:00 2001
From: Roshith <107235573+roshith844@users.noreply.github.com>
Date: Mon, 12 Jan 2026 23:17:17 +0530
Subject: [PATCH] docs: fix spelling mistake in documentation

correct typo where "youself" was written instead of "yourself"

(cherry picked from commit 933ca9e5dce1b0439a8c923459f2f16d7b5a27c8)
---
 adev/src/content/guide/signals/overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/adev/src/content/guide/signals/overview.md b/adev/src/content/guide/signals/overview.md
index cffc0924859..7180209b0fb 100644
--- a/adev/src/content/guide/signals/overview.md
+++ b/adev/src/content/guide/signals/overview.md
@@ -188,7 +188,7 @@ effect(() => {
 
 ## Advanced derivations
 
-While `computed` handles simple readonly derivations, you might find youself needing a writable state that is dependant on other signals.
+While `computed` handles simple readonly derivations, you might find yourself needing a writable state that is dependant on other signals.
 For more information see the [Dependent state with linkedSignal](/guide/signals/linked-signal) guide.
 
 All signal APIs are synchronous— `signal`, `computed`, `input`, etc. However, applications often need to deal with data that is available asynchronously. A `Resource` gives you a way to incorporate async data into your application's signal-based code and still allow you to access its data synchronously. For more information see the [Async reactivity with resources](/guide/signals/resource) guide.