From e3a29176a6b3db6fde710cc70ae855e03211ac7a Mon Sep 17 00:00:00 2001 From: kirm99 Date: Wed, 25 Sep 2019 10:40:58 -0400 Subject: [PATCH 1/2] Added my name to the constributors list --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 71208ef..0f7f843 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ ## git-tutorial -Contributors: Sidney Kochman, Grace Roller +Contributors: Sidney Kochman, Grace Roller, Kirsten Martindale 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 d46e4b10eaef5c0097d525d135cd40a664f1f9d8 Mon Sep 17 00:00:00 2001 From: kirm99 Date: Wed, 25 Sep 2019 11:05:21 -0400 Subject: [PATCH 2/2] Fixed a spelling mistake --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 18e7fdf..ee9090c 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.