From 83022b7b37dedf7d4152d39ed362eee957995635 Mon Sep 17 00:00:00 2001
From: Ryan Christian <33403762+rschristian@users.noreply.github.com>
Date: Tue, 27 Feb 2024 19:25:16 -0600
Subject: [PATCH] docs: Reverse recommendation for controlled inputs

---
 content/en/guide/v10/forms.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/guide/v10/forms.md b/content/en/guide/v10/forms.md
index e15cf9f4b..eac1ae49d 100755
--- a/content/en/guide/v10/forms.md
+++ b/content/en/guide/v10/forms.md
@@ -29,7 +29,7 @@ A framework like Preact in contrast generally has a unidirectional data flow. Th
 <input value={someValue} onInput={myEventHandler} />;
 ```
 
-Generally, you should try to use _Controlled_ Components at all times.  However, when building standalone Components or wrapping third-party UI libraries, it can still be useful to simply use your component as a mount point for non-preact functionality. In these cases, "Uncontrolled" Components are nicely suited to the task.
+Generally, you should try to use _Uncontrolled_ Components whenever possible. The DOM is fully capable of handling `<input>`'s state. However, there are situations in which you may need to have tighter control over the input value, in which case, "Controlled" Components can be used.
 
 > One gotcha to note here is that setting the value to `undefined` or `null` will essentially become uncontrolled.