diff --git a/draft-ietf-cose-hash-envelope.md b/draft-ietf-cose-hash-envelope.md
index 76d9c42..0e0ba52 100644
--- a/draft-ietf-cose-hash-envelope.md
+++ b/draft-ietf-cose-hash-envelope.md
@@ -161,7 +161,7 @@ The signature is produced using ES384 which means using ECDSA with SHA384 hash f
 
 This example is chosen to highlight that an existing system may use a hash algorithm such as sha256.
 This hash becomes the payload of a cose-sign1.
-When signed with a signature algorithm that is paramaterized by hash function, such as ECDSA with SHA384, the to be signed structure as described in Section 4.4 of RFC9052.
+When signed with a signature algorithm that is parameterized via a hash function, such as ECDSA with SHA384, the to be signed structure as described in Section 4.4 of RFC9052.
 
 The resulting signature is over the protected header and payload, providing integrity and authenticity for the hash algorithm, content type and location of the associated resource, in this case a software bill of materials.