Use normative language for error code per #25 (#37)

* Use normative language for error code per #25 * Update draft-ietf-scitt-scrapi.md --------- Co-authored-by: Steve Lasker <stevenlasker@hotmail.com>
ietf-wg-scitt · Dec 3, 2024 · e7751b5 · e7751b5
1 parent 39a0988
commit e7751b5
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/draft-ietf-scitt-scrapi.md b/draft-ietf-scitt-scrapi.md
@@ -123,7 +123,7 @@ application/concise-problem-details+cbor
 
 NOTE: SCRAPI is not a CoAP API. Nonetheless Constrained Problem Details objects ({{RFC9290}}) provide a useful CBOR encoding for problem details and avoids the need for mixing CBOR and JSON in endpoint implementations.
 
-As an example, submitting a Signed Statement with an unsupported signature algorithm would return a `400 Bad Request` status code and the following body:
+Examples of errors may include:
 
 ~~~cbor-diag
 {