From 299485ad5045e850bca6178d2a8786b016fc8f6f Mon Sep 17 00:00:00 2001 From: Ken Celenza Date: Fri, 4 Aug 2023 15:43:33 -0400 Subject: [PATCH] Update docs/user/lib_use_cases_acl.md Co-authored-by: Jeff Kala <48843785+jeffkala@users.noreply.github.com> --- docs/user/lib_use_cases_acl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/lib_use_cases_acl.md b/docs/user/lib_use_cases_acl.md index d579314b..26cf1828 100644 --- a/docs/user/lib_use_cases_acl.md +++ b/docs/user/lib_use_cases_acl.md @@ -1,6 +1,6 @@ # ACL -The ACL classes are intended to help guide the ACL conversation. It is not intended to solve every ACL challenge you may have. In essence, it provides sane defaults and welcomes you to extend the logic via supported extension mechanisms. Three patterns that heavily make up the capabilities are: +The ACL classes are intended to help guide the ACL conversation. It is not intended to solve every ACL challenge you may have. In essence, it provides sane defaults and welcomes you to extend the logic via supported extension mechanisms. There are three patterns that heavily make up the capabilities: - Expanding data to the ["Cartesian product"](#cartesian-product) (or permutations) of each rule, so that each product can be easily evaluated. - Providing a `f"{type}_*` method pattern, to dynamically find any `validate_*` or `enforce_*` method you provide.