Update docs/lfd121.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>

Author: david-a-wheeler

docs/lfd121.md

@@ -2129,7 +2129,7 @@ In a federated identity system, a server (such as a website) delegates authentic
 * The third party, called an Identity Provider (IdP), manages the user's credentials and authenticates users.
 * The server, commonly called a Relying Party (RP), trusts the IdP to make assertions about a user's identity.
 
-The **OpenID Connect (OIDC)** protocol is a common way to implement a federated identity system today on a website. In the OIDC protocol, when the user wants to sign into a website, the website redirects them to the IdP. The user authenticates to the IdP, and the IdP returns a token to the website indicating that the user authenticated successfully. The website checks that the token is valid, and if it is, signs the user in. OIDC is an authentication protocol built on top of the OAuth 2.0 authorization framework, and internally uses JSON web tokens (JWT) for exchanging user information. OIDC has generally replaced the older **OpenID*** specification [Federated Identity](https://developer.mozilla.org/en-US/docs/Web/Security/Authentication/Federated_identity).
+The **OpenID Connect (OIDC)** protocol is a common way to implement a federated identity system today on a website. In the OIDC protocol, when the user wants to sign into a website, the website redirects them to the IdP. The user authenticates to the IdP, and the IdP returns a token to the website indicating that the user authenticated successfully. The website checks that the token is valid, and if it is, signs the user in. OIDC is an authentication protocol built on top of the OAuth 2.0 authorization framework, and internally uses JSON web tokens (JWT) for exchanging user information. OIDC has generally replaced the older **OpenID** specification [Federated Identity](https://developer.mozilla.org/en-US/docs/Web/Security/Authentication/Federated_identity).
 
 OIDC lets websites *delegate* authentication to a third party. However, something needs to actually *do* the authentication. Many sites do authentication by implementing a password system, but there are alternatives. Two especially common ones are the Credential Management API and its extension the Web Authentication API.