From d6498e10aacaebf5b8c334b6417b6f0bab2e8d2d Mon Sep 17 00:00:00 2001 From: BigBlueHat Date: Tue, 3 Dec 2024 16:55:03 -0500 Subject: [PATCH] Improve text based on @TallTed review. Co-authored-by: Ted Thibodeau Jr --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index abe55c3..313a45b 100644 --- a/README.md +++ b/README.md @@ -104,8 +104,8 @@ parameters, in which case they do not specify `oauth2` or `zcap` properties. Please check specific test suite READMEs for further details on implementation properties and endpoints. Test suites MAY specify additional properties and features for endpoints such as mandatory JSON-LD contexts, keyTypes settings, additional tags for specific tests such as Enveloped Proofs, -and supported VC Data Model versions. Endpoints in most cases should: be VC-API capable; be able to sign and/or -verify using `did:key`; and be able to resolve the following contexts: +and supported VC Data Model versions. In most cases, endpoints are expected to: be capable +of using the test suite API; be capable of signing and/or verifying using `did:key`; and support the following contexts: - https://www.w3.org/ns/credentials/examples/v2 - https://www.w3.org/2018/credentials/v1