Merge pull request #218504 from derisen/patch-16

remove potentially misleading notice

Author: prmerger-automator[bot]

articles/active-directory/develop/msal-node-migration.md

@@ -25,14 +25,11 @@ ms.custom: has-adal-ref
 
 ## Update app registration settings
 
-When working with ADAL Node, you were likely using the **Azure AD v1.0 endpoint**. Apps migrating from ADAL to MSAL should also consider switching to **Azure AD v2.0 endpoint**.
+When working with ADAL Node, you were likely using the **Azure AD v1.0 endpoint**. Apps migrating from ADAL to MSAL should switch to **Azure AD v2.0 endpoint**.
 
 1. Review the [differences between v1 and v2 endpoints](../azuread-dev/azure-ad-endpoint-comparison.md)
 1. Update, if necessary, your existing app registrations accordingly.
 
-> [!NOTE]
-> In order to ensure backward compatibility, MSAL Node supports both v1.0 end v2.0 endpoints.
-
 ## Install and import MSAL
 
 1. install MSAL Node package via NPM:
@@ -177,7 +174,7 @@ authenticationContext.acquireTokenWithAuthorizationCode(
 );
 ```
 
-MSAL Node supports both **v1.0** and **v2.0** endpoints. The v2.0 endpoint employs a *scope-centric* model to access resources. Thus, when you request an access token for a resource, you also need to specify the scope for that resource:
+The v2.0 endpoint employs a *scope-centric* model to access resources. Thus, when you request an access token for a resource, you also need to specify the scope for that resource:
 
 ```javascript
 const tokenRequest = {