From d2acb51dc5b86ecc02de2f4ed39c2c027de71bcd Mon Sep 17 00:00:00 2001
From: zoevig <66307695+ZoeVig@users.noreply.github.com>
Date: Thu, 8 Jul 2021 14:50:25 +0100
Subject: [PATCH] Fixed small typo

---
 subjects/teacher/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/subjects/teacher/README.md b/subjects/teacher/README.md
index d5651538b..bc8c4616b 100644
--- a/subjects/teacher/README.md
+++ b/subjects/teacher/README.md
@@ -14,7 +14,7 @@ In a training folder, various folders `mystery` were prepared with some key diff
 To simplify your life as a teacher and as the answers will not be exactly the same in each `mystery` folder, you need to write a `teacher.sh` file that does the following:
 
 - step 1, it enters the `mystery` folder.(again, the names will vary)
-- step 2, it isolates, thru a similar command that you used to find it, and into an environment variable, the number (**and only the number**) of the key interview that helped solved the mystery (Unlike the interview number, the adress will not change across the `mystery` folders that will be tested, hence the command to find the interview is the same across all the `mystery` folders that will be tested).
+- step 2, it isolates, thru a similar command that you used to find it, and into an environment variable, the number (**and only the number**) of the key interview that helped solved the mystery (Unlike the interview number, the address will not change across the `mystery` folders that will be tested, hence the command to find the interview is the same across all the `mystery` folders that will be tested).
 - step 3, it prints the newly created environment variable.
 - step 4, it prints what the interview contains.
 - step 5, it executes the command that should have printed the shorted list of 4 suspects. (it shows only the license Plate, the Make, the Color, the Owner, and the Height)