Typos + formatting

Author: mmacy

articles/active-directory-b2c/customize-ui-overview.md

@@ -47,11 +47,11 @@ If customers try to edit their profile before signing in, they're redirected to
 
 User flows provide several built-in templates you can choose from to give your user experience pages a professional look. These layout templates can also and serve as starting point for your own customization.
 
-In the left menu, under **Customize**, select **Page layouts**. Then select **Template**.
+Under **Customize** in the left menu, select **Page layouts** and then select **Template**.
 
 ![Template selection drop-down in user flow page of Azure portal](media/customize-ui-overview/template-selection.png)
 
-Select a template from the list. Examples of each of the available templates' sign-in pages appear below.
+Next, select a template from the list. Here are examples of the sign-in pages for each template:
 
 | Ocean Blue | Slate Gray | Classic |
 |:-:|:-:|:-:|
@@ -63,18 +63,18 @@ When you choose a template, the selected layout is applied to all pages in your
 
 Azure AD B2C runs code in your customer's browser and uses a modern approach called [Cross-Origin Resource Sharing (CORS)](https://www.w3.org/TR/cors/).
 
-At runtime, content is loaded from a URL that you specify in a your user flow or custom policy. Each page in the user experience loads its content from the URL you specify for that page. After content is loaded from your URL, it's merged with an HTML fragment inserted by Azure AD B2C, and then the page is displayed to your customer.
+At runtime, content is loaded from a URL that you specify in your user flow or custom policy. Each page in the user experience loads its content from the URL you specify for that page. After content is loaded from your URL, it's merged with an HTML fragment inserted by Azure AD B2C, and then the page is displayed to your customer.
 
 Review the following guidance before using your own HTML and CSS files to customize the UI:
 
-- Azure AD B2C merges HTML content into your pages. Don't copy and try to change the default content that Azure AD B2C provides. It's best to build your HTML content from scratch and use the default content as reference.
-- JavaScript can now be included in your custom content.
-- Supported browser versions are:
+- Azure AD B2C **merges** HTML content into your pages. Don't copy and try to change the default content that Azure AD B2C provides. It's best to build your HTML content from scratch and use the default content as reference.
+- **JavaScript** can be included in your custom content for both [user flows](user-flow-javascript-overview.md) and [custom policies](javascript-samples.md).
+- Supported **browser versions** are:
   - Internet Explorer 11, 10, and Microsoft Edge
   - Limited support for Internet Explorer 9 and 8
   - Google Chrome 42.0 and above
   - Mozilla Firefox 38.0 and above
-- Don't include form tags in your HTML. Form tags interfere with the POST operations generated by the HTML injected by Azure AD B2C.
+- Don't include **form tags** in your HTML. Form tags interfere with the POST operations generated by the HTML injected by Azure AD B2C.
 
 ### Where do I store UI content?