setup

Author: beccaelenzil

README.md

@@ -16,16 +16,13 @@ While working on _Adagrams_, it may help to think of a physical metaphor for thi
 
 In this version of _Adagrams_, we will only be working with the English alphabet.
 
-![an image of a pile of letter tiles](assets/letter-tiles.jpeg)
+![an image of a pile of letter tiles](images/letter-tiles.jpeg)
 
-
-## Project Development
-
-### Pair Programming
+## Pair Programming
 
 Utilize good pair programming practices. Refer to articles from the [Agile Alliance](http://guide.agilealliance.org/guide/pairing.html), the [Agile Institute](http://powersoftwo.agileinstitute.com/2015/02/benefits-of-pair-programming-revisited.html), and the lesson in Learn titled Intro to Pair Programming from Approaching a Problem if you need a refresher for some best practices. Switch _driver_ and _navigator_ roles often. When there is uncertainty or confusion, step away from the keyboard and discuss, plan, and document on paper or whiteboard before continuing.
 
-### One-Time Project Setup
+## One-Time Project Setup
 
 Follow these directions once, a the beginning of your project:
 
@@ -36,47 +33,45 @@ Follow these directions once, a the beginning of your project:
 
 ![Fork Button](images/fork.png)
 
-1. In Github, add the other membe(s) of your team as collaborators to the repository. Do this by a The student who forked the respository should first choosing **Settings** from the top menu bar, then **Manage access** from the left navigation, and finally **Invite teams or people**.
+2. In Github, add the other membe(s) of your team as collaborators to the repository. Do this by a The student who forked the respository should first choosing **Settings** from the top menu bar, then **Manage access** from the left navigation, and finally **Invite teams or people**.
 
 ![Settings](images/settings.png)
+
 ![Manage access](images/manage-access.png)
+
 ![Invite teams or people](images/invite.png)
 
 The member(s) who are invite will need to accept the invitation either by accepting an email invitation or accepting the invitation in Github.
 
-
-
-
-
 *Each member of the pair should complete the following steps:*
 
-2. Navigate to your projects folder named `projects`
+3. Navigate to your projects folder named `projects`
 
 ```bash
 $ cd ~/Developer/projects
 ```
 
-. "Clone" (download a copy of this project) into your projects folder. This command makes a new folder called `adagrams-py`, and then puts the project into this new folder.  Make sure you are cloning from your copy of the project and not the class version (ada-cX).
+4. "Clone" (download a copy of this project) into your projects folder. This command makes a new folder called `adagrams-py`, and then puts the project into this new folder.  Make sure you are cloning from your copy of the project and not the class version (ada-cX).
 
 ```bash
 $ git clone ...
 ```
 
 Use `ls` to confirm there's a new project folder
 
-4. Move your location into this project folder
+5. Move your location into this project folder
 
 ```bash
 $ cd adagrams-py
 ```
 
-5. Create a virtual environment named `venv` for this project:
+6. Create a virtual environment named `venv` for this project:
 
 ```bash
 $ python3 -m venv venv
 ```
 
-6. Activate this environment:
+7. Activate this environment:
 
 ```bash
 $ source venv/bin/activate
@@ -96,22 +91,27 @@ $ pip install -r requirements.txt
 
 Summary of one-time project setup:
 
+One person:
+- [ ] Fork the project respository
+- [ ] Invite team members to the respository
+
+All team members:
 - [ ] `cd` into your `projects` folder
 - [ ] Clone the project onto your machine
-- [ ] `cd` into the `viewing-party` folder
+- [ ] `cd` into the `adagrams-py` folder
 - [ ] Create the virtual environment `venv`
 - [ ] Activate the virtual environment `venv`
 - [ ] Install the dependencies with `pip`
 
-### Workflow
+## Porject Development Workflow
 
 1. When you want to begin work on this project, ensure that your virtual environment is activated:
 
 ```bash
 $ source venv/bin/activate
 ```
 
-1. Run the game and play test your current wave.  Replace the word `wave` below with the wave number (ie, 1, 2, 3 or 4):
+2. Run the game and play test your current wave.  Replace the word `wave` below with the wave number (ie, 1, 2, 3 or 4):
 
 ```bash
 # Must be in activated virtual environment
@@ -123,18 +123,18 @@ $ python main.py wave
    - Check the `tests` folder, and find the test file you want to run
    - In that test file, read through each test case
 
-4. Run the tests for your specific wave
+2. Run the tests for your specific wave
 
 ```bash
 # Must be in activated virtual environment
 $ pytest tests/test_wave_01.py
 ```
 
-4. Use play-testing wth your partner to guide your development.
+3. Use play-testing wth your partner to guide your development.
 
-5. Use tests to verify your functions after thoroughly play-testing.
+4. Use tests to verify your functions after thoroughly play-testing.
 
-6. Use git to commit your work regularly!  Commit between each wave.
+5. Use git to commit your work regularly!  Commit between each wave.
 
 ```bash
 # Add your current work