diff --git a/content/2018/10/tls-client-authentication-leaks-user.html b/content/2018/10/tls-client-authentication-leaks-user.html
index cd753ee..4305d2a 100644
--- a/content/2018/10/tls-client-authentication-leaks-user.html
+++ b/content/2018/10/tls-client-authentication-leaks-user.html
@@ -32,7 +32,7 @@ profile their usage.
 I was confident that this was the case as I know that the entire
 handshake is in the clear.  It isn't till the Finished messages that
 the session becomes encrypted.  (TLS 1.3 fixed this by using a new
-derived key, [sender]_handshake_traffic_secret, to encrypt all the
+derived key, `[sender]_handshake_traffic_secret`, to encrypt all the
 server params, which the client will use to encrypt it's response to
 the certificate request in the server params.)  I decided to verify
 that this was the case.