Merge pull request #707 from timgates42/bugfix_typos

docs/filters.md

@@ -56,7 +56,7 @@ syntactically invalid string).
 
 The equality filter is used to check exact matching of attribute/value
 assertions.  This object will have an `attribute` and `value` property, and the
-`name` proerty will be `equal`.
+`name` property will be `equal`.
 
 The string syntax for an equality filter is `(attr=value)`.
 
@@ -295,7 +295,7 @@ f.matches({cn: 'foo'});  => false
 
 The approximate filter is used to check "approximate" matching of
 attribute/value assertions.  This object will have an `attribute` and
-`value` property, and the `name` proerty will be `approx`.
+`value` property, and the `name` property will be `approx`.
 
 As a side point, this is a useless filter. It's really only here if you have
 some whacky client that's sending this.  It just does an exact match (which

docs/guide.md

@@ -94,7 +94,7 @@ Want to run schema-less in ldapjs, or wire it up with some mongoose models? No
 problem.  Want to back it to redis? Should be able to get some basics up in a
 day or two.
 
-Basically, the ldapjs philospohy is to deal with the "muck" of LDAP, and then
+Basically, the ldapjs philosophy is to deal with the "muck" of LDAP, and then
 get out of the way so you can just use the "good parts."
 
 # Ok, cool. Learn me some LDAP!