From 16f9f6e4095b0689258602dc19bbdf560e22b7de Mon Sep 17 00:00:00 2001 From: Jeremy LaCivita Date: Wed, 10 Jul 2024 12:11:30 -0400 Subject: [PATCH] fix: Make must/should/could definitions less sophomoric --- requirements/specifications/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/requirements/specifications/index.md b/requirements/specifications/index.md index e6da4a553..d2eda9457 100644 --- a/requirements/specifications/index.md +++ b/requirements/specifications/index.md @@ -37,11 +37,11 @@ In the Firebolt Specification JSON, every capability is given a `level` of eithe - `"should"` - `"could"` -A capability with the level set to `"must"` **MUST** be supported. +A capability with the level set to `"must"` **MUST** be supported or the implementation in question is not a certified Firebolt implementation. -A capability with the level set to `"should"` **SHOULD** be supported. +A capability with the level set to `"should"` **SHOULD** be supported, especially if the implementation supports similar requirements in a non-Firebolt interface. -A capability with the level set to `"could"` **COULD** be supported. +A capability with the level set to `"could"` **COULD** be supported at the implementations discretion. #### 3.1.1. Should vs Could This section is non-normative and does not denote any requiements.