diff --git a/README.md b/README.md
index 5dc0eff..707d9e6 100644
--- a/README.md
+++ b/README.md
@@ -1,17 +1,20 @@
 # Git Workflow Exercise
-For this exercise we will use [Github Flow](https://guides.github.com/introduction/flow/), a modified, lightweight version of [Git Flow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).
+For this exercise we will use [Github Flow](https://help.github.com/en/articles/github-flow), a modified, lightweight version of [Git Flow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).
+
+
+GitHub Flow is a simple and effective branching strategy which the folks at GitHub use. Most teams actually do not need everything Git Flow gives them and are much better off with a simpler workflow.
 
 ## Instructions
 This repo contains answers to the collection of [Frontend Interview Questions](https://github.com/h5bp/Front-end-Developer-Interview-Questions#front-end-job-interview-questions) by the developers behind [H5BP](https://html5boilerplate.com/).
 
 1. Clone this repository.
 
-2. Choose an interview question to answer from [Frontend Interview Questions](https://github.com/h5bp/Front-end-Developer-Interview-Questions#front-end-job-interview-questions)
+2. Choose a previously unanswered interview question from [Frontend Interview Questions](https://github.com/h5bp/Front-end-Developer-Interview-Questions#front-end-job-interview-questions) <u>or</u> improve upon an existing answer.
 
-3. Create and push a new feature branch that is named adequately to inform your team of which question you have chosen to answer.
+3. Create a new feature branch that is named in the format of `feature/description-of-feature`.
 
-4. In the appropriate folder of your feature branch, create a [Markdown](https://guides.github.com/features/mastering-markdown/) file that contains the answer to your chosen question. The file should be named in the following format: `complete-text-of-question.md`
+4. In the appropriate folder, create a [Markdown](https://guides.github.com/features/mastering-markdown/) file that contains the answer to your chosen question. The file should be named in the following format: `complete-text-of-question.md`
 
 5. Once you are finished, commit your changes and push your feature branch to the repository.
 
-6. Follow the instructions for submitting a pull request.
\ No newline at end of file
+6. Follow the instructions for submitting/sending a [pull request](https://help.github.com/en/articles/creating-a-pull-request) to the owner of the repository.
\ No newline at end of file