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()`.