From 2d3a46db37137bcbbf679d16e944c682f805ba97 Mon Sep 17 00:00:00 2001
From: Elias Rad <146735585+nnsW3@users.noreply.github.com>
Date: Wed, 25 Sep 2024 14:02:58 +0300
Subject: [PATCH] Update CONTRIBUTING.md

---
 CONTRIBUTING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a29c31a0b94..e23efaf847d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -27,7 +27,7 @@ Then you can replace the string with a intl component. The `id` prop will be the
 +  <FormattedMessage id="home.learn" />
 </label>
 ```
-In some cases, jsx maybe not acceptable, you can use `intl.formatMessage` .
+In some cases, jsx maybe not be acceptable, you can use `intl.formatMessage` .
 ```jsx
 <input
    ref={searchInputRef}
@@ -92,7 +92,7 @@ But in some cases, the `id` prop may not be static. For example,
  <FormattedMessage id={plugin?.profile.name + '.displayName'} defaultMessage={plugin?.profile.displayName || plugin?.profile.name} />
 </h6>
 ```
-You can't be sure there is a match key in locale file or not. So it will be better to provide a `defaultMessage` prop.
+You can't be sure whether there is a match key in locale file or not. So it will be better to provide a `defaultMessage` prop.
 
 ### Should I update the non-english locale json files?
 You probably will have this question when you are updating the english locale json files.