From bf6d9bc7a3f88aab57ab55125d1f522b6c42f982 Mon Sep 17 00:00:00 2001 From: wbamberg Date: Mon, 3 Jun 2024 10:56:47 -0700 Subject: [PATCH] Update files/en-us/web/api/credential_management_api/credential_types/index.md Co-authored-by: Hamish Willee --- .../web/api/credential_management_api/credential_types/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/credential_management_api/credential_types/index.md b/files/en-us/web/api/credential_management_api/credential_types/index.md index a0ec08e1ae68732..87d2952fecea35a 100644 --- a/files/en-us/web/api/credential_management_api/credential_types/index.md +++ b/files/en-us/web/api/credential_management_api/credential_types/index.md @@ -68,7 +68,7 @@ The [WebOTP API](/en-US/docs/Web/API/WebOTP_API) defines the {{domxref("OTPCrede In browsers that support the `OTPCredential` type, the website's front end can call {{domxref("CredentialsContainer.get", "navigator.credentials.get()")}}, asking for an OTP credential, then ask the backend to generate a code and send the message containing it (only SMS is supported as a transport). The backend must send a specially formatted SMS message, which the browser can read. -The browser then returns an `OTPCredential` object in the fulfilment of the `Promise` returned from `get()`, and this object contains the code. The website front end can then use the code to autofill an input element on the site, or submit the code to the server automatically. +The browser then returns an `OTPCredential` object in the fulfilment of the `Promise` returned from `get()`, and this object contains the code. The website front end can use the code to autofill an input element on the site, or submit the code to the server automatically. ![Sequence diagram showing sign-in using an OTP credential.](otp-get.svg)