diff --git a/packages/console/src/assets/docs/single-sign-on/AzureAD/README.mdx b/packages/console/src/assets/docs/single-sign-on/AzureAD/README.mdx
index 39807c6b0..56b311d01 100644
--- a/packages/console/src/assets/docs/single-sign-on/AzureAD/README.mdx
+++ b/packages/console/src/assets/docs/single-sign-on/AzureAD/README.mdx
@@ -120,7 +120,7 @@ Visit the `Users and groups` section of your Azure AD SSO application. Click on
 
 Provide the email `domains` of your organization at the Logto's SAML SSO connector `experience` tab. This will enable the SSO connector as an authentication method for those users.
 
-Users with email addresses in the specified domains will be restricted to use SAML SSO connector as their only authentication method.
+Users with email addresses in the specified domains will be exclusively limited to use SAML SSO connector as their only authentication method.
 
 </Step>
 
diff --git a/packages/console/src/assets/docs/single-sign-on/GoogleWorkspace/README.mdx b/packages/console/src/assets/docs/single-sign-on/GoogleWorkspace/README.mdx
index 879e5adaf..3657cccba 100644
--- a/packages/console/src/assets/docs/single-sign-on/GoogleWorkspace/README.mdx
+++ b/packages/console/src/assets/docs/single-sign-on/GoogleWorkspace/README.mdx
@@ -102,7 +102,7 @@ Use the `Scope` field to add additional scopes to your OAuth request. This will
 
 Provide the email `domains` of your organization on the connector `experience` tab. This will enabled the SSO connector as an authentication method for those users.
 
-Users with email addresses in the specified domains will be restricted to use your SSO connector as their only authentication method.
+Users with email addresses in the specified domains will be exclusively limited to use your SSO connector as their only authentication method.
 
 </Step>
 
diff --git a/packages/console/src/assets/docs/single-sign-on/OIDC/README.mdx b/packages/console/src/assets/docs/single-sign-on/OIDC/README.mdx
index 56a8ca7c0..754dab28e 100644
--- a/packages/console/src/assets/docs/single-sign-on/OIDC/README.mdx
+++ b/packages/console/src/assets/docs/single-sign-on/OIDC/README.mdx
@@ -37,6 +37,6 @@ After successfully creating an OIDC application on the IdP side, you will need t
 
 Provide the email `domains` of your organization on the connector `experience` tab. This will enabled the SSO connector as an authentication method for those users.
 
-Users with email addresses in the specified domains will be restricted to use your SSO connector as their only authentication method.
+Users with email addresses in the specified domains will be exclusively limited to use your SSO connector as their only authentication method.
 
 </Step>
diff --git a/packages/console/src/assets/docs/single-sign-on/OKTA/README.mdx b/packages/console/src/assets/docs/single-sign-on/OKTA/README.mdx
index 977f916fb..9404296a9 100644
--- a/packages/console/src/assets/docs/single-sign-on/OKTA/README.mdx
+++ b/packages/console/src/assets/docs/single-sign-on/OKTA/README.mdx
@@ -76,7 +76,7 @@ Use the `Scope` field to add additional scopes to your OAuth request. This will
 
 Provide the email `domains` of your organization on the connector `experience` tab. This will enabled the SSO connector as an authentication method for those users.
 
-Users with email addresses in the specified domains will be restricted to use your SSO connector as their only authentication method.
+Users with email addresses in the specified domains will be exclusively limited to use your SSO connector as their only authentication method.
 
 </Step>
 
diff --git a/packages/console/src/assets/docs/single-sign-on/SAML/README.mdx b/packages/console/src/assets/docs/single-sign-on/SAML/README.mdx
index 8eea78ed3..ec1390c2b 100644
--- a/packages/console/src/assets/docs/single-sign-on/SAML/README.mdx
+++ b/packages/console/src/assets/docs/single-sign-on/SAML/README.mdx
@@ -1,7 +1,7 @@
 import SsoSamlSpMetadata from '@/mdx-components/SsoSamlSpMetadata';
 import Step from '@/mdx-components/Step';
 
-<Step index={0} title="Create an SAML SSO application on your IdP" >
+<Step index={0} title="Create a SAML SSO application on your IdP" >
 
 Initiate the SAML SSO integration by creating an application on the IdP side. Obtain the following configurations from Logto, representing your Service Provider (SP):
 
@@ -15,7 +15,7 @@ Fill in the above configurations in your IdP SAML application and continue to re
 
 </Step>
 
-<Step index={1} Configure SAML SSO on Logto>
+<Step index={1} title="Configure SAML SSO on Logto">
 
 To make the SAML SSO integration work, you will need to provide the IdP metadata to Logto. The IdP metadata is an XML document that contains all the information required for Logto to establish the trust with the IdP.
 
@@ -51,6 +51,6 @@ The user attributes returned from IdP may vary depending on the IdP configuratio
 
 Provide the email `domains` of your organization in the SAML SSO integration `experience` tab. This will enable the SSO connector as an authentication method for those users.
 
-Users with email addresses in the specified domains will be restricted to use SAML SSO connector as their only authentication method.
+Users with email addresses in the specified domains will be exclusively limited to use SAML SSO connector as their only authentication method.
 
 </Step>