1 files changed, 1 insertions, 1 deletions
diff --git a/PROTOCOL.u2f b/PROTOCOL.u2f
index fd4325b3a..69347e999 100644
--- a/PROTOCOL.u2f
+++ b/PROTOCOL.u2f
@@ -40,7 +40,7 @@ primarily use ECDSA signatures in the NIST-P256 field, though the FIDO2
 standard specifies additional key types, including one based on Ed25519.
 Use of U2F security keys does not automatically imply multi-factor
-authentication. From sshd’s perspective, a security key constitutes a
+authentication. From sshd's perspective, a security key constitutes a
 single factor of authentication, even if protected by a PIN or biometric
 authentication.  To enable multi-factor authentication in ssh, please
 refer to the AuthenticationMethods option in sshd_config(5).

diff --git a/PROTOCOL.u2f b/PROTOCOL.u2f index fd4325b3a..69347e999 100644 --- a/PROTOCOL.u2f +++ b/PROTOCOL.u2f
@@ -40,7 +40,7 @@ primarily use ECDSA signatures in the NIST-P256 field, though the FIDO2
40	standard specifies additional key types, including one based on Ed25519.	40	standard specifies additional key types, including one based on Ed25519.
41		41
42	Use of U2F security keys does not automatically imply multi-factor	42	Use of U2F security keys does not automatically imply multi-factor
43	authentication. From sshd’s perspective, a security key constitutes a	43	authentication. From sshd's perspective, a security key constitutes a
44	single factor of authentication, even if protected by a PIN or biometric	44	single factor of authentication, even if protected by a PIN or biometric
45	authentication. To enable multi-factor authentication in ssh, please	45	authentication. To enable multi-factor authentication in ssh, please
46	refer to the AuthenticationMethods option in sshd_config(5).	46	refer to the AuthenticationMethods option in sshd_config(5).