summaryrefslogtreecommitdiff
path: root/doc/contribute.md
diff options
context:
space:
mode:
authorGrant <Volatile86@gmail.com>2021-07-25 10:58:55 -0500
committerGitHub <noreply@github.com>2021-07-25 17:58:55 +0200
commit6222b7c22307b114fef0ddd2148472dbebbc5174 (patch)
treecf40686fb514801073f6426db237c65ca6d6c4ee /doc/contribute.md
parent1ae22f45f97bf5135a23ab0dedd87d7fdaff82bd (diff)
Correct spelling issue in documentation (#509)
* Correct spelling issue
Diffstat (limited to 'doc/contribute.md')
-rw-r--r--doc/contribute.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/contribute.md b/doc/contribute.md
index 09d20774..9f4c2154 100644
--- a/doc/contribute.md
+++ b/doc/contribute.md
@@ -48,7 +48,7 @@ When reviewing PR, the author and contributors will first look at the **descript
Then, reviewing **a few files that were modified for a single purpose** is a lot more easier than to review 30 files modified for many reasons (bug fix, UI improvements, typos in doc,...), even if all these changes make sense. Also, it's possible that we agree on some modification but not on some other, and we won't be able to merge the PR because of the changes that are not accepted.
-We do our best to keep the code as consistent as possible, and that mean we pay attention to the **formatting** of the code. If the code formatting is not consistent with our code base, we'll ask you to review it, which will take more time.
+We do our best to keep the code as consistent as possible, and that means we pay attention to the **formatting** of the code. If the code formatting is not consistent with our code base, we'll ask you to review it, which will take more time.
The last step of the review consists in **testing** the modification. If it doesn't work out of the box, we'll ask your to review your code and to ensure that it works as expected.