From d22db5e6d4bb55af1e9c9614f89b398a83526dab Mon Sep 17 00:00:00 2001 From: Bron Gondwana Date: Thu, 2 Feb 2023 15:35:48 +1100 Subject: [PATCH] Quota: update the limit -> hardLimit conversion in a couple more places This appears to just be an oversight. Fixing up the terminology --- spec/quotas/quota.mdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/quotas/quota.mdown b/spec/quotas/quota.mdown index 0c209b59..9fad81ae 100644 --- a/spec/quotas/quota.mdown +++ b/spec/quotas/quota.mdown @@ -44,7 +44,7 @@ The quota object MAY contain the following fields: The warn limit set by this quota object, using the "resourceType" defined as unit of measure. It can be used to send a warning to an entity about to reach the hard limit soon, but with no action taken yet. If set, it -SHOULD be lower than the "softLimit" (if present and different from null) and the "limit". +SHOULD be lower than the "softLimit" (if present and different from null) and the "hardLimit". * softLimit: "UnsignedInt|null" @@ -52,7 +52,7 @@ SHOULD be lower than the "softLimit" (if present and different from null) and th It can be used to still allow some operations, but refuse some others. What is allowed or not is up to the server. For example, it could be used for blocking outgoing events of an entity (sending emails, creating calendar events, ...) while still receiving incoming events (receiving emails, receiving calendars events, ...). If set, it SHOULD be higher than the "warnLimit" -(if present and different from null) but lower than the "limit". +(if present and different from null) but lower than the "hardLimit". * description: "String|null"