Update securetransport-tutorial.md

Author: bhavana-129

articles/active-directory/saas-apps/securetransport-tutorial.md

@@ -64,29 +64,29 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
 
     a. In the **Identifier** textbox, type one of the following URLs:
 
-    | Usertype | URL |
+    | User type | URL |
     |----------|----------|
     | Admin | `st.sso.admin`|
     | Enduser | `st.sso.enduser` |
 
     b. In the **Reply URL** textbox, type a URL using one of the following patterns:
 
-    | Usertype | URL |
+    | User type | URL |
     |----------|----------|
     | Admin | `https://<SecureTransport_Address>:<PORT>/saml2/sso/post/j_security_check`|
     | Enduser | `https://<SecureTransport_Address>:<PORT>/saml2/sso/post` |
 
     c. In the **Sign on URL** textbox, type a URL using one of the following patterns:
 
-    | Usertype | URL |
+    | User type | URL |
     |----------|----------|
     | Admin | `https://<SecureTransport_Address>:<PORT>` |
     | Enduser | `https://<SecureTransport_Address>:<PORT>` |
 
     > [!NOTE]
     > These values are not real. Update these values with the actual Reply URL and Sign on URL. Contact [SecureTransport Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
 
-1. Your SecureTransport application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows an example for this. The default value of **Unique User Identifier** is **user.userprincipalname** but SecureTransport expects this to be mapped with the user's displayname. For that you can use **user.displayname** attribute from the list or use the appropriate attribute value based on your organization configuration.
+1. Your SecureTransport application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows an example for this. The default value of **Unique User Identifier** is **user.userprincipalname** but SecureTransport expects this to be mapped with the user's display name. For that you can use **user.displayname** attribute from the list or use the appropriate attribute value based on your organization configuration.
 
 	![Screenshot shows the image of token attributes configuration.](common/default-attributes.png "Image")