From 149857f246fef4d83f5f37a7e5a87fdedce113f2 Mon Sep 17 00:00:00 2001 From: Tony Murray Date: Thu, 17 Aug 2017 12:49:44 -0500 Subject: [PATCH] Update Using-Git.md (#7178) --- doc/Developing/Using-Git.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/Developing/Using-Git.md b/doc/Developing/Using-Git.md index 4a410dadde..1cc7174c30 100644 --- a/doc/Developing/Using-Git.md +++ b/doc/Developing/Using-Git.md @@ -70,7 +70,7 @@ Now, create a new branch to do you work on. It's important that you do this as y one feature at a time and submit them as pull requests individually. If you did all your work in the master branch then it gets a bit messy! -You need to give you branch a name. If an issue is open (or closed on GitHub) then you can use that, in this example if the issue number is 123 then we will use issue-123. If a post exists on the community forum then you can use the post id like community-123. You're also welcome to use any arbitrary name for your branch but try and make it relevant to what the branch is. +You need to give your branch a name. If an issue is open (or closed on GitHub) then you can use that, in this example if the issue number is 123 then we will use issue-123. If a post exists on the community forum then you can use the post id like community-123. You're also welcome to use any arbitrary name for your branch but try and make it relevant to what the branch is. ```bash git checkout -b issue-123