Fix a few small typos
This commit is contained in:
parent
2ee04b14a3
commit
9fb353c278
|
@ -52,7 +52,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)`.
|
||||
|
||||
|
@ -263,7 +263,7 @@ the filter in the `filter` property.
|
|||
|
||||
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
|
||||
|
|
|
@ -91,7 +91,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!
|
||||
|
|
Loading…
Reference in New Issue