Update hooks.asc

took me a few trial and errors to figure out what 'named appropriately' meant -- this would clear it up

also, you had the proper name of Git rather than the .git subdirectory

Author: ajoslin103

book/08-customizing-git/sections/hooks.asc

@@ -15,7 +15,7 @@ When you initialize a new repository with `git init`, Git populates the hooks di
 All the examples are written as shell scripts, with some Perl thrown in, but any properly named executable scripts will work fine – you can write them in Ruby or Python or what have you.
 If you want to use the bundled hook scripts, you'll have to rename them; their file names all end with `.sample`.
 
-To enable a hook script, put a file in the `hooks` subdirectory of your Git directory that is named appropriately and is executable.
+To enable a hook script, put a file in the `hooks` subdirectory of your .git directory that is named appropriately (without any extension) and is executable.
 From that point forward, it should be called.
 We'll cover most of the major hook filenames here.