Update rebase section

diff --git a/branching.md b/branching.md
index b4c4e872f4bab3a16adb66246d80f058b792fe73..3806a5079db91abf4f58cb674ac48ecf891a872c 100644 (file)
--- a/branching.md
+++ b/branching.md
@@ -26,10 +26,11 @@ that contains all commits in both branches. Command `git merge --no-ff NAME`
 will merge the branch `NAME` to itself. `--no-ff` avoids melting the branch
 being merged. It's hard to explain, better to show.
 
-# Rebase - change the base commit of branch
+# Change the base commit of branch
 Each branch start at some commit. This starting commit of the branch can be
-also changed usually because of keeping clean history. The command `git rebase
-COMMIT` takes current branch and put it on top of the `COMMIT`.
+also changed. The usual case is keeping clean history. The command `git rebase
+COMMIT_ID` takes current branch and put it on top of the `COMMIT_ID`. Also,
+`git rebase NAME` could be used for rebasing current branch on top of other.
 
 # Cheat sheet
 ## Explore
@@ -46,5 +47,6 @@ COMMIT` takes current branch and put it on top of the `COMMIT`.
 - `git merge --no-ff NAME`
 
 ## Rebase
-- `git rebase COMMIT`
-- `git rebase -i COMMIT`
+- `git rebase COMMIT_ID`
+- `git rebase -i COMMIT_ID`
+- `git rebase NAME`