acrolinx fixes

Author: tapanm-MSFT

powerapps-docs/maker/portals/compose-page.md

@@ -354,7 +354,7 @@ The source code is displayed in the **Code Editor** pane at the bottom of the sc
 
 ## Add Power BI
 
-You can add Power BI component on a page to display Power BI dashboards and reports on your portal. When adding a Power BI component, you have different options such as access type, workspace, and advanced settings.
+You can add Power BI component on a page to display Power BI dashboards and reports on your portal.
 
 > [!NOTE]
 > Before you begin, read [Power BI access type considerations](#power-bi-access-type-considerations) and [general Power BI considerations](#general-power-bi-considerations) to get familiar with important Power BI terms and considerations for Power Apps portals.
@@ -417,19 +417,19 @@ To add a Power BI component to a web page:
         <br> For more information, go to [filter parameter details](https://docs.microsoft.com/power-bi/service-url-filters).
         - Only available for **Reports** with access types **Embed for your customer** and **Embed for your organization**.
 
-    1. **Embed code URL**: Enter embed code URL. 
+    1. **Embed code URL**: Enter embed code URL.
 
         ![Embed Code URL](media/embed-code-url.png "Embed Code URL")
 
-        - To learn how to get embed code URL, go to [Publish to web from Power BI](https://docs.microsoft.com/power-bi/service-publish-to-web)
+        - To learn about how to get embed code URL, go to [Publish to web from Power BI](https://docs.microsoft.com/power-bi/service-publish-to-web)
         - Only available for access type **Publish to web**.
 
 ### Power BI access type considerations
 
-The following explains Power BI access types in brief and lists access type considerations for Power Apps portals. For more information, go to [Difference between Power BI service and Power BI embedded](https://docs.microsoft.com/power-bi/developer/embedded/embedded-faq#how-is-power-bi-embedded-different-from-power-bi-the-service).
+The following list explains Power BI access types in brief. And lists access type considerations for Power Apps portals. For more information about Power BI access types, go to [Difference between Power BI service and Power BI embedded](https://docs.microsoft.com/power-bi/developer/embedded/embedded-faq#how-is-power-bi-embedded-different-from-power-bi-the-service).
 
 - **Embed for your customers**:
-    - Shows the list of workspaces shared to logged in user and enabled for [Power BI Embedded service](../portals/admin/set-up-power-bi-integration.md#enable-power-bi-embedded-service).
+    - Shows the list of workspaces shared to user currently logged in and enabled for [Power BI Embedded service](../portals/admin/set-up-power-bi-integration.md#enable-power-bi-embedded-service).
     - Uses Power BI Embedded service.
     - If you've used Power BI Embedded service with Power Apps portals before, you'll see the following error when you select **Embed for your customers**:
 
@@ -443,21 +443,21 @@ The following explains Power BI access types in brief and lists access type cons
     - Shows the list of workspaces shared with logged in user.
     - Uses Azure Active Directory authentication.
 
-- **Publish to web**: Anyone on Internet can view your published report or visual. This requires no authentication and includes viewing detail level data your reports aggregate. Before publishing a report, make sure you can share the data and visualizations publicly. Do not publish confidential or sensitive information. When in doubt, check your organization's policies before publishing.
+- **Publish to web**: Anyone on Internet can view your published report or visual. This requires no authentication and includes viewing detail level data your reports aggregate. Before publishing a report, make sure you can share the data and visualizations publicly. Don't publish confidential or sensitive information. Refer to your organization's policies before publishing.
 
 ### General Power BI considerations
 
-- [Portals Studio](../portals/portal-designer-anatomy.md) performance can degrade while working with Power BI workspaces due to the following Power BI workspace configurations:
+- [Portals Studio](../portals/portal-designer-anatomy.md) performance can degrade while working with Power BI workspaces because of the following Power BI workspace configurations:
     - High number of workspaces shared with logged in maker user.
     - Power BI workspaces are shared with many users.
-- [Capture liquid variable](../portals/liquid/portals-entity-tags.md#powerbi) is not supported in portals Studio while working with Power BI component.
+- [Capture liquid variable](../portals/liquid/portals-entity-tags.md#powerbi) isn't supported in portals Studio while working with Power BI component.
 - If you [reset portal](../portals/admin/reset-portal.md) and provision a new portal, you must add portal application ID of the new portal to the **Portal Power BI Embedded service** Azure AD security group. For more information, go to [Set up Power BI integration](../portals/admin/set-up-power-bi-integration.md#create-security-group-and-add-to-power-bi-account).
 - If you make a change in Power Apps portals admin center, you must reload the portals Studio if you already have it open.
 - Adding users to Power BI dashboards and reports may take a while to reflect in the portals Studio.
 
 ### Power BI performance and optimization considerations
 
-Embedding multiple Power BI workspaces may need additional considerations. Refer to the following resources for Power BI embed scenario troubleshooting, optimization and best practices:
+Embedding multiple Power BI workspaces may need additional considerations. Refer to the following resources for Power BI embed scenario troubleshooting, optimization, and best practices:
 
 - [Troubleshooting Power BI Embedded application content rendering](https://docs.microsoft.com/power-bi/developer/embedded/embedded-troubleshoot#content-rendering).
 - [Power BI Embedded performance best practices](https://docs.microsoft.com/power-bi/developer/embedded/embedded-performance-best-practices).