[directory-fortress-enmasse] branch master updated: sp.

[sm...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

smckinney pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/directory-fortress-enmasse.git


The following commit(s) were added to refs/heads/master by this push:
     new 21490a0  sp.
21490a0 is described below

commit 21490a07f9966af1639b8e36a6f87d968da009ca
Author: Shawn McKinney <sm...@apache.org>
AuthorDate: Thu Apr 11 17:45:12 2019 -0500

    sp.
---
 README-SECURITY-MODEL.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README-SECURITY-MODEL.md b/README-SECURITY-MODEL.md
index 71cd995..50e1206 100644
--- a/README-SECURITY-MODEL.md
+++ b/README-SECURITY-MODEL.md
@@ -92,7 +92,7 @@ a. All service invocations, except AccessMgr and DelAccessMgr, perform an ADMIN
  The entire list of permissions, and their mappings to services are listed in the table that follows.
 
 b. Some services (#'s 1 - 12 listed below) perform organizational verification, comparing the org on the ADMIN role with that on the target user or permission in the HTTP request.
- There are two types of organziations being checked, User and Permission.  
+ There are two types of organizations being checked, User and Permission.  
  
  For example, **roleAsgn** and **roleDeasgn**  (9 and 10 below) will verify that the caller has an ADMIN role with a user org unit that matches the ou of the target user.  
  There is a similar check on **roleGrant** and **roleRevoke** (11 and 12) verifying the caller has an activated ADMIN role with a perm org unit that matches the ou on the target permission.