Resolve build warnings

Author: Dickson-Mwendia

msal-javascript-conceptual/browser/iframe-usage.md

@@ -19,7 +19,7 @@ By default, MSAL prevents full-frame redirects to **Azure AD** authentication en
 - Similarly, you'll have to use the [logoutPopup()](./logout.md#logoutpopup) API for sign-outs (:warning: if your app is using a version of msal-browser older than v2.13, make sure to upgrade and replace the `logout()` API, as it will attempt a full-frame redirect to Azure AD).
 - When using [popup APIs](./initialization.md#popup-apis), you need to take into account any [sandboxing](https://html.spec.whatwg.org/multipage/origin.html#sandboxing) restrictions imposed by the parent app. In particular, the parent app needs to set the `allow-popups` flag when the iframe is sandboxed.
 
-**Azure AD B2C** offers an [embedded sign-in experience](https://docs.microsoft.com/azure/active-directory-b2c/embedded-login), which allows rendering a custom login UI in an iframe. Since MSAL prevents redirect in iframes by default, you'll need to set the [allowRedirectInIframe](./configuration.md#system-config-options) configuration option to **true** in order to make use of this feature. Note that enabling this option for apps on **Azure AD** is not recommended, due to the above restriction.
+**Azure AD B2C** offers an [embedded sign-in experience](/azure/active-directory-b2c/embedded-login), which allows rendering a custom login UI in an iframe. Since MSAL prevents redirect in iframes by default, you'll need to set the [allowRedirectInIframe](./configuration.md#system-config-options) configuration option to **true** in order to make use of this feature. Note that enabling this option for apps on **Azure AD** is not recommended, due to the above restriction.
 
 ## Browser restrictions
 

msal-javascript-conceptual/browser/known-issues-ie-edge-browsers.md

@@ -58,9 +58,9 @@ Note, these workarounds won't solve the issue for InPrivate browsing since both
 
 ## Issues due to popup blockers
 
-There are cases when popups are blocked in IE or Microsoft Edge, for example when a second popup occurs during [multi-factor authentication](~/identity/authentication/concept-mfa-howitworks.md). You'll get an alert in the browser to allow for the pop-up window once or always. If you choose to allow, the browser opens the pop-up window automatically and returns a `null` handle for it. As a result, the library doesn't have a handle for the window and there's no way to close the pop-up window. The same issue doesn't happen in Chrome when it prompts you to allow pop-up windows because it doesn't automatically open a pop-up window.
+There are cases when popups are blocked in IE or Microsoft Edge, for example when a second popup occurs during [multi-factor authentication](/entra/identity/authentication/concept-mfa-howitworks). You'll get an alert in the browser to allow for the pop-up window once or always. If you choose to allow, the browser opens the pop-up window automatically and returns a `null` handle for it. As a result, the library doesn't have a handle for the window and there's no way to close the pop-up window. The same issue doesn't happen in Chrome when it prompts you to allow pop-up windows because it doesn't automatically open a pop-up window.
 
 As a **workaround**, developers need to allow popups in IE and Microsoft Edge before they start using their app to avoid this issue.
 
 ## Next steps
-Learn more about [Using MSAL.js in Internet Explorer](msal-js-use-ie-browser.md).
+Learn more about [Using MSAL.js in Internet Explorer](use-ie-browser.md).

msal-javascript-conceptual/browser/resources-and-scopes.md

@@ -12,7 +12,7 @@ ms.reviewer: dmwendia, cwerner, owenrichards, kengaderdus
 
 # Resources and scopes
 
-Azure Active Directory v2.0 & Microsoft Identity Platform employs a *scope-centric* model to access resources. Here, a *resource* refers to any application that can be a recipient of an **Access Token** (such as [MS Graph API](https://docs.microsoft.com/graph/overview) or your own web API), and a *scope* (*aka* "permission") refers to any aspect of a resource that an **Access Token** grants rights.
+Azure Active Directory v2.0 & Microsoft Identity Platform employs a *scope-centric* model to access resources. Here, a *resource* refers to any application that can be a recipient of an **Access Token** (such as [MS Graph API](/graph/overview) or your own web API), and a *scope* (*aka* "permission") refers to any aspect of a resource that an **Access Token** grants rights.
 
 **Access Token** requests in **MSAL.js** are meant to be *per-resource-per-scope(s)*. This means that an **Access Token** requested for resource **A** with scope `scp1`:
 

msal-javascript-conceptual/browser/token-lifetimes.md

@@ -44,7 +44,7 @@ The `PublicClientApplication` object exposes an API called `acquireTokenSilent`
 4. If the access token is expired but the refresh token is still valid, MSAL will use the given refresh token to retrieve a new set of tokens, and then return a response.
 5. If the refresh token is expired, MSAL will attempt to retrieve an access tokens silently using a hidden iframe. This will use the sid or username in the account's claims object to retrieve a hint about the user's session. If this hidden iframe call fails, MSAL will pass on an error from the server as an `InteractionRequiredAuthError`, asking to retrieve an authorization code to retrieve a new set of tokens. You can do this by performing a login or acquireToken API call with the `PublicClientApplication` object. If the session is still active, the server will send a code without any user prompts. Otherwise, the user will be required to enter their credentials.
 
-See [here](./request-response-object.md#silentflowrequest) for more information on what configuration parameters you can set for the `acquireTokenSilent` method.
+See [the request and response objects](./request-response-object.md) article for more information on what configuration parameters you can set for the `acquireTokenSilent` method.
 
 ### Cache Lookup Policy
 

msal-javascript-conceptual/browser/v1-migration.md

@@ -20,7 +20,11 @@ Go to the Azure AD portal for your tenant and review the App Registrations. You
 
 ## 2. Add the msal-browser package to your project
 
-See the [installation section of the README](../README.md#installation).
+Using npm, use the following:
+
+```javascript
+npm install @azure/msal-browser
+```
 
 ## 3. Update your code
 

msal-javascript-conceptual/media/PackageStructure.png

@@ -246,6 +246,3 @@ Please look at the On Behalf Of flow [sample](https://github.com/AzureAD/microso
 * [WebAPI](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-node-samples/on-behalf-of/web-api/index.js) sample code
 * [WebApp](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-node-samples/on-behalf-of/web-app/index.js) sample code
 
-## Next Steps
-
-Proceed to understand the public APIs provided by `msal-node` for acquiring tokens [here](../browser/response.md)

msal-javascript-conceptual/node/request.md

@@ -39,7 +39,7 @@ The [`lib`](https://github.com/AzureAD/microsoft-authentication-library-for-js/t
 
 There are a number of different packages meant for different platforms. You can see the relationship between packages and different authentication flows they implement in the package structure below.
 
-![Package Structure](PackageStructure.png)
+![Package Structure](./media/PackageStructure.png)
 
 ## Samples
 

msal-javascript-conceptual/overview.md

@@ -74,7 +74,7 @@ This error is thrown when an interactive API (`loginPopup`, `loginRedirect`, `ac
 
 In `@azure/msal-react` there are 2 scenarios when this can happen:
 
-1. Your application is calling one of the APIs outside of the context where you do not have access to the `inProgress` state. For more about context see the [FAQ](./faq.md#what-can-i-do-outside-of-msal-react-context)
+1. Your application is calling one of the APIs outside of the context where you do not have access to the `inProgress` state. For more about context see the [MSAL React FAQ](./faq.md)
 1. Your application is calling one of the APIs without first checking if interaction is already in progress elsewhere.
 
 The following snippet throws the error when another component has already invoked an interactive API that is in progress:

msal-javascript-conceptual/react/errors.md

@@ -84,13 +84,14 @@ This means the following APIs are off-limits outside the context of `MsalProvide
 **Note:** If you do choose to use any other `@azure/msal-browser` API outside of the react context you should still use the same `PublicClientApplication` instance you pass into `MsalProvider`.
 
 ## How do I implement self-service sign-up?
-MSAL React supports self-service sign-up in the auth code flow. Please see our docs [here](https://azuread.github.io/microsoft-authentication-library-for-js/ref/modules/_azure_msal_browser.html#popuprequest) for supported prompt values in the request and their expected outcomes, and [here](http://aka.ms/s3u) for an overview of self-service sign-up and configuration changes that need to be made to your Azure tenant. Please note that that self-service sign-up is not available in B2C and test environments.
+
+MSAL React supports self-service sign-up in the auth code flow. Please see our docs [here](https://azuread.github.io/microsoft-authentication-library-for-js/ref/modules/_azure_msal_browser.html#popuprequest) for supported prompt values in the request and their expected outcomes, and an overview of [self-service sign-up](/entra/external-id/self-service-sign-up-overview) and configuration changes that need to be made to your Azure tenant. Please note that that self-service sign-up is not available in B2C and test environments.
 
 ## B2C
 
 ### How do I handle the forgot password flow in a react app?
 
-The [new password reset experience](https://docs.microsoft.com/azure/active-directory-b2c/add-password-reset-policy?pivots=b2c-user-flow#self-service-password-reset-recommended) is now part of the sign-up or sign-in policy. When the user selects the **Forgot your password?** link, they are immediately sent to the Forgot Password experience. You don't need a separate policy for password reset anymore.
+The [new password reset experience](/azure/active-directory-b2c/add-password-reset-policy?pivots=b2c-user-flow#self-service-password-reset-recommended) is now part of the sign-up or sign-in policy. When the user selects the **Forgot your password?** link, they are immediately sent to the Forgot Password experience. You don't need a separate policy for password reset anymore.
 
 Our recommendation is to move to the new password reset experience since it simplifies the app state and reduces error handling on the user-end. If for some reason you have to use the legacy forgot password flow, you'll have to handle the `AADB2C90118` error response returned from B2C service when a user selects the **Forgot your password?** link, and call login again with your forgot password policy.