Update entra-id-saml.mdx

Update to fix some typos and add the single sign out

Author: clairekinde11

src/content/docs/authenticate/enterprise-connections/entra-id-saml.mdx

@@ -60,17 +60,18 @@ You can make a connection available only to a specific organization, or you can
    </Aside>
 
 2. For the **Entity ID**, enter a random string like `hEb876ZZlkg99Dwat64Mnbvyh129`. Make a copy of the string as you will add this to your SAML application later.
-3. Scroll past the IdP metadata URL and other key attribute fields. We will ad dthis information later. 
+3. Scroll past the IdP metadata URL and other key attribute fields. We will add this information later. 
 4. Enter **Home realm domains**. This speeds up the sign in process for users of those domains.
    Note that all home realm domains must be unique across all connections in an environment. For more information about how, see [Home realm domains or IdP discovery](/authenticate/enterprise-connections/home-realm-discovery/).
 
    ![SAML configuration screen](https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/79c7b045-d391-47a0-ee77-a2c3cbb78c00/public)
 
 5. If you use home realm domains, the sign in button is hidden on the auth screen by default. To show the SSO button, select the **Always show sign-in button** option. 
 6. Copy the ACS URL, you will need this for the SAML provider app.
-6. If you want to enable just-in-time (JIT) provisioning, select the **Create a user record in Kinde** option. This saves time adding users manually or via API later.
-7. Select if you want to treat this connection as a trusted provider. A [trusted provider](/authenticate/about-auth/identity-and-verification/) is one that guarantees the email they issue is verified. We recommend leaving this off for maximum security.
-14. Select **Save**.
+7. Select if you want to **enable single sign out**. This will sign the user out of their Microoft Entra ID SAML account and end all sessions when they sign out. 
+8. If you want to enable just-in-time (JIT) provisioning, select the **Create a user record in Kinde** option. This saves time adding users manually or via API later.
+9. Select if you want to treat this connection as a trusted provider. A [trusted provider](/authenticate/about-auth/identity-and-verification/) is one that guarantees the email they issue is verified. We recommend leaving this off for maximum security.
+10. Select **Save**.
 
 ## Step 3: Create and configure an Entra ID enterprise application
 
@@ -104,13 +105,13 @@ Make sure you test the connection before enabling in production for your users.
    - First name attribute (Given name)
    - Last name attribute (Surname)
 3. Open the **Federation Metadata XML** file in a text editor and copy the contents of the file. 
-4. Paste them into the **Signing certifiacte** field in the Kinde connection.
+4. Paste them into the **Signing certificate** field in the Kinde connection.
 2. Switch on the connection. This will make it instantly available to users if this is your production environment.
    1. For environment-level connections, scroll down and select the apps that will use the auth method.
    2. For organization-level connections, scroll down and select if you want to switch this on for the org. 
 3. Select **Save**.
 
-## Step 4: Test the connection
+## Step 5: Test the connection
 
 1. Go to your test application and attempt to sign in.
 2. If you left the **Home realm domains** field blank in Kinde, when you launch your application, you should see a button to sign in. Click it and go to step 4.