improve README somewhat

Signed-off-by: Kipras Melnikovas <kipras@kipras.org>

Author: kiprasmel

README.md

@@ -11,7 +11,9 @@ stacked diffs in git, seamlessly.
 	</p>
 </div>
 
-why jump through branches manually, when we can extend `git rebase -i` instead?
+previously, if you wanted to adopt a stacked branch workflow, you'd have to do a lot of manual work every time you'd update anything in your stack -- jump thru each branch, re-rebase it on top of the previous one, get rid of duplicate commits, resolve conflicts, try to remember what the next branch was, and repeat...
+
+there must be a better way. and that's exactly how git-stacked-rebase came to be. 
 
 a branch is just a reference to some commit (literally, it's a single-line file that contains a 40-character commit SHA -- check your `.git/refs/` folder). why not just work on your latest feature branch, rebase comfortably, and then have your tool automatically update the partial branches to make them point to the correct new commits?
 
@@ -25,6 +27,8 @@ it's not only a CLI either - it's first and foremost a javascript library, and t
 
 in the future, we could create host-specific adapters. they could be used to automate some simple tasks, such as creating a pull request, or changing the base branch of a pull request, etc.
 
+there are bigger plans as well, such as creating a browser extension to improve the experience of exploring stacked PRs.
+
 ## Progress
 
 follow [http://kiprasmel.github.io/notes/git-stacked-rebase.html](http://kiprasmel.github.io/notes/git-stacked-rebase.html)
@@ -48,10 +52,5 @@ git config --global alias.rr             git-stacked-rebase
 ## Usage
 
 ```sh
-cd repo/
-
-# checkout your remote branches locally (until we automate it w/ a command?). 
-# then, checkout to the latest one.
-# then:
-
 git-stacked-rebase --help
+```