From e4ecea6486a788fe669695372055a371e353d144 Mon Sep 17 00:00:00 2001
From: uerdogan <35709819+uerdogan@users.noreply.github.com>
Date: Mon, 5 Feb 2018 17:34:19 +0100
Subject: [PATCH] Update remote-branches.asc

---
 book/03-git-branching/sections/remote-branches.asc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/book/03-git-branching/sections/remote-branches.asc b/book/03-git-branching/sections/remote-branches.asc
index ed0d28ac6..b10635172 100644
--- a/book/03-git-branching/sections/remote-branches.asc
+++ b/book/03-git-branching/sections/remote-branches.asc
@@ -132,7 +132,7 @@ This gives you a local branch that you can work on that starts where `origin/ser
 (((branches, tracking)))(((branches, upstream)))
 Checking out a local branch from a remote-tracking branch automatically creates what is called a ``tracking branch'' (and the branch it tracks is called an ``upstream branch'').
 Tracking branches are local branches that have a direct relationship to a remote branch.
-If you're on a tracking branch and type `git pull`, Git automatically knows which server to fetch from and branch to merge into.
+If you're on a tracking branch and type `git pull`, Git automatically knows which server to fetch from and which branch to merge in.
 
 When you clone a repository, it generally automatically creates a `master` branch that tracks `origin/master`.
 However, you can set up other tracking branches if you wish -- ones that track branches on other remotes, or don't track the `master` branch.