--- a/chapters/13.markdown Sat Apr 21 02:12:44 2012 +0100
+++ b/chapters/13.markdown Sat Apr 21 02:28:18 2012 +0100
@@ -41,7 +41,7 @@
Create a few more "snippet" abbreviations for some of the things you type often
in specific kinds of files. Some good candidates are `return` for most
-languages, `function` for javascript, and thinks like `“` and `”`
+languages, `function` for javascript, and things like `“` and `”`
for HTML files.
Add these snippets to your `~/.vimrc` file.
--- a/chapters/15.markdown Sat Apr 21 02:12:44 2012 +0100
+++ b/chapters/15.markdown Sat Apr 21 02:28:18 2012 +0100
@@ -104,7 +104,7 @@
perform the operator on the text inside the next set of parenthesis on the
current line.
-Let's make a companion "inside last parenthesis" ("previous" woud be a better
+Let's make a companion "inside last parenthesis" ("previous" would be a better
word, but it would shadow the "paragraph" movement). Run the following command:
:::vim
--- a/chapters/21.markdown Sat Apr 21 02:12:44 2012 +0100
+++ b/chapters/21.markdown Sat Apr 21 02:28:18 2012 +0100
@@ -92,7 +92,7 @@
* Strings that start with a number are coerced to that number, otherwise they're
coerced to `0`.
* Vim will execute the body of an `if` statement when its condition evaluates to
- a non-zero integer, *after* all coersion takes place.
+ a non-zero integer, *after* all coercion takes place.
Else and Elseif
---------------
@@ -115,4 +115,4 @@
Exercises
---------
-Drink a beer to console yourself about Vim's coersion of strings to integers.
+Drink a beer to console yourself about Vim's coercion of strings to integers.
--- a/chapters/22.markdown Sat Apr 21 02:12:44 2012 +0100
+++ b/chapters/22.markdown Sat Apr 21 02:28:18 2012 +0100
@@ -66,7 +66,7 @@
: echom "this must be the one"
:endif
-**Woah**. Stop right there. Yes, you saw that right.
+**Whoa**. Stop right there. Yes, you saw that right.
**The behavior of `==` depends on a user's settings.**
--- a/chapters/26.markdown Sat Apr 21 02:12:44 2012 +0100
+++ b/chapters/26.markdown Sat Apr 21 02:28:18 2012 +0100
@@ -120,7 +120,7 @@
:echom '\n\\'
Vim displays `\n\\`. Using single quotes tells Vim that you want the string
-*exactly* as-in, with no escape sequences. The one exception is that two single
+*exactly* as-is, with no escape sequences. The one exception is that two single
quotes in a row will produce a single single quote. Try this command:
:::vim
--- a/chapters/30.markdown Sat Apr 21 02:12:44 2012 +0100
+++ b/chapters/30.markdown Sat Apr 21 02:28:18 2012 +0100
@@ -14,7 +14,7 @@
the return needed to actually perform the search. Combining `normal!` with
`execute` fixes that problem.
-`execute` lets you build commands programatically, so you can use Vim's normal
+`execute` lets you build commands programmatically, so you can use Vim's normal
string escape sequences to generate the non-printing characters you need. Try
the following command:
--- a/chapters/38.markdown Sat Apr 21 02:12:44 2012 +0100
+++ b/chapters/38.markdown Sat Apr 21 02:28:18 2012 +0100
@@ -3,7 +3,7 @@
In one of the first chapters we talked about how to set options in Vim. For
boolean options we can use `set someoption!` to "toggle" the option. This is
-expecially nice when we create a mapping for that command.
+especially nice when we create a mapping for that command.
Run the following command:
--- a/chapters/51.markdown Sat Apr 21 02:12:44 2012 +0100
+++ b/chapters/51.markdown Sat Apr 21 02:28:18 2012 +0100
@@ -353,7 +353,7 @@
* Using a single function with several arguments to simplify creating related
mappings.
* Building up functionality in a Vimscript function incrementally.
-* Building up an `execute 'normal! ...'` string programatically.
+* Building up an `execute 'normal! ...'` string programmatically.
* Using simple searches to move around with regexes.
* Using special regex atoms like `%^` (beginning of file).
* Using search flags to modify how searches work.