(AzureCXP) fixes MicrosoftDocs/azure-docs#93193

Updated line 35 with review comments

Author: shwetamathur7

articles/active-directory/develop/v2-oauth-ropc.md

@@ -32,7 +32,7 @@ The Microsoft identity platform supports the [OAuth 2.0 Resource Owner Password
 > * If users need to use [multi-factor authentication (MFA)](../authentication/concept-mfa-howitworks.md) to log in to the application, they will be blocked instead.
 > * ROPC is not supported in [hybrid identity federation](../hybrid/whatis-fed.md) scenarios (for example, Azure AD and ADFS used to authenticate on-premises accounts). If users are full-page redirected to an on-premises identity providers, Azure AD is not able to test the username and password against that identity provider. [Pass-through authentication](../hybrid/how-to-connect-pta.md) is supported with ROPC, however.
 > * An exception to a hybrid identity federation scenario would be the following: Home Realm Discovery policy with AllowCloudPasswordValidation set to TRUE will enable ROPC flow to work for federated users when on-premises password is synced to cloud. For more information, see [Enable direct ROPC authentication of federated users for legacy applications](../manage-apps/home-realm-discovery-policy.md#enable-direct-ropc-authentication-of-federated-users-for-legacy-applications).
-> * There is a known issue where password with leading or trailing whitespaces are not supported with ROPC flow.
+> * Passwords with leading or trailing whitespaces are not supported by the ROPC flow.
 
 [!INCLUDE [try-in-postman-link](includes/try-in-postman-link.md)]