Merge pull request #1 from UtahDave/master

Just a couple proof reading suggestions for the README

Author: whiteinge

README.md

@@ -21,17 +21,17 @@ sufficient to showcase the differences between that many versions. In addition,
 the default keybindings are not well suited to moving individual changes
 between that many windows.
 
-The screenshow below is an example of Vimdiff as a Git mergetool using default
+The screenshot below is an example of Vimdiff as a Git mergetool using default
 settings. None of the conflicts have an obvious resolution:
 
 ![](./_utils/default-vimdiff.png)
 
 ### Editing Conflict Markers is Hard
 
 When human intervention is needed it is rarely as simple as choosing the "left"
-change or the "right" change. The correct resolution often involes a mix of
+change or the "right" change. The correct resolution often involves a mix of
 both changes. It is difficult to manually edit a file containing Git conflict
-markers because the human eye isn't well-suited to spotting subtle differences,
+markers because the human eye isn't well suited to spotting subtle differences,
 particularly when the differences are not adjacent:
 
 ![](./_utils/conflict-markers.png)
@@ -43,7 +43,7 @@ the resolution more clear. The merge base and history of each version of the
 conflict is a useful reference to learn the intent of each conflicting change,
 however those are not as useful to see in the diff.
 
-Vimdiff is well-suited to two-way diffs:
+Vimdiff is well suited to two-way diffs:
 
 ![](./_utils/vim-diffconflicts.png)