fmt

core/cap-0052.md

@@ -136,9 +136,17 @@ in the future.
 
 #### Webauthn / Passkeys
 
-The base64 encode/decode interface is largely motivated by the webauthn use case. Webauthn involves an application and device holding a key and using that key for authentication and authorization. The messages that Webauthn signs are JSON and contain a base64 url encoded challenge value.
-
-To implement Webauthn on Stellar in Soroban custom account contracts the challenge would be the hash of an authorization entry. Webauthn base64 url encodes it and the contract that does verification would either need to be able to decode the challenge value to compare with the value it expects, or be able to encode the value it expects to compare with the encoded value found in the JSON message.
+The base64 encode/decode interface is largely motivated by the webauthn use
+case. Webauthn involves an application and device holding a key and using that
+key for authentication and authorization. The messages that Webauthn signs are
+JSON and contain a base64 url encoded challenge value.
+
+To implement Webauthn on Stellar in Soroban custom account contracts the
+challenge would be the hash of an authorization entry. Webauthn base64 url
+encodes it and the contract that does verification would either need to be able
+to decode the challenge value to compare with the value it expects, or be able
+to encode the value it expects to compare with the encoded value found in the
+JSON message.
 
 For example, a client data JSON:
 ```json