review updates

rwike77 · rwike77 · commit 142b97378b59 · 2019-05-17T13:55:48.000-07:00
diff --git a/articles/active-directory/develop/msal-js-known-issues-ie-edge-browsers.md b/articles/active-directory/develop/msal-js-known-issues-ie-edge-browsers.md
@@ -48,9 +48,8 @@ Fixes for the authentication redirect loop issues have been released in [MSAL.js
 
 When the `storeAuthStateInCookie` flag is enabled, MSAL.js will use the browser cookies to store the request state required for validation of the auth flows.
 
-**Note**:
-- This fix is not yet available for the msal-angular and msal-angularjs wrappers. 
-- This fix does not address the issue with Popup windows.
+> [!NOTE]
+> This fix is not yet available for the msal-angular and msal-angularjs wrappers. This fix does not address the issue with Popup windows.
 
 Use workarounds below.
 
@@ -72,3 +71,6 @@ Note, this will not solve the issue for InPrivate browsing since both session an
 There are cases when popups are blocked in IE or Microsoft Edge, for example when a second popup occurs during multi-factor authentication. You will get an alert in the browser to allow for the popup once or always. If you choose to allow, the browser opens the popup window automatically and returns a `null` handle for it. As a result, the library does not have a handle for the window and there is no way to close the popup window. The same issue does not happen in Chrome when it prompts you to allow popups because it does not automatically open a popup window.
 
 As a **workaround**, developers will 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).
diff --git a/articles/active-directory/develop/msal-js-use-ie-browser.md b/articles/active-directory/develop/msal-js-use-ie-browser.md
@@ -25,7 +25,7 @@ ms.collection: M365-identity-device-management
 
 Microsoft Authentication Library for JavaScript (MSAL.js) is generated for [JavaScript ES5](https://fr.wikipedia.org/wiki/ECMAScript#ECMAScript_Edition_5_.28ES5.29) so that it can run in Internet Explorer. There are, however, a few things to know.
 
-## Authoring an application to run in Internet Explorer
+## Run an app in Internet Explorer
 If you intend to use MSAL.js in applications that can run in Internet Explorer, you will need to add a reference to a promise polyfill before referencing the MSAL.js script.
 
 ```html
@@ -52,4 +52,7 @@ If you want to run and debug locally your application running in Internet Explor
     1. Restart Internet Explorer.
     1. Run and debug your application.
 
-When you are done, restore the Internet Explorer security settings.  Select **Settings** -> **Internet Options** -> **Security** -> **Reset all zones to default level**.
+When you are done, restore the Internet Explorer security settings.  Select **Settings** -> **Internet Options** -> **Security** -> **Reset all zones to default level**.
+
+## Next steps
+Learn more about [Known issues when using MSAL.js in Internet Explorer](msal-js-use-ie-browser.md).
