Skip to content

Commit 1430469

Browse files
Merge pull request InterviewMap#102 from Dheyson/patch-1
Update git-en.md
2 parents ebd8d29 + 35711b7 commit 1430469

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Git/git-en.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99

1010
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
1111

12-
This is not for rookie, we'll introduce somthing about more advanced.
12+
This is not for rookie, we'll introduce something about more advanced.
1313
## Merge with Rebase
1414
This command shows no difference with the command `merge`.
1515

@@ -21,7 +21,7 @@ After using `rebase ` , the commits from `develop` will be moved to the third `c
2121

2222
![](https://user-gold-cdn.xitu.io/2018/4/23/162f11cc2cb8b332?w=505&h=563&f=png&s=26514)
2323

24-
Compare with `merge`, the result of `rebase` is very clear with a single flow. But if there is any conflict, you'll be in troule to solving them. You have to solve them one by one , while you only need to solve them one-time if using `merge`.
24+
Compare with `merge`, the result of `rebase` is very clear with a single flow. But if there is any conflict, you'll be in trouble to solving them. You have to solve them one by one , while you only need to solve them one-time if using `merge`.
2525

2626
You should use `rebase` on the local branchs which need be rebased. If you need to `rebase` the `develop` to the `master`, you should do as follows:
2727

0 commit comments

Comments
 (0)