Skip to content
This repository has been archived by the owner on May 14, 2024. It is now read-only.

Commit

Permalink
Merge pull request #707 from timgates42/bugfix_typos
Browse files Browse the repository at this point in the history
  • Loading branch information
UziTech committed Feb 25, 2021
2 parents 6719469 + be2b875 commit 0b2ac8b
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/filters.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)`.

Expand Down Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -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!
Expand Down

0 comments on commit 0b2ac8b

Please sign in to comment.