From 7958f0447f3214feb4015e2fd87e50d8defa3567 Mon Sep 17 00:00:00 2001 From: rsdexter Date: Wed, 25 Sep 2019 10:40:35 -0400 Subject: [PATCH 1/2] Add name to contributor list --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 71208ef..c5f30c5 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ ## git-tutorial -Contributors: Sidney Kochman, Grace Roller +Contributors: Sidney Kochman, Grace Roller, Robert Dexter Thank you to [Daniele Procida](https://dont-be-afraid-to-commit.readthedocs.io/en/latest/git/commandlinegit.html) and [Nicola Paolucci](https://www.atlassian.com/git/articles/git-forks-and-upstreams) for their amazing Git resources! From 541ed980933986077982d4a41f11da40e75097ea Mon Sep 17 00:00:00 2001 From: rsdexter Date: Wed, 25 Sep 2019 11:05:11 -0400 Subject: [PATCH 2/2] fixed a typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a791790..1d17b5e 100644 --- a/README.md +++ b/README.md @@ -214,7 +214,7 @@ Now, you can update the remote repository with these new changes: Up to this point, you've made changes to the original code base and updated your remote repositiory with those changes. Now you want to contribute back to the original repo. -To do this you'll open a **pull request**. Pull requests basically just merge one bracnch into another. But, pull requests are often used so maintainers can make sure the code getting merged in works and is up to project standards. They're also a great way to get feedback on your code. +To do this you'll open a **pull request**. Pull requests basically just merge one branch into another. But, pull requests are often used so maintainers can make sure the code getting merged in works and is up to project standards. They're also a great way to get feedback on your code. Go to your reposititory on GitHub. Click the **New pull request** button. Under the title **Open a pull request**, click the **compare across forks** option.