From 953344c3719edf392852f1d9e215e24e7cd5d5e3 Mon Sep 17 00:00:00 2001
From: Bubka <858858+Bubka@users.noreply.github.com>
Date: Fri, 12 Apr 2024 10:51:05 +0200
Subject: [PATCH] Add Enabling SSO section & small adjustments

---
 docs/security/Authentication/sso.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/security/Authentication/sso.md b/docs/security/Authentication/sso.md
index 7202d2f..e10d74b 100644
--- a/docs/security/Authentication/sso.md
+++ b/docs/security/Authentication/sso.md
@@ -13,6 +13,10 @@ SSO is probably overkill for a single user usage but becomes relevant in a multi
 For now 2FAuth only supports 2 SSO providers: __OpenID__ and __Github__
 !!!
 
+## Enabling SSO
+
+SSO is enabled by default. You can check it at _Admin > App setup_, in the _Registrations_ section.
+
 ## Enable a provider
 
 ### Create the client
@@ -93,13 +97,13 @@ When you sign in via SSO for the first time, you are registered to 2FAuth transp
 
 ## Disabling SSO
 
-As an administrator, you can fully disable Single sign-On from the 2FAuth UI.
+As an administrator, you can fully disable Single Sign-On from the 2FAuth UI.
 
 Go to _Admin > App setup_, scroll down to the _Registrations_ section and uncheck [!badge size="l" icon="checkbox" text="Enable Single Sign-On"].
 
 Note that:
 
 - Existing "SSO users" won't be able to sign in via SSO anymore, but their accounts remain. Still, the password reset feature can be used so they can get a password and sign in again.
-- There is no need to disable the providers env vars.
+- There is no need to unset the providers env vars.
 
 Enabling back SSO restores the providers and the ability for SSO users to sign in again.