From e240670a8e171280ac09123f216950824dd5f519 Mon Sep 17 00:00:00 2001
From: GroundedCastle <74363301+GroundedCastle@users.noreply.github.com>
Date: Mon, 11 Jan 2021 18:43:56 -0600
Subject: [PATCH] Update README.md

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

diff --git a/README.md b/README.md
index 8cfeb34..9e82429 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ Before you start you should have a few things installed on your machine:
 2. Jasmine.  Jasmine is a testing framework for JavaScript. Type `jasmine -v` to check for it. If you need to install it, type `npm install -g jasmine` to do so.
 3. A copy of this repository. Copies of repositories on your machine are called clones. If you need help cloning, you can learn how [here](https://docs.github.com/en/free-pro-team@latest/github/creating-cloning-and-archiving-repositories/duplicating-a-repository)
 
-Each exercise includes 3 files: a markdown file with a description of the task, an empty (or mostly empty) JavaScript file, and a set of tests.  To complete an exercise, you'll need to go to the exercise directory with `cd exerciseName` in the terminal and run `jasmine exerciseName.spec.js`.  This should run the test file and show you the output.  When you first run a test, it will fail.  This is by design! You must open `cd exerciseName` and write the code needed to get the test to pass. Some of the exercises have test conditions defined in their spec file that are defined as 'xit' compared to 'it'. This is purposeful. After you pass you first 'it', you will change the next 'xit' to an 'it' and test your code again. You'll do this until all conditions are satisfied.
+Each exercise includes 3 files: a markdown file with a description of the task, an empty (or mostly empty) JavaScript file, and a set of tests.  To complete an exercise, you'll need to go to the exercise directory with `cd exerciseName` in the terminal and run `jasmine exerciseName.spec.js`.  This should run the test file and show you the output.  When you first run a test, it will fail.  This is by design! You must open `cd exerciseName` and write the code needed to get the test to pass. Some of the exercises have test conditions defined in their spec file that are defined as 'xit' compared to 'it'. This is purposeful. After you pass your first 'it', you will change the next 'xit' to an 'it' and test your code again. You'll do this until all conditions are satisfied.
 
 The first exercise, `helloWorld`, will help the process become clearer.