Combined quick fixes from several Push Requests.

acknowledgements.markdown

@@ -24,7 +24,6 @@ requests, pointed out typos, raised issues, and otherwise contributed:
 * [lheiskan](https://github.com/lheiskan)
 * [lightningdb](https://github.com/lightningdb)
 * [manojkumarm](https://github.com/manojkumarm)
-* [manojkumarm](https://github.com/manojkumarm)
 * [markscholtz](https://github.com/markscholtz)
 * [marlun](https://github.com/marlun)
 * [mattsacks](https://github.com/mattsacks)

chapters/01.markdown

@@ -60,7 +60,7 @@ Read `:help echo`.
 
 Read `:help echom`.
 
-Read `:help messages`.
+Read `:help :messages`.
 
 Add a line to your `~/.vimrc` file that displays a friendly ASCII-art cat
 (`>^.^<`) whenever you open Vim.

chapters/15.markdown

@@ -37,7 +37,7 @@ all the text inside the parentheses.  You can think of this new movement as
 "parameters".
 
 The `onoremap` command tells Vim that when it's waiting for a movement to give
-to an operator and it sees `p`, it should treat it like `i(`.  When we ran `dp`
+to an operator and it sees `p`, it should treat it as `i(`.  When we ran `dp`
 it was like saying "delete parameters", which Vim translates to "delete inside
 parentheses".
 

chapters/23.markdown

@@ -118,7 +118,7 @@ Let's try using it.  Run the following commands:
 What did we do here?
 
 * First we set the `textwidth` globally to `80`.
-* The we ran an if statement that checked if `TextwidthIsTooWide()` was truthy.
+* Then we ran an if statement that checked if `TextwidthIsTooWide()` was truthy.
 * This wound up not being the case, so the `if`'s body wasn't executed.
 
 Because we never explicitly returned a value, Vim returned `0` from the

chapters/25.markdown

@@ -48,7 +48,7 @@ Floats can also be specified in multiple ways.  Run the following command:
     :::vim
     :echo 100.1
 
-Notice that we're using `echo` here and not `echom` like we usually to.  We'll
+Notice that we're using `echo` here and not `echom` like we usually do.  We'll
 talk about why in a moment.
 
 Vim displays `100.1` as expected.  You can also use exponential notation.  Run

chapters/26.markdown

@@ -33,7 +33,7 @@ This time Vim displays `5`, because the strings are coerced to the numbers `3`
 and `2` respectively.
 
 When I said "Number" I really *meant* Number.  Vim will *not* coerce strings to
-Floats!  Try this command to see prove this:
+Floats!  Try this command to see proof of this:
 
     :::vim
     :echom 10 + "10.10"

chapters/28.markdown

@@ -34,8 +34,8 @@ We'll look at the function more later, but for now just trust that it returns
 the path of the previous buffer.  You can play with it using `echom` if you want
 to see for yourself.
 
-Once `bufname` is evaluated Vim the string `"rightbelow vsplit bar.txt"`.  The
-`execute` command evaluates this as a Vimscript command which opens the split
+Once `bufname` is evaluated Vim builds the string `"rightbelow vsplit bar.txt"`.  
+The `execute` command evaluates this as a Vimscript command which opens the split
 with the file.
 
 Is Execute Dangerous?