Show more features in the README

Closes GH-39

Author: frou

README.md

@@ -16,20 +16,34 @@ This package was originally created by [@psykzz](https://github.com/psykzz) and
 
 ## How to use
 
-Place the text insertion cursor on the line you are interested in, then press <kbd>Ctrl</kbd><kbd>Alt</kbd><kbd>B</kbd> (Mac/Windows) or <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>Q</kbd> (Linux).
+Place the text cursor on the line you are interested in, then press <kbd>Ctrl</kbd><kbd>Alt</kbd><kbd>B</kbd> (Mac/Windows) or <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>Q</kbd> (Linux).
 
 (Instead of pressing the keyboard shortcut, you can alternatively right click and select *Git Blame* from the context menu)
 
 The blame information will appear:
 
-![Screenshot](https://raw.githubusercontent.com/frou/st3-gitblame/master/screenshot.png)
+![Screenshot](https://raw.githubusercontent.com/frou/st3-gitblame/master/docs/screenshot-blame.png)
 
-You can then click `[Show]` to show the commit in full, or `[Copy]` to copy the Commit ID (aka SHA) to your clipboard. To close the blame information, click the `×` icon, or press the keyboard shortcut again.
+If you want, you can then click `[Show]` to show the commit in full:
+
+![Screenshot](https://raw.githubusercontent.com/frou/st3-gitblame/master/docs/screenshot-blame-show.png)
+
+...or click `[Copy]` to copy the Commit ID (aka SHA) to your clipboard.
+
+If the latest blame information was not as illuminating as you hoped for, click the `[Prev]` to step back through multiple previous commits that affected the line.
+
+To close the blame information, click the `×` icon, or press the keyboard shortcut again while the text cursor is still on the same line.
 
 ## Advanced use
 
-In combination with Sublime Text's *Multiple Cursor* feature, you can query blame information for more than one line simultaneously by first placing a cursor on each line you are interested in.
+In combination with Sublime Text's *Multiple Selection* feature, you can query blame information for more than one line simultaneously by first placing a text cursor on each line you are interested in, and then running as described above.
+
+You can also query blame information for every line in the entire file simultaneously by pressing <kbd>Ctrl</kbd><kbd>Alt</kbd><kbd>Shift</kbd><kbd>B</kbd> (Mac/Windows) or <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>C</kbd> (Linux). Doing this shows blame information in a different style (it's located to the left of the content, and more compact, but with fewer features):
+
+![Screenshot](https://raw.githubusercontent.com/frou/st3-gitblame/master/docs/screenshot-blameall.png)
+
+To close all of them, click the `×` icon on any one of them, or press the keyboard shortcut again.
 
-You can also query blame information for every line in the entire file simultaneously by pressing <kbd>Ctrl</kbd><kbd>Alt</kbd><kbd>Shift</kbd><kbd>B</kbd> (Mac/Windows) or <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>C</kbd> (Linux). To close all of them, click the `×` icon on one of them, or press the keyboard shortcut again.
+As well as via keyboard shortcuts, this package's commands are also made available in the *Command Palette*. Type "Git Blame" into it to find them:
 
-This package's commands are also made available in the *Command Palette*. Type "Git Blame" into it to find them.
+![Screenshot](https://raw.githubusercontent.com/frou/st3-gitblame/master/docs/screenshot-palette.png)