Skip to content

Commit 1b6af38

Browse files
committed
Fix two grammatical errors
Signed-off-by: Thomas Ackermann <[email protected]>
1 parent 1d874a3 commit 1b6af38

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

book/09-git-and-other-scms/sections/client-tfs.asc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Git-tfs maps the branch you cloned from to `tfs/default`, and others get their o
134134

135135
Another thing to notice is the `git-tfs-id:` lines in the commit messages.
136136
Instead of tags, git-tfs uses these markers to relate TFVC changesets to Git commits.
137-
This has the implication that your Git commits will have a different SHA-1 hash before and after they has been pushed to TFVC.
137+
This has the implication that your Git commits will have a different SHA-1 hash before and after they have been pushed to TFVC.
138138

139139
===== Git-tf[s] Workflow
140140

@@ -259,7 +259,7 @@ There's a new `TFS_C35348` tag, indicating that TFVC is storing the exact same s
259259
It's important to note that not every Git commit needs to have an exact counterpart in TFVC; the `6eb3eb5` commit, for example, doesn't exist anywhere on the server.
260260

261261
That's the main workflow.
262-
There are a couple other considerations you'll want to keep in mind:
262+
There are a couple of other considerations you'll want to keep in mind:
263263

264264
* There is no branching.
265265
Git-tf can only create Git repositories from one TFVC branch at a time.

0 commit comments

Comments
 (0)