Commits

Steve Losh committed 5c84fa9

Proof 21-23.

Comments (0)

Files changed (2)

chapters/22.markdown

     :endif
 
 Vim echoes "two".  There's still nothing surprising, so what was I going on
-about at the beginning?
+about at the beginning of the chapter?
 
 Case Sensitivity
 ----------------
 break at some point.  Save yourself the trouble and type the extra character.
 
 When you're comparing integers this distinction obviously doesn't matter.
-Still, I feel that it's better to use the case-sensitive comparisons everywhere,
-even where they're not needed, than to forget them in a place that they *are*
-needed.
+Still, I feel that it's better to use the case-sensitive comparisons everywhere
+(even where they're not strictly needed), than to forget them in a place that
+they *are* needed.
 
 Using `==#` and `==?` with integers will work just fine, and if you change them
 to strings in the future it will work correctly.  If you'd rather use `==` for
-integers that's fine, but you need to remember to change the comparison if
+integers that's fine, just remember that you'll need to change the comparison if
 you change them to strings in the future.
 
 Exercises

chapters/23.markdown

 
 This will display two lines: "Meow!" and "0".  The first obviously comes from
 the `echom` inside of `Meow`.  The second shows us that if a Vimscript function
-doesn't return a value, it implicitly return `0`.  Let's use this to our
+doesn't return a value, it implicitly returns `0`.  Let's use this to our
 advantage.  Run the following commands:
 
     :::vim
 Read the first paragraph of `:help E124` and find out what characters you're
 allowed to use in function names.  Are underscores okay?  Dashes?  Accented
 characters?  Unicode characters?  If it's not clear from the documentation just
-try them out.
+try them out and see.
 
 Read `:help return`.  What's the "short form" of that command (which I told you
 to never use)?  Is it what you expected?  If not, why not?