Update use-scim-to-provision-users-and-groups.md

Author: Jak-MS

articles/active-directory/manage-apps/use-scim-to-provision-users-and-groups.md

@@ -1318,7 +1318,7 @@ The SCIM spec does not define a SCIM-specific scheme for authentication and auth
 *  Client ID: The authorization server issues the registered client a client identifier, which is a unique string representing the registration information provided by the client.  The client identifier is not a secret; it is exposed to the resource owner and **must not** be used alone for client authentication.  
 *  Client secret: The client secret is a secret generated by the authorization server. It should be a unique value known only to the authorization server. 
 
-Best practices (recommended but not required)
+Best practices (recommended but not required):
 * Support multiple redirect URLs. Administrators can configure provisioning from both "portal.azure.com" and "aad.portal.azure.com". Supporting multiple redirect URLs will ensure that users can authorize access from either portal.
 * Support multiple secrets to ensure smooth secret renewal, without downtime.