From f006165f2052653781f35d8b3dfdb352c3d1c796 Mon Sep 17 00:00:00 2001 From: tyler99b Date: Wed, 25 Sep 2019 10:37:38 -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..b67f756 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ ## git-tutorial -Contributors: Sidney Kochman, Grace Roller +Contributors: Sidney Kochman, Grace Roller, Tyler Bejel 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 03e2bb2525e1af3045af09a71ffad5a68e4c9bcf Mon Sep 17 00:00:00 2001 From: tyler99b Date: Wed, 25 Sep 2019 11:05:42 -0400 Subject: [PATCH 2/2] Fixed typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2e0950b..36b0587 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.