fixup assertion signature dfn

index.bs

@@ -1339,12 +1339,12 @@ Authenticators produce cryptographic signatures for two distinct purposes:
     signature=] is signed by an [=attestation private key=], which is chosen depending on the type of [=attestation=] desired.
     For more details on [=attestation=], see [[#sctn-attestation]].
 2. An <dfn>assertion signature</dfn> is produced when the [=authenticatorGetAssertion=] method is invoked. It represents an
-    assertion by the authenticator that the user has consented to a specific transaction, such as logging in, or completing a
-    purchase. Thus, an assertion signature asserts that the authenticator which possesses a particular credential private key
-    has established, to the best of its ability, that the human who is requesting this transaction is the same human who
-    consented to creating that particular credential. It also provides additional information that might be useful to the
-    caller, such as the means by which user consent was provided, and the prompt that was shown to the user by the
-    authenticator.
+    assertion by the [=authenticator=] that the user has [=user consent|consented=] to a specific transaction, such as logging
+    in, or completing a purchase. Thus, an [=assertion signature=] asserts that the [=authenticator=] possessesing a particular
+    [=credential private key=] has established, to the best of its ability, that the user requesting this transaction is the
+    same user who [=user consent|consented=] to creating that particular [=public key credential=]. It also provides additional
+    information that might be useful to the caller, such as the means by which [=user consent=] was provided, and the prompt
+    that was shown to the user by the [=authenticator=].
 
 The formats of these signatures, as well as the procedures for generating them, are specified below.