Remove vague statement about "any securing mechanism" per @jandrieu.

Co-authored-by: Joe Andrieu <[email protected]>

Author: msporny

index.html

@@ -3693,10 +3693,7 @@ <h3>Ecosystem Compatibility</h3>
 Readers are advised that a digital credential is only considered a
 <a>verifiable credential</a> or a <a>verifiable presentation</a> if it is a
 <a>conforming document</a> and it utilizes at least one securing mechanism, as
-described by this specification. Additionally, any <a>conforming document</a>,
-using any securing mechanism, where every claim in the <a>conforming
-document</a> is secured, is considered a <a>verifiable credential</a> or a
-<a>verifiable presentation</a>. While some communities might call some digital
+described by their respective requirements in this specification. While some communities might call some digital
 credential formats that are not <a>conforming documents</a>
 "verifiable credentials", doing so does NOT make that digital credential a
 <a>verifiable credential</a> or a <a>verifiable presentation</a> as defined by