(AzureCXP) fixes MicrosoftDocs/azure-docs#106471

Performed changes in line no. 77
Changed from 
"you won't need to make any changes to them if you've them configured already."
changed to
"you won't need to make any changes to them if you've  configured them already. "

Author: YashikaTyagii

articles/active-directory/authentication/how-to-authentication-methods-manage.md

@@ -74,7 +74,7 @@ To check settings in the Authentication methods policy, sign in as an [Authentic
 
 :::image type="content"  source="media/concept-authentication-methods-manage/authentication-methods-policy.png" alt-text="Screenshot that shows the authentication methods." lightbox="media/concept-authentication-methods-manage/authentication-methods-policy.png":::
 
-The Authentication methods policy has other methods that aren't available in the legacy policies, such as FIDO2 security key, Temporary Access Pass, and Azure AD certificate-based authentication. These methods aren't in scope for migration and you won't need to make any changes to them if you've them configured already. 
+The Authentication methods policy has other methods that aren't available in the legacy policies, such as FIDO2 security key, Temporary Access Pass, and Azure AD certificate-based authentication. These methods aren't in scope for migration and you won't need to make any changes to them if you've  configured them already. 
 
 If you've enabled other methods in the Authentication methods policy, write down the users and groups who can or can't use those methods. Take a note of the configuration parameters that govern how the method can be used. For example, you can configure Microsoft Authenticator to provide location in push notifications. Make a record of which users and groups are enabled for similar configuration parameters associated with each method.