From a9f8e0279b7c2366c01da6c25eb0c7d8875bbe57 Mon Sep 17 00:00:00 2001
From: prateekbytes <113372195+prateekbytes@users.noreply.github.com>
Date: Tue, 13 Sep 2022 00:23:04 +0530
Subject: [PATCH] Typo error in CONTRIBUTING.md fixed (#111401)

I found a typo error in CONTRIBUTING.md and fixed it.
---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ca6d34e75f..cf1c28ed39 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -159,7 +159,7 @@ To contribute API documentation, an excellent command of the English language is
 We have a [whole section in our style guide](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#documentation-dartdocs-javadocs-etc)
 that you should read before you write API documentation. It includes notes on the "Flutter Voice", such as our word and grammar conventions.
 
-In general, a really productive way to improve documentation is to use Flutter and stop any time your have a question: find the answer, then
+In general, a really productive way to improve documentation is to use Flutter and stop any time you have a question: find the answer, then
 document the answer where you first looked for it.
 
 We also keep [a list of areas that need better API documentation](https://github.com/flutter/flutter/issues?q=is%3Aopen+is%3Aissue+label%3A%22d%3A+api+docs%22+sort%3Areactions-%2B1-desc).