# HG changeset patch
# User Steve Losh <steve@stevelosh.com>
# Date 1365042566 14400
# Node ID 3a16b2131235c37ad9e69b7c1437f9542ff9d560
# Parent  21526a22974e7bb102f5719cc0c5579769de8027
Proof 42-48.

diff -r 21526a22974e -r 3a16b2131235 chapters/42.markdown
--- a/chapters/42.markdown	Wed Apr 03 22:14:56 2013 -0400
+++ b/chapters/42.markdown	Wed Apr 03 22:29:26 2013 -0400
@@ -23,8 +23,8 @@
 a bunch of related stuff".  Vim has a more specific meaning of "plugin", which
 is "a file in `~/.vim/plugins/`".
 
-Most of the time I'll be using the first definition, but if something is unclear
-please [let me know](http://twitter.com/stevelosh/) and I'll try to reword it.
+Most of the time I'll be using the first definition.  I'll try to be clear when
+I mean the second.
 
 ~/.vim/colors/
 --------------
@@ -50,7 +50,7 @@
 
 Any files in `~/.vim/ftdetect/` will *also* be run every time you start Vim.
 
-"ftdetect" stands for "filetype detection".  The files in this directory should
+`ftdetect` stands for "filetype detection".  The files in this directory should
 set up autocommands that detect and set the `filetype` of files, and *nothing
 else*.  This means they should never be more than one or two lines long.
 
@@ -59,7 +59,7 @@
 
 Files in `~/.vim/ftplugin/` are different.
 
-The naming of these files matters.  When Vim sets a buffer's `filetype` to
+The naming of these files matters!  When Vim sets a buffer's `filetype` to
 a value it then looks for a file in `~/.vim/ftplugin/` that matches.  For
 example: if you run `set filetype=derp` Vim will look for
 `~/.vim/ftplugin/derp.vim`.  If that file exists, it will run it.
@@ -76,7 +76,7 @@
 ~/.vim/indent/
 --------------
 
-Files in `~/.vim/indent/` are a lot like `ftplugin` files -- they get loaded
+Files in `~/.vim/indent/` are a lot like `ftplugin` files.  They get loaded
 based on their names.
 
 `indent` files should set options related to indentation for their filetypes,
@@ -102,8 +102,8 @@
 be loaded every time Vim starts, but *after* the files in `~/.vim/plugin/`.
 
 This allows you to override Vim's internal files.  In practice you'll rarely
-need this, so don't worry about it until you find yourself thinking "Vim sets
-option X and I want something different".
+need this, so don't worry about it until you find yourself thinking "Vim itself
+sets option `x`, but I want something different".
 
 ~/.vim/autoload/
 ----------------
@@ -127,3 +127,6 @@
 
 Reread this chapter.  I'm not kidding.  Make sure you understand (in a very
 rough way) what each directory we've talked about does.
+
+For extra credit, find some Vim plugins you use and look at how they structure
+their files.
diff -r 21526a22974e -r 3a16b2131235 chapters/43.markdown
--- a/chapters/43.markdown	Wed Apr 03 22:14:56 2013 -0400
+++ b/chapters/43.markdown	Wed Apr 03 22:29:26 2013 -0400
@@ -7,7 +7,7 @@
 
 In the past, when you wanted to use a plugin someone else wrote you would
 download the files and place them, one-by-one, into the appropriate directories.
-You could also use zip or tar to do the placing for you.
+You could also use `zip` or `tar` to do the placing for you.
 
 There are a few significant problems with this approach:
 
diff -r 21526a22974e -r 3a16b2131235 chapters/46.markdown
--- a/chapters/46.markdown	Wed Apr 03 22:14:56 2013 -0400
+++ b/chapters/46.markdown	Wed Apr 03 22:29:26 2013 -0400
@@ -44,7 +44,7 @@
 *regexes* instead of literal keywords.
 
 Notice that the regular expression we're using starts with `\v` which tells Vim
-to use "very magic" mode.  Reread the chapter on Basic Regular Expressions if
+to use "very magic" mode.  Reread the chapter on basic regular expressions if
 you're not sure what that means.
 
 In this particular case the "very magic" mode isn't necessary.  But in the
diff -r 21526a22974e -r 3a16b2131235 chapters/48.markdown
--- a/chapters/48.markdown	Wed Apr 03 22:14:56 2013 -0400
+++ b/chapters/48.markdown	Wed Apr 03 22:29:26 2013 -0400
@@ -145,3 +145,4 @@
 Read `:help foldminlines`.
 
 Read `:help foldignore`.
+