From 5b29fa1255a9e2d5e073bfa672a6fdb2a312107a Mon Sep 17 00:00:00 2001 From: Vincent Kraus Date: Wed, 26 Jul 2023 18:09:13 +0200 Subject: [PATCH] fix: deploy --- docs/kratos/social-signin/09_ory.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/kratos/social-signin/09_ory.mdx b/docs/kratos/social-signin/09_ory.mdx index d0a1ca7fb..7e07605a5 100644 --- a/docs/kratos/social-signin/09_ory.mdx +++ b/docs/kratos/social-signin/09_ory.mdx @@ -43,8 +43,8 @@ provider using the OAuth2 authorization code flow straight away. Third-party applications will typically -- offer a "Sign in with " button, and optionally, more ways to register and log in like passkeys, passwords, or other - social sign-in providers. +- offer a **Sign in with $YourBrand\_** button, and optionally, more ways to register and log in like passkeys, passwords, or + other social sign-in providers. - store identities for the application's user base, which is a subset of the identities managed by the SSO provider, plus any identities who sign in through other means. - store additional user data, which is not managed by the SSO provider, alongside a subset of the identity traits managed by the