added more changes to the sso doc

Signed-off-by: dishanktiwari2501 <[email protected]>

content/saas/sso.md

@@ -105,7 +105,7 @@ Assuming the admin has set up its IDP, the admin can provide the necessary infor
 
 1. **Username Attribute:** This attribute refers to a username. The attribute configured in IDP for the username can be passed here.
 
-1. **Entity Issuer URL:** It contains the value of the Identifier (Entity ID). This should be your automate URL with dex callback. Ensure that this is a valid URL. The sample URL is: [https://your_automate_url/dex/callback](https://your_automate_url/dex/callback).
+1. **Entity Issuer URL:** It contains the value of the Identifier (Entity ID). This should be your automate URL with dex callback. Ensure that this is a valid URL. The sample URL is [https://your_automate_url/dex/callback](https://your_automate_url/dex/callback).
 
 1. **CA Certificate:** This is the (Base64) Certificate value generated by your IDP on app configuration. Ensure that this certificate has -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- markers. This value should be used as it is and should not contain /n sequences.
 
@@ -114,7 +114,7 @@ Assuming the admin has set up its IDP, the admin can provide the necessary infor
 1. **Allowed Groups:** This field is optional. It provides a single sign-in for members of the listed groups and discards all user groups that are not on the list. Groups must be on the allowed_groups list to access Chef Automate.
 
 1. **Name Id Policy Format:** When provided, Chef Automate will request a name ID of the configured format in the SAML AuthnRequest.
-This is a mandatory field for Microsoft365 and Azure AD IDPs Defaults to urn:oasis:names:tc:SAML:2.0:nameid-format:persistent.
+This is a mandatory field for Microsoft365 and Azure AD IDPs Defaults to `urn:oasis:names:tc:SAML:2.0:nameid-format:persistent`.
 
 ### Undo your Changes
 
@@ -124,25 +124,25 @@ Admins can now select **Cancel** to override the edited field data.
 
 1. Visit the [Okta](https://okta.com) page and log in to your account.
 
-1. Select on Applications to create your SAML application.
+1. Select Applications to create your **SAML** application.
 
 1. Select on Create App Integration.
 
-1. Select SAML 2.0, and select next.
+1. Select **SAML 2.0**, and select next.
 
 1. You will be redirected to a page where you can create your app.
 
 1. Fill in the config information as shown in the below image and select next.
 
-    * Single sign-on URL: This should be the URL for your automate server plus /dex/callback. For example: [https://your_automate_url/dex/callback](https://your_automate_url/dex/callback)
+    * Single sign-on URL: This should be the URL for your automate server plus /dex/callback. For example [https://your_automate_url/dex/callback](https://your_automate_url/dex/callback)](https://your_automate_url/dex/callback)
 
     * Audience URI: This will be the same URL as the Single sign-on URL
 
     * Default RelayState should be blank
 
-    * Name ID Format should be Unspecified
+    * Name ID format should be Unspecified
 
-    * Application Username should be Email
+    * Application username should be Email
 
     * Under attributes, you’ll want to create two:
 
@@ -156,7 +156,7 @@ Admins can now select **Cancel** to override the edited field data.
 
 1. Add users who can log in using this app.
 
-    * Select on Assignments, then Assign, and then assign to people. Select users from the list to add users to the app.
+    * Select Assignments, then Assign, and then assign to people. Select users from the list to add users to the app.
 
     IMAGE
 
@@ -256,8 +256,6 @@ The steps are as follows:
 
         * Note the following values from Section 4:
 
-          IMAGE
-
             * Login URL.
 
             * Azure AD Identifier.
@@ -266,9 +264,7 @@ The steps are as follows:
 
     * After setup, go to Users and Groups to assign users and groups to the application.
 
-      IMAGE
-
-    Click on Add user/group to assign users and groups to the application.
+    Select `Add user/group` to assign users and groups to the application.
 
 1. Configure SAML on the Chef Automate via SSO UI
 
@@ -289,7 +285,7 @@ The steps are as follows:
         * **Entity Issuer:** This should be the URL provided in section 1 for Identifier (Entity ID). (for example: In our case, it is [https://{your-chef-automate-fqdn}/dex/callback](https://{your-chef-automate-fqdn}/dex/callback))
 
         * **Name Id Policy Format:** This should be the Unique User Identifier (Name ID) value from the value column for Name ID present in square brackets. eg:- user.
-        userprincipalname [nameid-format:emailAddress]and add it to the end of urn:oasis:names:tc:SAML:1.1:.
+        userprincipalname [nameid-format:emailAddress] and add it to the end of `urn:oasis:names:tc:SAML:1.1:`.
 
         IMAGE
 
@@ -317,4 +313,4 @@ These values are accepted for name_id_policy_format:
 
 * urn:oasis:names:tc:SAML:2.0:nameid-format:transient
 
-Click the Submit button to patch the SSO settings on the chef-automate Multiple options can be selected.
+Select **Submit** button to patch the SSO settings on the chef-automate Multiple options can be selected.