Skip to content

Commit 6bb8b13

Browse files
Merge pull request TheOdinProject#321 from Alex-Nemet/fix_typo_readme
Readme.md: fix spelling
2 parents 34d63cc + 614b8b8 commit 6bb8b13

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Diff for: README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,10 @@ If you have a suggestion to improve an exercise, an idea for a new exercise, or
1010

1111
## How To Use These Exercises
1212

13+
1314
1. Fork and clone this repository. To learn how to fork a repository, see the GitHub documentation on how to [fork a repo](https://docs.github.com/en/get-started/quickstart/fork-a-repo).
1415
- Copies of repositories on your machine are called clones. If you need help cloning to your local environment you can learn how from the GitHub documentation on [cloning a repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository).
15-
2. Before you start working on any execises, you should first ensure you have the following installed:
16+
2. Before you start working on any exercises, you should first ensure you have the following installed:
1617
- **NPM**. You should have installed NPM already in our [Installing Node.js](https://www.theodinproject.com/paths/foundations/courses/foundations/lessons/installing-node-js) lesson. Just in case you need to check, type `npm --version` in your terminal. If you get back `Command 'npm' not found, but can be installed with:`, **do not follow the instructions in the terminal** to install with `apt-get` as this causes permission issues. Instead, go back to the installation lesson and install Node with NVM by following the instructions there.
1718
- **Jest**. After cloning this repository to your local machine and installing NPM, go into the newly created directory (`cd javascript-exercises`) and run `npm install`. This will install Jest and set up the testing platform based on our preconfigured settings.
1819
3. Each exercise includes the following:
@@ -21,7 +22,6 @@ If you have a suggestion to improve an exercise, an idea for a new exercise, or
2122
- A `solutions` directory that contains a solution and the same test file with all of the tests unskipped.
2223

2324
To complete an exercise, you'll need to go to the exercise directory with `cd exerciseName` in the terminal and run `npm test 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 the exercise file and write the code needed to get the test to pass.
24-
2525
4. Some of the exercises have test conditions defined in their spec file as `test.skip` compared to `test`. This is purposeful. After you pass one `test`, you will change the next `test.skip` to `test` and test your code again. You'll do this until all conditions are satisfied. **All tests must pass at the same time**, and you should not have any `test.skip` instances by the time you finish an exercise.
2626
5. Once you successfully finish an exercise, check the `solutions` directory within each exercise to compare it with yours.
2727
- You should not be checking the solution for an exercise until you finish it!

0 commit comments

Comments
 (0)