From de525473b490b22fb3b1daf066bb62fd811f64dd Mon Sep 17 00:00:00 2001 From: Brooklyn Zelenka Date: Thu, 2 Nov 2023 15:27:58 -0700 Subject: [PATCH] Update README.md Co-authored-by: Brian Ginsburg <7957636+bgins@users.noreply.github.com> Signed-off-by: Brooklyn Zelenka --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6b150766..bf56548d 100644 --- a/README.md +++ b/README.md @@ -332,7 +332,7 @@ For example, a capability may used to represent the ability to send email from a > > —[Mark Miller], [Robust Composition] -The set of capabilities delegated by a UCAN is called its "authority." To frame it another way, it's the set of effects that a principal can cause, and functions as a declarative description of delegated abilities. +The set of capabilities delegated by a UCAN is called its "authority." To frame it another way, it's the set of effects that a principal can cause, and acts as a declarative description of delegated abilities. Merging capability authorities MUST follow set semantics, where the result includes all capabilities from the input authorities. Since broader capabilities automatically include narrower ones, this process is always additive. Capability authorities can be combined in any order, with the result always being at least as broad as each of the original authorities.