update readme

README.md

@@ -10,7 +10,7 @@ We set out to provide a reference implementation in JavaScript.
 
 We also seek to remedy confusion over how JWT and JSON-LD Signatures are compatible, this implementation differs significantly from [Ed25519Signature2018](https://github.com/digitalbazaar/jsonld-signatures/blob/master/lib/suites/Ed25519Signature2018.js#L32). 
 
-If the signature is a valid JWS, then its property name should be `jws`, this library's signatures are `base64Url(hex(leftpad(r),hex(leftpad(s)),hex(v))`. This means that no JWS header is validated when the signature is validated. It also means this signature suite can be used to create a valid JWS for `ES256K-R`, but note that the JOSE algorithm registry does not contain these algorithms yet, and you may have trouble validating JWTs generated with these values such as [did-jwt](https://github.com/uport-project/did-jwt)
+If the signature is a valid JWS, then its property name should be `jws`, this library's signatures are `base64Url(hex(leftpad(r),hex(leftpad(s)),hex(v))`. This means that no JWS header is validated when the signature is verified. It also means this signature suite can be used to create a valid JWS for `ES256K-R`, but note that the JOSE algorithm registry does not contain these algorithms yet, and you may have trouble validating JWTs generated with these values such as [did-jwt](https://github.com/uport-project/did-jwt)
 
 [JSON Web Token (JWT) with ES256K (secp256k1) signature](https://connect2id.com/products/nimbus-jose-jwt/examples/jwt-with-es256k-signature)