Fix grammar and input variable to verification interface.

Co-authored-by: Dave Longley <[email protected]>

index.html

@@ -4122,16 +4122,16 @@ <h3>Securing Mechanism Specifications</h3>
 
         <p>
 Securing mechanism specifications MUST provide a verification algorithm that
-returns only the information in the [=conforming document=] that has been
-secured, without any securing mechanism information included, such as `proof` or
+returns the information in the [=conforming document=] that has been
+secured in isolation, without any securing mechanism information included, such as `proof` or
 JOSE/COSE header parameters and signatures. Verification algorithms MAY return
 additional information that might be helpful (for example, during validation or
 for debugging purposes), such as securing mechanism details. A verification
 algorithm MUST provide an interface that receives a media type ([=string=]
-|inputMediaType|) and secured data ([=byte sequence=] or [=map=] |securedData|).
-If the verification algorithm expects a [=byte sequence=], provide |securedData|
+|inputMediaType|) and input data ([=byte sequence=] or [=map=] |inputData|).
+If the verification algorithm expects a [=byte sequence=], provide |inputData|
 to the algorithm. If the verification algorithm expects a [=map=], provide the
-result of [=parsing JSON bytes to an Infra value=] given |securedData|. Securing
+result of [=parsing JSON bytes to an Infra value=] given |inputData|. Securing
 mechanism specifications MAY provide additional algorithms and interfaces to the
 ones specified in this document. The verification algorithm returns a
 verification result with at least the following [=struct/items=]: