Provide a short description explaining the what, why, and how of your project. Use the following questions as a guide:

• my motivation was to learn how to create a website
• I built this project to better my ability to learn about coding
• it solves the problem of not having a study guide
• how to make a website

N/A

To use this Prework Study Guide, each section is layed out for the user to read and use to study. furthermore, in the DevTools the user is able to get suggestions on what to study first.

N/A

The last section of a high-quality README file is the license. This lets other developers know what they can and cannot do with your project. If you need help choosing a license, refer to https://choosealicense.com/.

🏆 The previous sections are the bare minimum, and your project will ultimately determine the content of this document. You might also want to consider adding the following sections.

Badges aren't necessary, but they demonstrate street cred. Badges let other developers know that you know what you're doing. Check out the badges hosted by shields.io. You may not understand what they all represent now, but you will in time.

If your project has a lot of features, list them here.

If you created an application or package and would like other developers to contribute to it, you can include guidelines for how to do so. The Contributor Covenant is an industry standard, but you can always write your own if you'd prefer.

Go the extra mile and write tests for your application. Then provide examples on how to run them here.