From cbd761df176591bfa6f9e67b070c0e1246ae3046 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Mon, 3 May 2021 08:21:09 -0600 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Patrick Cloke --- content/client-server-api/modules/sso_login.md | 2 +- informal/idp-brands.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/modules/sso_login.md b/content/client-server-api/modules/sso_login.md index 71bd32bbe..c9f95413a 100644 --- a/content/client-server-api/modules/sso_login.md +++ b/content/client-server-api/modules/sso_login.md @@ -40,7 +40,7 @@ administrator to configure where the CAS server is and the REST endpoints which consume the ticket. Homeservers may optionally expose multiple possible SSO options for -the user to persue, typically in the form of several "login with $service" +the user to pursue, typically in the form of several "login with $service" buttons. These services, or "identity providers" (IdPs), are typically OpenID Connect, though the exact protocol used is not a concern for this specification. diff --git a/informal/idp-brands.md b/informal/idp-brands.md index 87bbc32db..1dbf0c8dd 100644 --- a/informal/idp-brands.md +++ b/informal/idp-brands.md @@ -20,7 +20,7 @@ For the brands listed here, the `identifier` would be used as the `brand` value under `m.login.sso`'s flow. Note that each brand may have their own requirements for how they are represented by clients, such as -Facebook/Twitter wanting their signature blues for button backgrounds whereas Github is not as particular +Facebook/Twitter wanting their signature blues for button backgrounds whereas GitHub is not as particular about the press requirements. Clients should not rely on this document for guidance on press requirements and instead refer to the brands individually.