From e45b2953510fc47395459b5e0cd29e58dc9c6b94 Mon Sep 17 00:00:00 2001 From: snakegandhi Date: Mon, 10 Jan 2022 19:38:55 -0500 Subject: [PATCH] added sentence directing user to docs for forking --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a85211d..c2a58a9 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ These exercises should be done when instructed during the course of the curricul ## How to use these exercises -1. Fork and copy this repository. Copies of repositories on your machine are called clones. If you need help cloning to your local environment you can learn how [here](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository). +1. Fork and copy this repository. To learn how to fork a repository, see [this link](Forking is an easy process, and can be learned [here](https://docs.github.com/en/get-started/quickstart/fork-a-repo). Copies of repositories on your machine are called clones. If you need help cloning to your local environment you can learn how [here](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository). 2. Go to an exercise directory and open the HTML file in your browser. You can either open the file directly, or use something like VSCode's Live Server. 3. For each exercise, view the README, and edit the CSS file to make the output in your browser look like the images provided. 4. Each README has a "Self Check" list. Use this to make sure you haven't missed any important details in your implementation.