From 5587c9b110728fb67bf3f50b3e84466d29091a89 Mon Sep 17 00:00:00 2001
From: Denny Hong <60201810+dennyhong96@users.noreply.github.com>
Date: Tue, 5 Oct 2021 12:04:11 -0700
Subject: [PATCH] docs: fix wording in "Testing Form" section.

---
 docs/guide/essentials/forms.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/guide/essentials/forms.md b/docs/guide/essentials/forms.md
index 791e3888c..16048296b 100644
--- a/docs/guide/essentials/forms.md
+++ b/docs/guide/essentials/forms.md
@@ -358,7 +358,7 @@ test('fills in the form', async () => {
 
 What happens if your Input component is not that simple? You might be using a UI library, like Vuetify. If you rely on digging inside the markup to find the right element, your tests may break if the external library decides to change their internals.
 
-In such cases you can use set the value directly, using the component instance and `setValue`.
+In such cases you can set the value directly, using the component instance and `setValue`.
 
 Assume we have a form that uses the Vuetify textarea: