Fix multiple typo in docs

kanidm_book/src/accounts_and_groups.md

@@ -81,7 +81,7 @@ An example can be easily shown with:
 
 ## Why Can't I Change admin With idm_admin?
 
-As a security mechanism there is a distiction between "accounts" and "high permission
+As a security mechanism there is a distinction between "accounts" and "high permission
 accounts". This is to help prevent elevation attacks, where say a member of a
 service desk could attempt to reset the password of idm_admin or admin, or even a member of
 HR or System Admin teams to move laterally.
@@ -102,7 +102,7 @@ Further, groups that are considered "idm_high_privilege" can NOT be managed
 by the standard "idm_group_manage_priv" group.
 
 Management of high privilege accounts and groups is granted through the
-the "hp" variants of all privilieges. For example:
+the "hp" variants of all privileges. For example:
 
 * idm_hp_account_read_priv
 * idm_hp_account_manage_priv

kanidm_book/src/posix_accounts.md

@@ -25,7 +25,7 @@ group id to the gid number of the UPG.
 As there is now an equivalence between the uid and gid number of the user and the UPG,
 there is no benefit to seperating these values. As a result kanidm accounts *only*
 have a gidnumber, which is also considered to be it's uidnumber as well. This has a benefit
-of preventing accidental creation of a seperate group that has an overlapping gidnumber
+of preventing accidental creation of a separate group that has an overlapping gidnumber
 (the uniqueness attribute of the schema will block the creation).
 
 ### UPG generation

kanidmd/src/lib/constants/entries.rs

@@ -340,7 +340,7 @@ pub static JSON_DOMAIN_INFO_V1: &str = r#"{
     }
 }"#;
 
-// Anonymous should be the last opbject in the range here.
+// Anonymous should be the last object in the range here.
 pub static JSON_ANONYMOUS_V1: &str = r#"{
     "attrs": {
         "class": ["account", "object"],