From e1f0f49de378f0467b0f0adc0f8390571250b020 Mon Sep 17 00:00:00 2001
From: Christopher Fremond <34804391+Frenchris@users.noreply.github.com>
Date: Tue, 27 Jul 2021 18:53:14 +0100
Subject: [PATCH] Update reviews.md
---
docs/reviews.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/reviews.md b/docs/reviews.md
index d5415772..3a9a60f1 100644
--- a/docs/reviews.md
+++ b/docs/reviews.md
@@ -23,21 +23,21 @@ Then, when a match with another student who also wants to review is found, you w
-Once you and the other student have confirmed the match, you can go and check the code of the other student on his repository in the component `Your review` :
+Once you and the other student have confirmed the match, you can go and check the code of the other student on their repository in the component `Your review` :
-When you have checked his code, those 4 steps will have to be completed to achieve the review :
+When you have checked their code, those 4 steps will have to be completed to achieve the review :
- You have to bet if the exercise of the other student will fail or succeed after running the tester
- The other student has to do the same with your exercise and make his own bet, that you will see on the component `Review of your exercise`
- Once the other student's bet is set, the tester button unblocks and you have to run it on your exercise to output the result determining if your exercise has failed or succeeded ; this result is compared to the other student's bet to determine if it was wrong or right
-- The other student also has to run the tester on his exercise to determine his result and so if your bet was wrong or right
+- The other student also has to run the tester on their exercise to determine their result and so whether your bet was wrong or right
-In fact, a bet is succeeded if it is equal to the tester output :
+A bet is considered succeeded if it is equal to the tester output :
You can have those 4 cases :