From 4e85f00d4933336cbd79b907ab04237fc1948453 Mon Sep 17 00:00:00 2001
From: Hammad Zafar <75698921+hammadzafar05@users.noreply.github.com>
Date: Wed, 1 Jan 2025 12:11:05 +0500
Subject: [PATCH] Fixed Docs: Updated the URL

---
 packages/forms/docs/03-fields/15-textarea.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/forms/docs/03-fields/15-textarea.md b/packages/forms/docs/03-fields/15-textarea.md
index c0306a05d6..449b008d88 100644
--- a/packages/forms/docs/03-fields/15-textarea.md
+++ b/packages/forms/docs/03-fields/15-textarea.md
@@ -51,7 +51,7 @@ Textarea::make('description')
 
 There are a few differences, compared to [`disabled()`](getting-started#disabling-a-field):
 
-- When using `readOnly()`, the field will still be sent to the server when the form is submitted. It can be mutated with the browser console, or via JavaScript. You can use [`dehydrated(false)`](advanced#preventing-a-field-from-being-dehydrated) to prevent this.
+- When using `readOnly()`, the field will still be sent to the server when the form is submitted. It can be mutated with the browser console, or via JavaScript. You can use [`dehydrated(false)`](../advanced#preventing-a-field-from-being-dehydrated) to prevent this.
 - There are no styling changes, such as less opacity, when using `readOnly()`.
 - The field is still focusable when using `readOnly()`.